Automated labels?

I was wondering if there was a way to have JIRA automatically label issues based on some sort of criteria. I'm specifically looking for a way to label issues with "Overdue" if they have hit their due date.

3 answers

1 vote

Hi Majken,

JIRA does not have a built-in feature for that, but I believe you should be able to achieve this with a custom script using the Script Runner plugin.

I've found a similar script to add labels automatically, but based on a different condition. Maybe you can customize that script.

https://answers.atlassian.com/questions/56290/auto-assign-labels-based-on-the-user-group

Hope this helps

Thanks, though it says it is not available for OnDemand. :(

To find Overdue issues, you do not need to add a label. It is a direct search criteria that you can apply.

Look at a sample query at https://jira.atlassian.com/issues/?jql=resolution%20%3D%20Unresolved%20AND%20due%20%3C%3D%20%220%22

Usage of labels will be an over head as you need to remove them also if the due date is updated.

Yes, I know how to find them. The thing is we want them to be labeled so that they jump out when we're not searching just for the overdue issues.

It's easier to remove a label than it is to change the due date. In some of our usecases as well, we don't want the overdue label removed, we want a record that it was overdue.

Ah that explains. So considering that you are using OnDemand, I would suggest to create a filter, run a REST call from an external script to get those overdue issues, and again invoke another REST call to add the label. THis external script has to be scheduled to run from an machine that you have.

https://docs.atlassian.com/jira/REST/latest/

https://www.google.com.au/search?q=site%3Aanswers.atlassian.com+add+label+issue+jira+REST

Sorry for the long period of silence. This seems complex to me but I'm sure we have people on the team that could handle this. A simpler solution of course would be prefered, but this should work.

A little late :-), but we make "overdue" (or imminent) issues "jump out" by making it part of the JQL conditions for an "Expedite" swimlane on our Scrum/Kanban boards.

E.g., swimlane JQL:  priority = Critical OR duedate < 3d OR issuetype in (Incident, Bug)

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Wednesday in Jira

Make your Atlassian Cloud products more secure: our NEW admin security guide

Hey admins! I’m Dave, Principal Product Manager here at Atlassian working on our cloud platform and security products. Cloud security is a moving target. As you adopt more products, employees consta...

153 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you