Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Closing Sprint caused some issues to go to Not Applicable

chris.reyes
chris.reyes
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.
Get recognized
August 1, 2019

I had a sprint that crossed multiple projects with some issues that were left in To Do state.  When  the sprint was closed, the issues went to "Not Applicable" for a particular project.  At first, I thought it was just issues that had sub-tasks assigned and were marked as done.  But now I'm being told that they were not.  Any idea what could cause this and how I can make it so that in the future when I close a sprint it doesn't move those issues to Not Applicable.  Thank you.

Answer
Watch
Like Be the first to like this
235 views

0 answers

Suggest an answer

Log in or Sign up to answer
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events