Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,557,138
Community Members
 
Community Events
184
Community Groups

'Top of Sprint' and 'Bottom of Sprint' missing in Jira Cloud (they exist in Jira Data Center)?

As a Product Owner who wants to order his backlog and future sprints easily,

I find Jira Data Center has 'Top of Sprint' and 'Bottom of Sprint' when I right-click an issue, which makes reordering the backlog easier under certain circumstances

but I find Jira Cloud has no such 'Top of Sprint' and 'Bottom of Sprint' options in the right-click context-menu, which makes reordering the backlog more cumbersome (and prone to mistakes) (e.g. dragging an issue from the very bottom to the very top is more time-consuming, and error prone, than the simpler 'Top of Sprint' mechanism in Jira Data Center)

Knowing that the user-interface in Cloud and Data Center do diverge, does anyone know where 'Top of Sprint' and 'Bottom of Sprint' is in Jira Cloud as it is in Jira Data Center?

Or maybe this was a feature in Data Center that never made its way into the Cloud code-base for some reason... any insights?

1 answer

In Cloud you still have the top of backlog and bottom of backlog when right clicking an issue.

Schermafbeelding 2023-05-25 062331.png

A more dirty approach I have seen with clients is to create a sprint (which will never actually be started) and use it as container (example "most urgent bugs") fo tickets.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events