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

Workflow Column named "To Do", mapped to state "Selected for Development", but stories don't appear.

Jason Weddell

In our workflow columns, we've mapped the status "Selected for Development" to the column named "To Do". When I transition a story to "Selected for Development" it doesn't appear in our "To Do" column on the Kanban board.

I've checked our filters and made sure the board was published and there isn't anything to suspect stories of this type with this status shouldn't be visible in that column when transitioned from the backlog to this state.

In the image below, I feature screen clips of (upper left) the To-Do Column, (lower left) a story in the Selected for Development state, and (Right) the column section under the Board Settings showing the SFD status mapped to To Do, but the SFD status shows No issues. Over all, we have 6 issues in SFD state.
JIRA SFD TODO Issue.png

I'm unsure where to look to troubleshoot further.

Accepted answers

Nic Brough -Adaptavist-

Could you show us the workflow and the board filter?

Also, your status is cut off at differing points, so I'm wondering if we might be seeing the right one. Could you visit admin -> issues -> status, and go find the "selected for dev" status - look above and below it, are there others?

For example, I ran into a place a few weeks ago that had (a different status name, but I'll use yours as the example)

Selected for development
Selected for developers
Selected for developer

In this case, the user had simply mapped the wrong status into their columns, and because of the truncation in the config screen, not been able to see that they had the wrong one!

All comments

Nic Brough -Adaptavist-

Could you show us the workflow and the board filter?

For example, I ran into a place a few weeks ago that had (a different status name, but I'll use yours as the example)

Selected for development
Selected for developers
Selected for developer

In this case, the user had simply mapped the wrong status into their columns, and because of the truncation in the config screen, not been able to see that they had the wrong one!

Jason Weddell

Thanks for your reply!

Looking into that, we only have one Status with those characters, Selected for Development, and to throw an additional curveball into the mix, we can't delete the status from the workflow because JIRA claims there are issues in that status (there are) but the status itself reports zero. We're working in project Demo, so the error makes sense but the lack of visibility does not.

JIRA SFD TODO Issue 2.PNG

Nic Brough -Adaptavist-

Bother, that rules out that idea.

So, you're getting a delete error because the status has issues in it. They don't necessarily have to be in the project you are looking at! Projects can have different workflows, and someone else might be sharing your status.

Next step is a quick check of the issue data. Go to the issue navigator (simple or advanced search will both work for this), and search for just "status = selected for development" - don't limit it with anything else.

Ideally set the columns to be displayed to include either issue key (or just project), resolution and status - those are the only three that might help us out here.

Second thing to look at is your board's filter - what does that select for? And what do you get if it is used in the issue navigator?

Jason Weddell

Ha. The filter didn't have SFD selected. Everything but. Wild.

Thanks!

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