Some stories dissapear after moved from NextGen to Classic

Burhan Mubarok July 14, 2020

I have a project in Classic mode, I moved from NextGen type to another Classic project in bulk, then the stories disappears from active sprint and also disappears from the Backlog. But, I still can find it on the advance search result. It only works well once I remove any epic from the stories before moving that stories in bulk. Why not removing the epic automatically once we move those stories if it's not supported on the project target?

1 answer

1 accepted

0 votes
Answer accepted
Bill Sheboy
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.
July 14, 2020

Hi @Burhan Mubarok   -- Welcome to the Atlassian Community!

The issues are not showing because the moved-to project (target) filter is preventing them from showing.  If they are showing in the backlog, but not on the board, it could instead be an issue of status mapping to the board or the board sub-filter.

When you bulk moved them, the reason the epic was not cleared is because you did not clear the field.  JIRA would not clear the field by default because some teams might need an epic that is in one backlog, but has work items in multiple different projects to support it.

When making a change like you note (to/from Classic and Next-Gen), consider doing that before a sprint starts.  That will reduce the chance of issues that disrupt reporting on the sprint later.

 

Best regards,

Bill

Burhan Mubarok July 14, 2020

owh I see, noted & thanks.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events