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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • 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

Automation for Jira - Automatically Add Label to Stalled Tickets

Hi Automation Community!

I'm trying to figure out a way to automatically tag tickets that are stalling in our downstream release process.  I need help understanding if this is feasible to solve using Automation for Jira and if yes, a recommended way of proceeding.

 

User Story:

As a Release Manager,

I want Automation for Jira to add a custom label to any Jira issue that has sat in our Jira Workflow Status "Ready for Pre-Prod" for 5 calendar days,

so that I can quantify and measure the impacts of downstream dependencies.

 

Thanks in advance for your support and help!

1 answer

1 accepted

2 votes
Answer accepted
edwin vasquez Community Leader Feb 09, 2020

Hello @Jack Arndt ,

This is possible with Automation for Jira and after some testing I was able to accomplish what you asked for.

What you need to do is create a rule that will run a trigger (I would suggest scheduled everyday, at start of day), search for issues matching your query, and then edit the issue to add the label. This is the rule I created, I set my trigger to Manually triggered so its easier to test.

trigger.pngand this is the JQL I used to find those issues.

project = "Sample Project1" AND status = "In Progress" AND NOT status changed after startOfDay(-5d)

 

As you can see, there is no labels prior to me manually running the rule.

trigger2.pngAfter running the rule...

trigger3.png

I would suggest to also create a rule that will remove the label when the issue is transitioned to any other status. I hope this helps and answers your question. Let me know if you need any clarification.

edwin - i came on this post when working on a similar problem. But what I found is that the rule as you set it (which is also how I initially solved it) removes existing labels.  Essentially the 'edit field' action seems to replace the field value, which with labels is not always what you want.

If anyone has a way to _add_ a label without affecting existing labels, I'd love to know...

 

Or if other people are not seeing this function have the same effect, that would also be great to know...

Like edwin vasquez likes this

ah!  I figured it out.

When you use the Edit Field action, there's a text field for entering the new value.  To the right of that field there's an elipsis overflow menu icon.  Clicking that icon gives you options for adding or removing explicit values from the field, instead of just replacing the field.

 

@Jack Arndt you might want to update your automation rule to avoid losing label data

Like # people like this
edwin vasquez Community Leader Feb 21, 2020

Thanks for Sharing @Alex Bernardin 

Suggest an answer

Log in or Sign up to answer
TAGS

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