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

Next challenges

Recent achievements

  • Global
  • Personal


  • Give kudos
  • Received
  • Given


  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Default creation state on Kanban board should use the 'Backlog Kanban' state

I have a project with 3 boards globally like this :

- Dev Scrum board (Dev todo, Dev in progress, Dev done)

- IT Kanban board (IT todo, IT in progress, IT done)

- Test Kanban board (Dev done and IT done, Test in progress, Test done)

The project workflow is set so that when we create a new issue, it has 'Dev todo' state.


We also have a 'IT backlog' state to allow IT users to maintain their backlog and we have set this state as 'Backlog Kanban' in the columns definition of the IT board.

IT Kanban.JPG

When we create a ticket in the IT backlog, the state is 'Dev todo', we expected it to have 'IT backlog' state.


Is there a way to do this ? (automation, feature...)


1 answer

1 accepted

0 votes
Answer accepted

Hi @Bruno Gasnier,

I understand that all boards are associated with the same Jira project. It is important to understand that issues are created inside a project, while a board is essentially a view on those issues. Or in other words, you always create your issues in a project, never in a board.

When creating an issue, apart from choosing a project you also have to select the issue type (story, task, bug, ...) you want to create. An issue type can only have a single workflow within a project, but each separate issue type can have its own workflow.

Having said that, if a different workflow is required for different issues in the same project, the usual way to solve this is to set up different issue types - each having its own workflow. That way an IT task can have a different initial status than e.g. a Story that goes to the dev team.

Have a look into the documentation on:

Ok, I will create a new issue type for IT tasks.

Thanks !

Suggest an answer

Log in or Sign up to answer
Site Admin

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you