Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

how to change issue status when its moved onto the board

We are not using sprints, and have a Kan Ban board that we pull work onto as needed.

We have a Backlog state and a ToDo state.  When I move a card from the backlog and put it on the board, I would like to automatically change the state from Backlog to ToDo.

Is this possible?  I don't see any automation or workflow triggers based on moving cards to the board.

2 answers

1 accepted

0 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 10, 2022

Hello @jolyont 

Are you working with a Team Managed project or a Company Managed project?

With a Team Managed project there is currently no way to detect that an issue is either "in the backlog" or "on the board". Issues in either location can be in any of the allowed statuses.

With Company Managed project Kanban boards that use a Backlog, the Backlog displays only issues in the status assigned to the Backlog, while the board displays on issues in the other valid statuses. In that case changing the status of the issue is what moves the issue to the board.

We're using team managed projects.  We also want to have issues in the backlog with a variety of statuses, so I'm not sure it would work with Company Managed projects either.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Nov 11, 2022

With a Company Managed project you can map multiple statuses to the "backlog" group. Each status is either mapped to the backlog or to a column on the board.

For a Company Managed project the Backlog screen shows a list for issues in the "backlog" and a list for issues that are in the left-most column of your board.

In this example I have two statuses mapped to the backlog, and In Progress is the left-most column of my board that has a mapped status.

Screen Shot 2022-11-11 at 2.30.52 PM.png


So, in the Backlog screen the "backlog" list includes all issues in either the Backlog or Selected for Development status, and the upper section shows the issues in the left-most status of my board - i.e. In Progress.

Screen Shot 2022-11-11 at 2.31.16 PM.png


The upper section will show only the issues in the left-most column of your board where Statuses are mapped. If you have multiple Statuses mapped to the left-most column then issues in all those statuses will show in the upper section. The title for that section will be the same title used on the left-most column in your board.

This looks useful.  I'll have to have a play with it. Thanks!

Same issue, so frustrating at the utter lack of functionality in Team Managed projects. I can do all this fine in Company Managed projects but Team Managed is just broken. It's one redeeming feature is that it sandboxes a project to a team so they don't break anything for other projects, every single other aspect of Team Managed projects just feels broken or not implemented. Seems pretty clear Team Managed is a dead duck with little meaningful development going on, I can only assume Atlassian have been beavering away all their Dev effort on a "New Next Next Gen" version to replace Company Managed and Team Managed, that or they've just given up trying to improve the product.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events