nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Proper way to cancel issue that is scheduled in a sprint?

Jay Smith

When an issue is scheduled in a future sprint and it is determined that it should be canceled should it be removed from the sprint? Will this keep it from showing on a sprint report as completed outside of the sprint?

If so, what is the proper order?

Clear Sprint Field
Cancel issue

Cancel Issue
Clear Sprint Field

Thanks in advance,

Jay

Accepted answers

Jack Brickey

You mention “future sprint”.

If indeed the issue is not in an active sprint then - drag out of the sprint (or remove the sprint from the field) and then cancel the story.

if it is in an active sprint then simply mark the story done with resolution of won’t do or canceled and let it fall thru the sprint naturally.

All comments

Rhett_gmys65

My recommendation:

1. Clear Sprint Field
2. Cancel Issue

You could look into some automation that clears any future sprints from an issue that's cancelled.

Pete Singleton

I believe if you clear the sprint field then it will be considered a change of scope for the sprint. Best to cancel/resolve the issue with a "won't do" or withdrawn resolution.

Jack Brickey

You mention “future sprint”.

If indeed the issue is not in an active sprint then - drag out of the sprint (or remove the sprint from the field) and then cancel the story.

if it is in an active sprint then simply mark the story done with resolution of won’t do or canceled and let it fall thru the sprint naturally.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud