Automation: Label change when shifting between teams boards

Joshua Buchanan June 9, 2021

Hey all,

We run a single project for a large product, with multiple teams utilizing different boards. 

As we have some tasks running through from team to team, we use clear labels to define which Team this is sitting with, so that everyone is in the know & and our boards are kept (mostly) clean.

 

Though the challenge we are facing is that people are forgetting to remove and change over labels, our data is getting skewed. 

 

Is there a way to automate the process, so for example if a task goes:

To 'Board A', it removes the last label and assigns 'Label A' (associated with that current board)

If the task then needs to get moved on to 'Board D', it would then remove 'Label A' and assign 'Label D(associated with that current board).

 

Hopefully, that makes sense? 

 

Thanks in advance!

1 answer

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 9, 2021

Hi @Joshua Buchanan 

That sounds possible to do with Automation for Jira rules. 

You note using multiple boards for the different teams; what is different in the team filters to support the shift from one team to another (e.g. Component = Team1 vs Team2)?  Using that information, you could trigger a rule on that field changing and then update the labels.

Best regards,

Bill

Joshua Buchanan June 10, 2021

Hey Bill,

 

Thanks for messaging back :)

Great answer, the difference would be the naming convention - eg. optimization vs experimentation - if that makes sense? 

 

Cheers,

 

Josh

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 10, 2021

Josh, what do you mean by "naming convention"?  Are you changing the summary (title) of an issue based upon the team working on it?

If so, you may want to consider using a field like component or label instead to reflect such a change of teams.  Those are less likely to be impacted by typos for changes.

Joshua Buchanan June 14, 2021

Hey Bill,

 

Sorry for any confusion - what we are changing is simply the Label. By changing this, said ticket then gets pulled into a different board. 

 

Does that make sense? 

 

Cheers,

 

Josh

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
June 14, 2021

Hi, Josh. 

That makes sense: you are using labels to manage on which team's board the issue appears (based upon the filters).  You should be able to edit the label directly to move issues or create an manually triggered automation rule to do so...although that would seem more complicated than just changing the label.

Am I missing something about your use case?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events