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 None +1

marie.mitchell

Hello,

How do you remove 'none +1' from the Sprint field in tickets?

We have several tickets marked as 'ready', which must have been assigned a sprint at some stage but then removed (hence the none +1, +2 etc).

They are not disrupting the sprint board, but leading to inaccurate data by suddenly pulling in to the Sprint Health gadget, so it looks like we have pulled in more tickets than we have.

Thanks,

Marie

Accepted answers

Bill Sheboy

Hi @marie.mitchell

I saw an older ticket related to this symptom which was resolved years ago. People have started commented on it again, and I suggest submitting a new defect to Atlassian support:

https://support.atlassian.com/contact/#/

Once you hear from them, please post back here what you learn. Thanks!

Best regards,

Bill

All comments

Bill Sheboy

Hi @marie.mitchell

I saw an older ticket related to this symptom which was resolved years ago. People have started commented on it again, and I suggest submitting a new defect to Atlassian support:

https://support.atlassian.com/contact/#/

Once you hear from them, please post back here what you learn. Thanks!

Best regards,

Bill

marie.mitchell

Thank you @Bill Sheboy - i shall do that and hopefully report back soon!

Best wishes,

Marie

brenda_banderschaper

@Bill Sheboy experiencing the same and appears the link posted on Mar 9 isn't functional. Are there any insights you can provide? Thanks in advance.

Bill Sheboy

Hi @brenda_banderschaper -- Welcome to the Atlassian Community!

Which link do you mean? I tried both of the ones that I provided and they worked for me.

In the old defect, there are several new posts about people seeing this problem, so I suggest if your are on a paid Jira license, to ask your site admin to submit a ticket to Atlassian support. They have access to logs we (customers) do not and so perhaps can help uncover this. Thanks!

Kind regards,
Bill

Kamal Manohar

experiencing the same and appears that when we close the existing sprint without resolving/ moving the existing Task/Stories to the next sprint. The task/ Story will move to the backlog and the sprint name will be "None+1". Correct me if I am wrong.

Bernie.Figueroa

Afternoon all, I'm looking to resolve the same issue. I see this was reported previously and then again in 2021. Was there any resolution?

Brian Modra

I'm also getting "None + 1" tickets in the backlog. They are from the previous (closed) sprint.

This has suddenly started happening, so I suspect a bug

Brian Modra

I wondered if that was what happened, but I'm seeing tickets with "None +1", "None +2" and "None +3" - suddenly. I definitely did not see any of these before sprint planning of this current sprint,

Brian Modra

I have worked around this by adding a quick filter:

Screenshot 2024-06-26 at 3.47.12 PM.png

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud