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

Automatically change the status of a story when moving from Backlog to Board

Gérard Françon_krt4s3

Hello,

Using a team-managed project, setup as Kanban, we have the Board and Backlog:

Is it possible to automatically change the status of a story (bug, tech debt, etc.) from Backlog to To Do when we move a story from the Backlog to the Board?

Thank you.

Accepted answers

Vikrant Yadav

Hi @Gérard Françon Welcome to Atlassian Community!

Unfortunately, it's not possible to set up automation for Team Managed project when issue to Board from backlog. You can only setup for Company Managed project or Scrum Team Managed Project.

All comments

Vikrant Yadav

Hi @Gérard Françon Welcome to Atlassian Community!

Unfortunately, it's not possible to set up automation for Team Managed project when issue to Board from backlog. You can only setup for Company Managed project or Scrum Team Managed Project.

Gérard Françon_krt4s3

Thank you @Vikrant Yadav for your answer.

Vikrant Yadav

@Gérard Françon Thanks for your response!

Kindly accept the solution, if it works for you. As it helps others looking for same solution.

Bill Sheboy

Hi @Gérard Françon -- Welcome to the Atlassian Community!

Adding to the answer from @Vikrant Yadav ...

There does not appear to be an event visible to automation rules when issues are moved to / from a team-managed project board, and so rules cannot detect this change. It does not even show up as an issue update!

A convoluted workaround is using a scheduled trigger rule to check which issues are on the board, and then transition any which are in "backlog" to your first status (e.g., "To Do"). For example:

trigger: scheduled, such as once per day
action: Send Web Request, calling the REST API function to get the issues on your board: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/#api-rest-agile-1-0-board-boardid-issue-get
action: create variable, using text functions, extract the keys of any issues in a backlog status
branch: on JQL to the issues in the variable
- action: transition to the first status on your board

A major problem with this rule is automation usage. Each execution will count toward monthly usage, and you appear to be on a Free license level. If this rule ran too often it would quickly consume your 100 count limit. If you ran it daily, it may not be often enough to help avoid the manual step to just change the status.

Kind regards,
Bill

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud