Version Manager is keep on loading for long time without displaying any data for particular project

[Leo Prakash]

Hi Team,

Version Manager is keep on loading for long without displaying any data for a particular project in Jira server

all other projects are working fine. so would like to know any limitations for this app(e.g. number of version per project and so on)

or what would be cause for this. any guidance or leads would be much appreciated

Jira server: 8.5.12

App version: 1.3.1

Thanks in advance

Leo

[Holger Schimanski]

Thanks for getting in contact and reporting this issue. Couple of questions to

• Is Version Manager for Jira working fine for other projects?
• What is the normal Release tab showing?
• What is the project admin page on Versions showing?
• Do you see anything related to Version Manager for Jira in the Jira log files?
• What is the result if you call the webservice from your browser URL? e.g. key = project key http://{YOUR_JIRA_HOME_URL}/rest/versionmanager/1.0/versionmanager/{key}

‌

[Leo Prakash]

Hi @Holger Schimanski ,

Thanks for the response, please find the asnwers inline

• Is Version Manager for Jira working fine for other projects?

‌ >>> Yes, it is working fine for all other projects

• What is the normal Release tab showing?

‌ >>> Unreleased

• What is the project admin page on Versions showing?

‌ >>>Unreleased

• Do you see anything related to Version Manager for Jira in the Jira log files?

‌ >>> Sadly, couldn’t find anything in the log. that’s where I lost

• What is the result if you call the webservice from your browser URL? e.g. key = project key http://{YOUR_JIRA_HOME_URL}/rest/versionmanager/1.0/versionmanager/{key}

‌ >>> I do get api results for a project but takes more time to retrieve the data, almost takes 3 mins for getting api result

‌

Thanks & Regards,

Leo

‌

[Holger Schimanski]

Can you attach a screenshot of the release tab? And the result from the webservice call?

[Leo Prakash]

‌

[Leo Prakash]

BTW, I didn’t take screen shot of complete list as they are huge in size

‌

Thanks & Regards,

Leo

[Holger Schimanski]

Doer this project has significant higher number of versions e.g. hundred of version compared to the other projects?

[Leo Prakash]

yeah, but we do have other project with similar level of versions list which works fine though it takes sometime(not much different with other working projects)

[Leo Prakash]

Please let me know if this app has any limitations to support number of versions to check with respective team to consider their versions list once

‌

[Holger Schimanski]

Yes, there is some limitation, because the Version Manager for Jira page reads in the full list of unreleased and released versions. Looks like this is significant high and this is why even the REST API call takes 2-3 min like in your case.

The other projects with similar amount of versions might use the feature to archive versions. And then these are not loaded to the Version Manager for Jira page.

Maybe you can speak to the project team and can ask them if they could archive some of their long list of versions?

[Leo Prakash]

Thanks for the update, I’m checking with the team. if possible could you please let me know the number of versions(approximately) this app supports

Thanks in advance

[Holger Schimanski]

This is not really easy to answer because this mostly relates to network performance. The more versions you have and the less powerful network or Jira server you have, the longer it takes to load the page. But 50 versions should not be an issue I would say.

[Holger Schimanski]

After some further contact from user, I am investigating this performance issue again. Could be the case, that getting the number of assigned issues to the version (in the REST API call it’s property countissues, see above) is the root cause for the performance issue.

I am using VersionManager from Jira Java API to prepare the data for the Version Manager page using the methods getIssuesWithFixVersion and getIssuesWithAffectsVersion. Currently looking into other ways to get the count issues.

[Holger Schimanski]

Fixed in version 1.3.3 by using SearchService Jira API. Please update your Jira instance.