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

Issue showing up on Sprint board but is actually in Backlog

stephan.lewis

I have a group of issues that show up on the current sprint board but are actually not supposed to be in the Sprint. They are actually in the backlog.

I can't figure out a way to remove them from the current sprint. Normally I would just go to the backlog view and be able to drag them from the current sprint into the backlog - but they are already in the backlog.

Never seen this before

Accepted answers

All comments

Jordan Richter_agw0n8

Hi Stephan.

Could you post a screenshot of how this looks? Have you tried clearing the Sprint field on individual issues to see if that removes them from the Sprint?

Thanks,

Jordan

stephan.lewis

Actually I have a correction. I thought that the issues were already in the backlog - but that was not the case. I just happened to have 8 issues in the Sprint and 8 in the backlog and assumed that they were the same. This wasn't the case.

So the real problem is that I have 8 issues showing up in a Sprint board, but when I go to the Backlog view they aren't there.

Regarding clearing the Sprint field on the individual issues I don't have that option. I had never seen that happen before. I was thinking that it was a permission issue but haven't had any success trying different permission screens.

stephan.lewis

I took a look at other issues on the board and depending on the person determines if I have the option to clear the sprint field.

Based on this I went to see what was common between the ones that had the option and those that didn't.

I thought it was that I needed to add the people to the project - but that didn't work.

stephan.lewis

More detective work, I was able to determine that is limited to 4 users and 1 specific project.

Haven't been able to pinpoint the root cause.

I still believe that it is a pemission issue - just can't figure it out

stephan.lewis

Problem solved - they were sub-tasks!!!!

Hate sub-tasks ...

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