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

Why some of the tickets are disappering from the sprints preview in the backlog

Joanna Nejfeld

Hi,

can I ask for help figuring out why I can't see some of my tickets in the backlog preview after adding them to a specific sprint? I made sure that:

they have a proper issue type associated with the workflow setup for my project
a proper status that is mapped in the columns in the board settings
a proper sprint assigned

It started happening a couple of days ago, it used to work normally.

I was able to identify that it happens only when the issue is in the status that finishes the sprint (status mapped to the last columns in the board settings)

1. This is how statuses are mapped in the columns

columns and statuses mapping.png

2. Filter used in board settings

project = DDA AND issuetype in ("Dev Story", "Dev Task", "Dev Bug") AND labels = WTT_Dev ORDER BY Rank ASC

3. Exemplary ticket preview (it's not visible in the screenshot but the issue type is Dev Story)

Ticket created for jira workflow testing - JIRA 2023-08-01 17-14-50.png

4. When I have this issue in one status before (in QA) it's displayed properly (disappears after status change to Ready for Stage Release)

backlog view.png

Accepted answers

Bill Sheboy

Hi @Joanna Nejfeld

What do you mean by "backlog preview"? Do you mean the backlog view for the current sprint, a future sprint, or something else?

Please post an image showing the view you mean, and which does not show the issue you are describing. That may provide more context for the community to help. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Joanna Nejfeld

What do you mean by "backlog preview"? Do you mean the backlog view for the current sprint, a future sprint, or something else?

Please post an image showing the view you mean, and which does not show the issue you are describing. That may provide more context for the community to help. Thanks!

Kind regards,
Bill

Joanna Nejfeld

hi Bill, I mean backlog view for the future sprints (I used a newly created one for the sake of sharing the example). The screenshot of it is shared above under point 4.

Bill Sheboy

Thanks for that information.

Once an issue is completed for the sprint (i.e., moved to the last column of the board), it is done...and so I would not expect it to appear in a future sprint.

Joanna Nejfeld

in this case not really. The last column on the board isn't definite. Ready for Stage doesn't equal to done. The workflow continues to the UAT stage which is set up as a separate board.

Also, if that was the case then it shouldn't work at all but it did (sometimes we needed to defer some o the tickets into the next sprint/-s at the ready-for-stage status and it used to work and display those tickets in the backlog view normally

Bill Sheboy

For a sprint on a Jira board, the last column is "done". When there are other boards in the same project, their respective board layout determines doneness. These are aspects of the Jira tool, regardless of how a team defines its processes.

Was the issue in the last column on the board when the sprint completed?

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