Single status not migrating issues from sprint to sprint

philipf
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 21, 2024

Using Jira cloud, when we end one sprint and start another, all undone tickets are migrated to the next sprint.

However, tickets that are located in a status we call 'ready for QA' (in progress type), does not migrate the tickets over and sends them to the backlog.

Is there any reason that all of the other statuses migrate when we end and start a new sprint, and this one status does not?

We are not seeing this problem on any other board or workflow.

1 answer

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 21, 2024

Hello @philipf 

Does your board scope include multiple projects? Are the issues in the 'ready for QA' status from a different project than all the other issues that successfully move to the next sprint?

Do you have any Automation Rules in place that could be affecting these issues?

philipf
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 22, 2024

I was an idiot, i realized people had multiple boards so when I checked the settings, the one board was okay, and the other boards needed to be mapped.

All good, and thank you.

Suggest an answer

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

Atlassian Community Events