I need a automation adding time label on work items for passed time for every week (+7, +14, +21..). I try on Rovo but it didnt go very well. The rule should run once a day, and the labels should not overlap. For example, a scrum story/issue is created and 7 days have passed --> then automation add +7d label for this work item and atfer 14th days from creation --> +7d label should remove and +14d label need add to work item. Thank you in advance for your help and advice, and have a good day.
Hello @Erkan GÜLER
If I’m honest, I wouldn’t use labels for this unless you really need that “badge” look on the issue and an easy JQL filter.
The clean way in Jira Cloud is a small custom field like Age bucket (single select: 7d / 14d / 21d / 28d…). Then a daily automation just sets that one field based on created date. It’s harder for users to mess up, reporting is cleaner, and you don’t end up with label chaos over time.
If you still want to do it with labels, it’s fine, just do it in a disciplined way: run it once per day, use non-overlapping time windows (7–14, 14–21, 21–28…), and always remove the other “age labels” before adding the new one so they never overlap.
I’d also usually limit it to unresolved items so you’re not touching old completed tickets forever.
Automation are pretty simple.
Rule: add +7d
Trigger: Scheduled (daily)
JQL:
created <= -7d AND created > -14d
Action: Edit issue Labels
Remove: +14d, +21d (and any other “age” labels you use)
Add: +7d
Rule: add +14d
Trigger: Scheduled (daily)
JQL:
created <= -14d AND created > -21d
Labels:
Remove: +7d, +21d
Add: +14d
Rule: add +21d
Trigger: Scheduled (daily)
JQL:
created <= -21d AND created > -28d
Labels:
Remove: +7d, +14d
Add: +21d
Add project = XYZ / issuetype = Story to the JQL if you only want this for certain items.
Thank you for your feedback. After a brief review, I realized that placing too many visual labels on the work items might cause confusion. I plan to resolve this by adding quick filters. Best wishes...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, all depends on your approach. We can give advices but you know the best what suite you the most, and let's be clear, Atlassian giving us 1000 possibilities to solve problems 🤠
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I plan to resolve this by adding quick filters. Example: unassigned items with range of X days.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.