"Backlog" status tickets displaying in Scrum Board's 1st column

[M Carolyn Eckstein]

We have multiple projects set up identically with the same simple filter:

• Company-managed
• Scrum Board
• Same workflow, issues schema, etc.

In existing projects, we have both "To Do" and "Backlog" statuses mapped to the 1st column of the active sprint's Board, labeled "To Do". When I create a new issue, it automatically places it into the Backlog, with the status "Backlog". It does not display on the active sprint's Board in the 1st column despite being mapped there (see screenshot). This is how I've always used Jira for probably over a decade.

In our new project with identical Project and Board Settings, when I create a new issue, it automatically places it into the Backlog with status "Backlog" — but it visually displays on the active sprint's Board in the 1st column, together with the "To Do" status issues. "To Do" status (for us) indicates budget is approved & assignee is allowed to start working on the task.

If I un-map the "Backlog" status so that it's not mapped to the 1st column, creating new issues will say (error) that I've successfully created a new issue but that it's not visible (see screenshot).

How can we get the Backlog to operate the way it does in all our other Scrum Board projects? I'd prefer not to add another column for "Backlog", and also don't want to change this Board to Kanban so that we can plan out Sprints (I also don't agree KBs should ever have Backlogs if they're following true Kanban methodology, but that's a discussion for another day...).

Thanks in advance!

[Trudy Claspill · Accepted solution]

Hello @M Carolyn Eckstein 

For a Scrum board issues will display in the board view only when:

1. They are assigned a status that is mapped to a column, and
2. The issue is assigned to an Active Sprint

When you create an issue in a Company Managed project, the issue it will not natively be assigned to any sprint. You could use an Automation Rule to do that or a Post Function in the Workflow Transition to do that.

If you are seeing issues getting automatically added to sprints upon issue creation in a Company Managed project there are a few things to check.

1. Is the Sprint field visible in the Create Issue dialog, and is the user creating the issue setting that field?
2. Is an Automation Rule running against that project and automatically assigning newly created issues to the current active sprint?
3. Is there a Post Function in the Create transition in the Workflow that is assigning the issue to an Active Sprint?

Also, what steps are you executing to create the issue? Are you using the Create button in the menu bar?

What type of issue are you creating? Is it a standard level issue (i.e. Story or Task) or is it a Sub-task or an Epic?

Lastly can you confirm that your new project is a Company Managed project and not a Team Managed project?

[M Carolyn Eckstein]

1. Used the +Create blue button along top to create all issues.
2. Issues I created for testing this problem were Tasks only.
3. We have no automation rules set up.
4. There is no Post Function in the workflow that assigns it to the Active Sprint.

It's now working. No idea what has changed, other than time has passed since I looked at it this morning. I double-checked, and the Sprint field is still blank (just as I left it when I created 2 Task issues this morning).

Is it Friday yet?  🙃

Thank you for your help! Hopefully this won't happen again. I know there have been a lot of code updates rolled out recently. Who knows, maybe there was a quirk hiding in there somewhere.