There is a peculiar issue observed when rearranging idea cards in the Roadmap view

Question

Hi team,

There is a peculiar issue observed when rearranging idea cards in the Roadmap view. Not sure it is a bug or some unknown limitation. Here are the things we did.

* The "Autosave" functionality is disabled.
* The Sort is set as "View Rank", and there is no field specified for sorting.
* The user is licensed "Creator" access without "Manage View" permission.
* The user attempted to move the target idea card from the bottom to the top within the same column of the Roadmap View. However, this action resulted in an unexpected error and failure.
*

* Regarding the note, the user refreshed but the reordered issue card were back to previous sequence.

Not sure if anyone else encountered this issue, could you please help to take a look if this is normal or somewhat bug?

Thank you.

Tanguy Crusson · Answer

@Andrea Egert the root cause of the issue is a bug when a project administrator has created a project role which doesn't have "manage views" permission, and users with that project role try to do the following:

* Reorder ideas in a view with "View rank" enabled (as in the ranking of ideas is specific to the view, not shared with other views in the project)
* Reorder ideas in a timeline view

We're going to fix this.

In the meantime, you can ask your project admin to give you "Manage views" permission and it will work fine.

Andrea Egert · Answer

Hi @Rohan Swami our PMs used to be able to stack rank (sort within their otherwise locked-down JPD views) and are expected to do so as part of our quarterly planning motion. Not having this option due to a bug is a massive blow to our JPD / Atlassian tool stack integration journey (discovery, planning, delivery & launch). I'd, therefore, like to escalate this bug. We don't have an effective workaround and wouldn't consider this an edge case, esp. since we need to lock down views in JPD so PMs don't disrupt each others' work when they change views.

Rohan Swami · Answer

@Leo LI we've identified the bug here and it's on our backlog to fix it. Heads up this isn't a high priority for us as this unique combination of permissions is a rare edge case so I can't offer a timeline on when it will be fixed.