nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Mergen Yazılım A_S_

Hi,
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.

Accepted answers

Shannon S

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:

JSWSERVER-13530

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

Thank you!

Regards

Shannon

All comments

Shannon S

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:

JSWSERVER-13530

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

Thank you!

Regards

Shannon

Mergen Yazılım A_S_

Hi,

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.

Shannon S

Thank you for confirming, Mergen!

Take care and have a pleasant rest of your week.

Regards,

Shannon

floriantrautmann

Hi,

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

Can you please help us?

Regards

Florian

apr080

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

Shannon S

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.

Regards,

Shannon

apr080

Hi Shannon,

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

Regards,

Abhilash

Shannon S

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.

Regards,

Shannon

Jack Liu_6c2ays

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

Shannon S

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.

Regards,

Shannon

Roy Schumacher

we are using

v8.2.3#802003

and the issue is still present.

anyhing we can do?

Shannon S

Hello Roy,

The original case was fixed in 7.2.7 or higher, so definitely if you're still experiencing it in 8.2.3, it needs to be reported to support.

I see that you have done that, so they will be able to have a look at your logs and determine the cause.

Please feel free to come back here and let us know if there's a new bug ticket people should follow, as it will help should anyone run into the problem in the future.

Regards,

Shannon

Johan Scholtz_laaegc

We are experiencing the same issue now with this and running DC solution running version 7.12.3.

However I must also add that we are experiencing sync issues between the Nodes, Could this also cause the issue whereby Backlog items are dragged to to the new sprint and then fall back into Backlog once you refresh.

Shannon S

Hello Johan,

Welcome to Atlassian Community! It's nice to meet you.

Roy raised a ticket earlier but it looks like we are still troubleshooting that at this moment, so I don't have an answer as to if this is a regression or a new bug.

I would recommend that you raise a ticket with the Support Team and link to this thread. They will then be able to proceed with troubleshooting and using your support logs in order to determine the issue.

Let me know if you have any trouble with that.

Regards,

Shannon

Divya TV

We see this problem on 8.13.12 Jira datacenter as well.

squizzypouet

Hi,
Same problem for me in my company,
However, we found out that removing the content of the "Fix Version" field allows to work around.

Srikanth Ganipisetty_0hsoyh

Issue still exists on v9.5 and raised a support ticket

Thanks,

Srikanth Ganipisetty

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-software