Search

dfuller@atlassian.com , to 394c56f07d39 's point, this should also be linked to jiraalign-7284. similar export issues that need to be addressed.

Hi dgarcia@atlassian.com, I hope you are doing well. Thank you for your response. Like many of the customers below, we are not very pleased with the resolution of this issue. It will be nearly impossible to convince our customers, who have been working with JA for more than two years, that they are now unable to use this functionality as usual. Considering that JA is not as powerful as Jira in terms of reporting, it is important to have a way to extract data from the tool. The bug ticket was created in September 2023, and closing it and opening a new suggestion now, and gathering interest for it, is not in our best interest.

Kind Regards

Georgi Gogichev

Hey dgarcia@atlassian.com, would you be willing to link this issue to your new issue (JIRAALIGN-7421) as related issues?

Also, I'm going to post my comment here on both this issue and on the new issue.

I personally would summarize many of the use cases driving the need for high-volume exports as having the following context:

• Since many (if not all) of JA's clients operate with large sets of goal, strategy, and work data, they regularly need to investigate and analyze their data from many different angles, which requires slicing and dicing the data in a lot of different ways.
• The native reports in Jira Align are a great starting point, but I don't believe that JA now (or could ever in the future) an entirely sufficient set of native reports that covers all the users/leadership teams' needs.
• JA's API and EI solutions are certainly good-enough options for some clients, but many of my JA clients have a lot of frustration about how hard it is slice and dice the data. And there really is no one specific question that just needs a better report around it. Given that the nature of the questions is fundamentally business intelligence questions, the BI analysis/investigations need as little friction as possible to come from the tool.   
• From a coaching standpoint, there are some native reports that I've been able to steer them toward for certain information, but every JA client of mine has lamented to me that they would like some kind of way to more quickly and easily analyze and slice-and-dice and visualize their data with more flexibility.
• And while they don't enjoy resorting to the use of Excel and pivot tables, they feel like they have no other option. Thus, they will regularly ask for large data dumps out of the system so that they can throw all that data into large Excel files or BI tools to make it easier for them to interact with the data.
• Given the nature of Jira Align and that it's targeted to large customers with large, complex data sets of goals, strategies, and work and that it doesn't have sufficient native data-analysis/BI functionality that inherently is needed with large data sets like this, my own thinking is that:
  • the export functionality in Jira Align needs to be changed to allow for regular, large data dumps, and/or
  • EI & Atlassian Analytics need to be automatically included with the purchase of Jira Align

dgarcia@atlassian.com I think you can safely assume at least 35 affected customers and 64 watchers right away on the new suggestion ticket at JIRAALIGN-7421. This is sorely needed, and this current "fix" is disappointing indeed.

dgarcia@atlassian.com dfuller@atlassian.com f58471712ff6 this is not in line with any organization AT SCALE. 500 records hogwash, and hardly worth the export if you are looking at data trying to compare work and value streams for organizations that are large. If there were a better way to fully utilize API functionality for a non-technical person, then maybe you have a point, but then still have an issue of export limits so they don't tax performance. Why not create cloned servers to support reporting functionality for readily? It's a fairly clean approach and reduced the strain on the system. My guess is that Atlassian already has built in redundancy of servers, so this should be fairly low cost and effort to clone an additional server for your instances and point reporting queries to that server instead of the "main" server hosting the instance. 

My gut is telling me this is a play to funnel people into Atlassian's version of power BI.  Please set this issue to Open as it's not a fix, having this product for 3 years now there was never a suggested export limit, so to 1b3e342cf014's point, this is not a previously designed thing, or if it was, it's an abject failure on Atlassian to not properly inform its clients of that functional design and use constraint. I will not need to export issues if the filtering and summary reports were slightly more useful when trying to review cross program and cross portfolio data, PIs at a time. 

Hello Denise - so what changed ? this was working fine in the past now is not working anymore, for the record our stakeholders are using this capability since day one they got on the platform (for more than 1 and a half years) so mentioning is limited to 500 or 1000 records is not really a great answer also we invested already in your solution and also we had to invest into other solutions to created reports that partially help the user so we are already overinvested. (and reading the comments we are not the only customer in this situation) 

Hi folks,

My name is Denise Garcia and I am a Product Manager on Jira Align. I apologize for the lack of communication on the closing of this ticket. From all of the comments and votes I can understand how frustrating it has been for the export to be inconsistent with high volumes of records.

To share more context, our detailed engineering analysis of export performance indicated that the underlying infrastructure code was designed for ~500 records at optimal performance. This is similar to Jira’s 1,000 record limit. Exporting over 500 records consistently and reliably will necessitate a substantial investment in the feature and its underlying infrastructure. As a result, the pop-up modal with guidance to limit to 500 records is a step in leading you, our users, to better and more consistent results.

At this time, since the maximum the product can handle is 500 records to export, we will be closing this ticket with the guidance to limit exports to 500 records. You can read more about this modal guidance in our release notes. We have also created a new suggestion ticket to reliably support the export of more than 500 records.

We know this may fall short of expectations, so making the investment in improving export capabilities in Jira Align is something we are evaluating for future roadmap work, along with many other competing priorities. Something that will help me evaluate where our investment is best placed is to get a better understanding of your use cases for exporting. I know some of you have shared in past comments, but for any additional folks, can you share in the new suggestion ticket what are you doing with the exported data? There may be other solutions (with a shorter delivery time) that we can improve to meet your end goal with the data.

I appreciate your patience. Thank you for your continued engagement and feedback.

Cheers,

Denise Garcia

I do agree with 1b3e342cf014.

I personally believe it would make more sense to keep this bug open until the bug is fully resolved. I also agree that running the query in the background and emailing a link to the finished file would make more sense generally speaking, and it would also create more similarity in functionality/behavior between Jira Align and Jira.

My thinking is that the addition of the message to restrict the export to no more than 500 work items is a great interim improvement that potentially merits having its own issue (but I'm not sure whether we should consider that issue a bug or a suggestion, though).

This is definitely not fixed ... please address the problem as just adding a message "restrict export to 500 work items" is absolutely not acceptable.

Offer a solution to extract the data for the users by running the query in background and send the result to email if this is taxing in the UI. 

This is also still not working on 11.2.0 for our instance. This needs to be reopened