The result was an Excel file which is completely blocking/slowing down my whole system?

[PRAMOD KUMAR REDDY KASIREDDY]

Has there something changed on JIRA server side?

The Filter I use is: project = XX AND issuetype = CRQ AND issuekey not in ORDER BY key DESC

And I do a Export all fields.

Even reducing it to external only reduces the number from ~1800 to ~1400 without performance improvement.

Is this just my PC or a general problem?

Who can help me with this?

[Trudy Claspill]

Hello @PRAMOD KUMAR REDDY KASIREDDY 

If you are accessing a Jira Server/Data Center instance, that is an on premise instance. You will need to contact the administrators for your Jira instance to find out if an upgrade or other change has been made for that instance that could cause a performance impact for you.

[PRAMOD KUMAR REDDY KASIREDDY]

We see that recently the excel export of the issue also includes the details of the linked issues (as shown below) , due to which the Excel file becomes too huge sometimes and not possible to open.

Can this setting be configurable ?

[Trudy Claspill]

We do not see any data from your last post.

When exporting all fields, each row of the output will include the Issue Key for each issue that is linked to the issue in that row, but it should not be including any other details of the linked issues. If it does, that is not native functionality and has come from some third party app that has been added to your system.

Another way to reduce the output is to change your search results view from Details to List.

Then use the columns option to select just the fields you want in your export.

Then use one of the "(current fields)" options in the Export options.

These images are from Jira Cloud, but I believe the same functionality exists in Jira Server.

[Juan José Marchal Gómez]

Hello,

What do you want to do exactly?

Best regards.