Automation - creating a rule

[Julia Roesschen]

I wish to automize the following: The tag within an issue changes automatically when I move the issue from the backlog to the board, vice versa.
E.g. as long as the issue is in the backlog I want the label "backlog" and as soon as it is being moved to my board I want it to change the label to "board".
I am looking for an appropriate trigger for this automation.

There is the option to use "Issue transitioned" so that the rule is applied whenever I transition my issue through the workflow e.g. move it from "To Do" to "In Progress".

However, since issues are being moved back and forth between Board and Backlog, it could happen that a "in Progress" issue is moved back to the backlog, and since the rule is triggered by the workflow only, the tag would not change accordingly.

[Jack Brickey]

I am not following your ultimate goal here. Why do you need to have a label for backlog vs. board? Once I understand the need I might be able to assist with automation.

[Julia Roesschen]

Hi Jack,

I use the labels for a Gadget in a JIRA Dashboard that calculates and updates the numbers of active issues in the board vs. issues held in the backlog.

At the moment, I manually replace the labels in the tickets whenever they are being moved between the board and backlog. Automatic changing of the labels would save me the time and work and I would still be able to see the correct numbers in my dashboard.

[Jack Brickey]

i see. interesting. 

Ok so I think you are trying to cover the case where say you complete a sprint and incomplete issues return to the Backlog or Next sprint and you want to replace the 'active' label with 'backlog'. Is that correct? If so, I'm thinking that you need to incorporate some conditions into your automation, and/or maybe another rule. Maybe, trigger on sprint completing and finding any issues that are not done and not in an active sprint and the label is 'active' then set to 'backlog'. I would play with this and test something out but at the moment I am facing a very ugly bug in my instance where I cannot access any boards of any type.

[Julia Roesschen]

We're currently not working in sprints so the return of issues into the backlog happens kind of on-demand, based on team decisions. So the whole automation would have to be triggered solely by the manual move to the backlog/board. But you are right, looking for some kind of rule as a condition would make sense. I will try around a bit! Thanks for your input and good luck fixing the bug!