Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Automation: Label change when shifting between teams boards

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

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

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

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.

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

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
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

226 views 7 7
Read article

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