Hi,We're encountering a spinning icon problem when trying to delete a version inside a project in JIRA, one that never times out, and would like to know how to get around this.In more detail:- JIRA 7.6- Project -> (admin) Versions -> (select version) -> Delete- The spinning icon starts but never returns.When we look at Development Tools on the browser for this action, we can see a REST API call to:- relatedIssuesCount?=xxx {some large number}- After one minute, this call is (canceled) as seen in the devtools window- But the spinning icon never stops, nor do we see a timeout error, it will spin forever unless the window is closed.We were able to test this API relatedIssuesCount outside of project admin, and can confirm that it takes 1.7m minutes to complete.Does anyone know what setting it is that is forcing the REST call relatedIssuesCount to timeout/cancel when we try to delete a version inside a project?Cheers,Am.

Hi Amanda!Talking about the REST call relatedIssuesCount:Returns a bean containing the number of fixed in and affected issues for the given version.Source: Get version related issuesI have seen this before, but the problem was resolved by removing the version via REST:Delete project versions via delete version REST API We can try re-indexing Jira data before jumping into the REST call to remove the version just to see if it'll be any significant improvement at performance level, but, since this could require a downtime (re-indexing using the Lock JIRA and rebuild index option), testing this within a staging environment may be a good option regarding best practices.Best Regards.

Community
Q&A
Jira
Questions
Spinning icon when deleting a version inside a project

How can I unlock the Configuration of custom fields

Why is the configuration of some fields e.g. "Sprint" locked by Jira and how can I unlock those fields again? Because in the old issues it's there and only in the newly created ones I can't add this field.

1 answer

1 accepted

0 votes

Answer accepted

Hi Amanda!

Talking about the REST call relatedIssuesCount:

Returns a bean containing the number of fixed in and affected issues for the given version.
Source: Get version related issues

I have seen this before, but the problem was resolved by removing the version via REST:

Delete project versions via delete version REST API

We can try re-indexing Jira data before jumping into the REST call to remove the version just to see if it'll be any significant improvement at performance level, but, since this could require a downtime (re-indexing using the Lock JIRA and rebuild index option), testing this within a staging environment may be a good option regarding best practices.

Best Regards.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Thanks Henrique. I'm happy to accept this answer in terms of REST API. Some users will be less familiar with REST, but it is something that admins can use as a workaround. A.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Forums

Q&A

Community resources

Support

Top groups

Community resources

Support

Learn

Community resources

Support

Events

Community resources

Support

How can I unlock the Configuration of custom fields

1 answer

1 accepted

Suggest an answer

Was this helpful?

Thanks!

TAGS

Community showcase

Atlassian Community Events