Jira Forge Export Excel file

[DanielVelkov]

Hello,
We need to implement an export button for some table data we generate from the issues object.
Is that possible? What are the allowed formats?
I tried an implementation using the file-saver and exceljs packages but it seems forge doesn’t allow npm packages other than @forge/ui

[ibuchanan]

Welcome to the Atlassian developer community @DanielVelkov,

@DanielVelkov

We need to implement an export button for some table data we generate from the issues object.
Is that possible?

Possible, but only as a distinct feature, not associated with existing export capabilities. See this recent discussion:

How to add menu item to the Export Issues menu

Hello, I would like to add a menu item in the Export Issues menu (in the Issues page ) and the Export menu (in the Search page) or a new Menu next to the Export Issues one. I don’t see a module in Forge to do that. Is there a way to do it? Thanks, Edgar

@DanielVelkov

What are the allowed formats?
I tried an implementation using the file-saver and exceljs packages but it seems forge doesn’t allow npm packages other than @forge/ui

It isn’t so much that there is an explicit set of “known formats”. Rather that you will have some limitations based on the Forge environment.

In the currently GA runtime, you are limited by Atlassian’s proprietary Node-like implementation. While our documentation has a pretty exhaustive list of limitations, we are aware that it’s often hard to know if those limitations apply to a specific library. You might have to probe the dependency tree pretty hard to know if and why a particular library doesn’t work.

Fortunately, there is a new Forge native Node.js runtime that helps solve these problems:

The new native Node.js runtime enables Forge functions to run within a standard Node.js environment. This will allow you to import any built-in, local, or third-party Node modules into your app.

You might try using your libraries in that runtime instead.

That said, you still don’t have full access to the infrastructure, which some libraries might assume. For example, you won’t have a way to just “drop a file” on disk and pick it up outside the Forge App. So you will still want to be aware of the new runtime’s limitations.

[DanielVelkov]

Thanks for the quick and thorough answer. I changed the project to that runtime and it at least deploys, but the file-saver “saveAs” function doesn’t work. It doesn’t throw any error nor download the file. I am using the latest package versions for forge, file-saver and excelJS. Here is the code:

const workbook = new excelJs.Workbook();
const worksheet = workbook.addWorksheet('Report Data');
workbook.xlsx.writeBuffer().then( (buffer) => {
      const blob = new Blob([buffer], { type: "applicationi/xlsx" });
      saveAs(blob,"Worklogs.xlsx");
    });

[DanielVelkov]

Has anyone tried something like this?
@ibuchanan any follow up to your answer?

[rcsr]

@DanielVelkov

applicationi/xlsx

You have a typo. Maybe it’ll work if you fix it. If not maybe try exporting it as a CSV instead - that way you can bypass the need to rely on an external library that Forge may or may not support.

We are developing a custom UI app that also allows users to export data and it works for us when exporting as JSON. Here’s a snippet that maybe you can test out:

  const jsonData = JSON.stringify(exportData);
  const blob = new Blob([jsonData], { type: 'application/json' });

  // Create a download link
  const url = URL.createObjectURL(blob);
  const download = `data.json`;

  return (
    <Button appearance='link' href={url} download={download}>
      Export summary
    </Button>
  );

Edit: Oh nevermind, I thought you were using custom UI but it looks like you’re using UI kit?

[DanielVelkov]

Yes I am using UI Kit. Maybe that’s the root of the problem.