Ticket moved to top of the backlog does not stay at the top of the backlog

[Andy Roth]

We are seeing an issue in a scrum backlog where a ticket moved to the top of the backlog via the context menu moves, but on refresh the ticket moves to somewhere in the middle.

STR:

1. From a scrum board backlog view, right click on a ticket and select 'Top of Backlog'

> the ticket moves to the top of the backlog

2. Refresh the page

> the ticket moves to somewhere in the middle of the backlog

ER: The ticket remains at the top of the backlog

Note: If we use the keyboard shortcut (S+T) the issue does not happen

[Trudy Claspill]

Hello @Andy Roth 

I have seen this same issue reported in two other posts.

I'll ask you the same questions.

You already answered one of them - you are using a Scrum board.

Is it for a Company Managed project or a Team Managed project?

I haven't been able to recreate this problem in either a Company Managed Kanban board or a Team Managed Scrum board.

[Andy Roth]

It is a company managed project.

[Jeroen Poismans]

Hi Andy,

I was able to reproduce this behaviour. Seems like if you move issues with "Top of Backlog", after refreshing it places it at the top, but after the issues you have previously done this with.

Example:

• s1
• s2
• s3
• s4

=> Move s4 with "Top of backlog"
=> Refresh (seems fine)
=> Move s3 with "Top of backlog" (appears at the top)
=> Refresh

=> s3 is now suddenly below s4

Is that the behaviour?

Possible that this could be a bug.

[Andy Roth]

Hi Jeroen

Not quite.  For us, the issue happens on the first refresh. The ticket moves down many spots, to somewhere in the middle of the backlog.

The backlog contains over 800 issues, and I wonder if that is contributing to this?

[Jeroen Poismans]

Yes, is exactly the behaviour and is a bug. Other users are experiencing this too, so best to open a support case:

https://support.atlassian.com/contact

Regards!

[Andy Roth]

Ticket created: https://support.atlassian.com/requests/JST-870863/

Thanks!