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

Move tickets from backlog to kanban board when status changes

We are using a simple team-managed Kanban board for helpdesk level tickets. Currently we are using the backlog feature. New tickets are put into backlog, which is desired. I'm looking for a way to automatically move the tickets out of the backlog to the kanban board as soon as the status changes from New -> any other status.

I believe that the trigger "Issue transitioned" is the right things, but I cannot figure out what the correct action would be. So far, all things tried just failed.

Any suggestions are appreciated.

1 answer

1 accepted

3 votes
Answer accepted
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2022

Hi @Paul Williams and welcome to the community!

I'm not quite sure I understand what you mean about moving from backlog to Kanban when the status changes.  Typically when you change the status, that moves it from the backlog to the Kanban.  Do you have multiple statuses mapped to the backlog? 

Maybe you can share a screenshot of your Columns and Statuses configuration.  You can locate it by navigating from the top right ellipses:


Hi Mark! Thank you for checking on my question.
I've attached two screenshots of our project. The first one is the Columns and Statuses. As far as I'm aware, we do not have any status mapped to backlog.

Screenshot 2022-10-25 at 17.07.02.png

The second picture shows what I want to achieve.

When I change the status of any ticket in the backlog part, I would like it to move automatically to the board part so that it becomes visible on the kanban board. This does not happen as of now.

Screenshot 2022-10-25 at 17.08.06.png

Like Jacob Rose likes this
Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2022

So, the way you'll want to handle this is:

  1. Drag your first status (New Tasks, Start) to the backlog column
  2. Remove the New Ticket column

This will ensure all new tickets show up in the backlog.  Then you'll be able to simply drag them up to Do-It which will have it appear on the Kanban.

When you say "backlog column" do you mean the one with the fishing net? It reads:

Drag and drop a status here to hide it from the board and backlog. Issues with these statuses won’t be visible.

That also removed the tickets from the backlog. I'm a bit confused right now.

I just compared with a company-managed project, and that has a backlog column indeed where you can map a status to backlog. It seems that this feature does not exist in a team-managed project. Another reason to move from team to company managed project for our Helpdesk board it seems.

Mark Segall
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 25, 2022 • edited

Apologies - My mind was on company managed with my response. 

So, by default the backlog is just a backlog.  New issues should arrive there and then as you drag them up to "Board", they will appear in the first column of the Kanban.  

Unfortunately, there's no way that I know of to have the To Do status automatically linked to the Backlog so that you could remove it from the Kanban view as you would in a company managed project.  For whatever reason, it's completely separate.

Like Jacob Rose likes this

Thanks again for checking and clarification. I'll thing of porting our current function of the team-managed project to a company-managed project. 

Like Mark Segall likes this

I have this very same problem. I don't understand why there's no action available in Jira automation for team-managed projects that would allow tickets to be transitioned automatically from the backlog to the board when they're assigned or when someone marks them as being in progress.

Right now, we often lose visibility of tickets that people are actively working on simply because they didn't go to the backlog and manually send them to the board.

It seems like needless toil to require folks to manually move backlog tickets to the board when they're taking actions that imply that a ticket is no longer backlog.

I'd recommend to migrate to a company managed project if possible. Migration is super easy and it has no downsides if you have admin permissions on a product level. 

We never looked back tbh...

Hi, Paul.

Unfortunately, we don't have company-wide admin rights.

I can't understand why Atlassian would provide a workflow management product where basic functionality is inaccessible to automation when teams manage their own projects in a larger organization.

It's a bit maddening!


Depending on your workload and team structure, you could think about a dedicated backlog review meeting and sort your backlog. Then ask your team to work top-to-bottom and explain how to drag the tickets to the board. Or use the backlog as a supervisor planning field and tell your team to only work on what's in the board. You / the team lead would then be able to decide what's being worked on by moving work onto the board. 

That way you have a clear line of expectation for your team. They don't need to worry about what's in the backlog and you can control the workload.

Obviously this strongly depends on the work and team environment. 

I can fully understand your frustration but believe me, it is just not worth the time. Adapt, improve, overcome ;)

Like Jacob Rose likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events