Issues moved from backlog to sprint return to backlog after page refresh

In our jira server, we use scrum. We are not able to move some issues to any sprint. When we move issue from backlog to sprint X, it seems everything is ok. But after page refreshing or opening backlog view on another browser, we see that it is still in backlog. When we open issue in detail, we can see its sprint field is filled by true sprint but in backlog view it is still seem in backlog. 

Any idea?

Thanks in advance.




3 answers

1 accepted

1 vote
Answer accepted

Hello Mergen,

Could you let us know what version of Jira Software you're running? It seems like it might be related to this bug:

However, this should have been fixed in 7.2.7, so please confirm your version.

Thank you!




Thanks for your quick reply.

I have searched but not found that bug report before ask question, sorry for that.

As you said, I checked the version and yes, it is 7.2.1.

After upgraded JIRA to 7.6.1, the problem has resolved.


Best regards.

Thank you for confirming, Mergen!

Take care and have a pleasant rest of your week.




same problem here. But we have realized that bug after updating our Jira from 6.x to 7.6..?

Can you please help us?



Hi Florian,

If that is the case, then it may have a different cause. I would recommend replicating the error, and having a look at the Jira Server Logs. See if you notice any errors there about what is occurring.



Thanks for your quick reply Shannon!

There are no errors in our logfiles. After reloading the "backlog" page the issue moves back from the sprint to the backlog. In the issue detail view, the right sprint is still selected. (same behaviour shown in the screen cast..)



There definitely should be something, so that's odd that there's no errors at all.

I'm going to create a support ticket for you so we can have a deeper look at your support zip. Please check your email in a few minutes for that ticket.



Have we got solution for this Since we are also facing the same issue.

Hi there,

The original bug was fixed in Jira 7.2.7: JSWSERVER-13530

The issue with Florian's case was that the Sprint field has a missing key via a customfield table. It may be that if you're already in Jira 7.2.7 that another field is missing that is expected.

Have you raised a support case for this? The team may be able to help you to determine what is expected, provided you'er already in Jira 7.2.7 or higher.



Hi Shannon,

We are using Jira 7.2.4 .Could you please suggest how to resolve this issue.




Hi Abhilash,

The issue is fixed in 7.2.7 and higher. I would recommend upgrading Jira to at least 7.2.7 or higher.

The Fallback method is the better route in this case.

Let me know if you have any issues.



Thank you Shannon for reply

I met the same problem now, any one have other suggestion or solutions?

Hi Jack,

The issue is fixed in 7.2.7 and higher. I would recommend upgrading Jira to at least 7.2.7 or higher.

If you are using a version higher than 7.2.7, then you will need to reach out to our support team and they can work with you to determine what the problem might be.



Suggest an answer

Log in or Sign up to answer
Community showcase
Published Feb 26, 2019 in Jira Software

How to prevent the propagation of unused project schemes, workflows & screens in Jira software

Atlassian ranks project attributes as the third most important factor impacting performance in the category of data. It’s not surprising, since project attributes are precisely the rules used to ma...

649 views 0 7
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you