Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Version Report says no stories associated although the filter returns a large # of results.

I use the Version Report regularly.  The next release for our project has > 6000 stories associated.  For some reason, the Version Report stopped working and says that there are no stories associated with this release.  If I view the associated query, all results are returned as they always have been.


1 answer

0 votes
Ivan Lima Community Leader Jan 01, 2021

Hi @Mandy Ernst, it's indeed really odd what you described. Did you have a chance to take a look at the View and understand the version report documentation? Perhaps you can double-check the functionalities on the last section, Understanding the Version Report, to help you troubleshoot. Also, when you mentioned "If I view the associated query", are you referring to the link on the right side of the chart "View <version name> in Issue Navigator" or to your board filter?

@Ivan Lima thank you for the response!  I took a quick look at the referenced article, just to be sure, but I do understand the Version report pretty well.  It has been a central part of our program reporting structure for the last year, and I haven't really had any issues to-date.  You are correct, I clicked on "View <version name> in Issue Navigator"...and see a full set of results.  Since this just started happening (it was working before the holidays, but now is not), I was wondering if we somehow hit some sort of max threshold of associated issues or something else pre-defined like that that could be causing the problem!?  I hope not, as I really need this report to work or I will have to re-design my entire status reporting process! :(

@Mandy Ernst, I created a test project with 7000+ issues assigned to a version, and the version report loaded just fine. For the first link, in my case, "View Version 1 in Issue Navigator", it worked without any error. The subsequent links underneath the Status Report, where you've got the link "View in Issue Navigator", throw the following error: "414 Request-URI Too Large" - which relates to the fact that requests with long URLs get rejected.

That said, assuming you have adequately reviewed your board/project(s) configurations, you should be able to have your version report working as you expected. I would advise you to have your Jira administrator to take another look into this along with you. If the error persists, even after you guys triple-check the configs, I would say it might be a candidate for an escalation with Atlassian.

The error I mentioned is a known Apache's limitation, but I'm not aware of how Jira cloud has handled it. I'll share this post with other folks as I'm now interested in learning how others have experienced similar situations.


Ivan Lima Community Leader Jan 02, 2021

Well, as an update here, I'm getting timeouts with that many issues. I'm now playing with the number of issues to determine an approximate number that my site can handle without prompting a timeout. I didn't want to touch on the fact that 6k+ stories on a single release sound a lot, but I'm beginning to believe that a re-designing is not a bad idea. 😉

Hi Ivan!  Thank you so much for your "research" and follow up.  It does sound like I've hit some sort of threshold, so I guess I'll just have to work around it for now.  

To respond to your comment, yes, I realize that this seems like an very excessive "single release".  It's a bit complicated to explain our overall structure, but long story short, we are managing a very large ERP system implementation, so while we are pulling a few things forward into early releases and pushing some stuff past the initial "MVP", the "MVP" itself is still a pretty large and concerted effort...We also have the work divided into multiple sub-teams, so we CAN still run the Version report for each of those sub teams, I have just leveraged a Program-level summary board for which the Version Report provided a nice "birds eye" view of the overall status toward that MVP deliverable.  

Thanks again for your time!!

Like Ivan Lima likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you