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; } } }

Sprint Name= Done+1

Andrea Sloan

When I hover my mouse over some done Sprint Issues on the Sprint field, I can see what Sprint this issue belonged to. However on the display the Sprint field displays with a "None +1" and not with the actual Sprint name value. It appears this only displays like this for done issues as I do see display Sprint name for open issues. Why is this happening and how can I resolve it?

Accepted answers

Prachi Bolar

Hi @Andrea Sloan ,

Welcome to community

I understand this behaviour can be confusing and there is a feature request logged for this

https://jira.atlassian.com/browse/JRACLOUD-90916

The explanation from the FR

The Done work items in the completed sprint display as none +1 in the sprint field, thus causing confusion to the user. Instead, it should be displaying the sprint name it was part of directly

The jira-123 work item was part of sprint X.
The work item Jira-123 was done or completed and sprint X is completed.
You start a new sprint Y.
Here the work item Jira -123 ticket status is Completed and as the sprint is Completed and not an Active Sprint, the sprint field in that work item will be set to none + 1 as it is not a part of any active sprint currently.
The +1 annotation is shown to remind us that this work item was part of a previously closed sprint. If you click on +1 it will show you the details of the sprint the work item was part of.
If you add this work item Jira -123 to any other active sprint that says sprint Y, then it will display as sprint Y + 1. Here +1 indicates it was part of the previous sprints.
Once you close Sprint Y, the work item Jira -123 will be displayed as none +2. Here +2 indicates it was part of 2 sprints.

Thank You,

Prachi

All comments

Tuncay Senturk _Snapbytes_

Hi @Andrea Sloan

I'm not 100% sure but it may be because of the issues that are associated with multiple Sprints (for example, an issue was started in one Sprint but completed in a later one). The most recent active Sprint is displayed by default. For completed issues, Jira collapses this field to show something like:

"None +1" or "Sprint 3 +1"

(where Sprint 3 is the sprint name, and +1 indicates there's one more sprint the issue was part of.)

If it says None +1, it means the active Sprint is no longer present or available (e.g. deleted or no right to see).

As I mentioned, this is what I think the cause is, take it with a pinch of salt.

Dirk Lachowski_b0vz9b

Read it as „part of one older sprint but not of any currently active one“

Prachi Bolar

Hi @Andrea Sloan ,

Welcome to community

I understand this behaviour can be confusing and there is a feature request logged for this

https://jira.atlassian.com/browse/JRACLOUD-90916

The explanation from the FR

The Done work items in the completed sprint display as none +1 in the sprint field, thus causing confusion to the user. Instead, it should be displaying the sprint name it was part of directly

The jira-123 work item was part of sprint X.
The work item Jira-123 was done or completed and sprint X is completed.
You start a new sprint Y.
Here the work item Jira -123 ticket status is Completed and as the sprint is Completed and not an Active Sprint, the sprint field in that work item will be set to none + 1 as it is not a part of any active sprint currently.
The +1 annotation is shown to remind us that this work item was part of a previously closed sprint. If you click on +1 it will show you the details of the sprint the work item was part of.
If you add this work item Jira -123 to any other active sprint that says sprint Y, then it will display as sprint Y + 1. Here +1 indicates it was part of the previous sprints.
Once you close Sprint Y, the work item Jira -123 will be displayed as none +2. Here +2 indicates it was part of 2 sprints.

Thank You,

Prachi

Andrea Sloan

Thank you, Prachi!

Chelsea

Thank you for sharing this info: https://jira.atlassian.com/browse/JRACLOUD-90916

I agree, this is quite annoying behavior. Jira should retain last active sprint for the work item, instead of updating to "None" once the sprint is closed. This is losing visibility, unless you hover over each work item's sprint individually.

Moving a work item to sprint "None" does not make any sense to me. Why would someone want that behavior?

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