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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,082
Community Members
 
Community Events
176
Community Groups

Using Jira Automation to update existing tickets that are either closed or not closed

My team is looking to into using Jira automation to clean up existing tickets. We are trying to cover the following

  1. Find existing stories  and bugs with blank fixversion and update with the epic fixversion 
  2. Find any existing stories and bugs whose fixversion does not match epic fixversion and update with with epic fixversion
  3. Update all sub-task and technical sub-task to match the parent fixverison
  4. Update epic to "Blocked" status if any associated issue type tagged to the epic (bug, story, technical task, sub-task or related links_ has a "Block" status or "Blocked By" link
  5. Update an epic to "In Progress" if any associated ticket tagged to epic (bug, test, story including story sub-tasks etc) are not in "Open" or "Blocked" status
  6. Change an epic to "Closed" status when all associated tickets tagged to the epic has been closed.
  7. Change an epic status to "Reopen" if any associated tickets tagged to the epic has reopened.

For our team, everything is linked to the epic, so fixversion must take the values from the epic. It's time consuming for programmers and tester to go back to "clean-up" tickets. Thus we want to automate these procedures not just for new tickets, but to clean up older tickets. Thus the automation should address tickets in "Closed" status as well. 

 

It seems that the updates are not working. Let's take the first item on the list. The query as follow:

ATTEMPT #1

Run on scheduled every 12 hours 

JQL QUERY: issuetype in (bug, story) and "epic link" is not blank 

 

Branch Stories

If ISSSUE TYPE is one of story or bug

And Fixverion is empty

 

Action

Edit fixversionn copy from epic

 

ATTEMPT #2

 

Run on scheduled every 12 hours 

JQL QUERY: issuetype in (bug, story) and "epic link" is not blank 

 

If Fixversion is empty

Action

Edit fixversion copy from epic

 

Expectation update all stories and bugs across status to match the epic fixversion

 

There is no demo that fits my the this scenario

2 answers

0 votes
wwalser Atlassian Team Nov 01, 2020

What does the audit log say about the attempts that you've tried thus far? Have you tried adding audit log actions to determine what step the automation doesn't complete successfully.

https://support.atlassian.com/jira-software-cloud/docs/debug-a-rule/

The automation to close epics when all issues under the epic is not working. I am still working on that. So I decided to focus on building rules that closes stories, tasks etc after a specific release date.

 

I found out that the automation will only follows the steps suggested by our workflow. I wanted all epics to move to the close status ignoring that  if an epic is under a "QA Review" then it must go to "Testing" before a ticket is closed. For now, manually closing epics will continue. 

0 votes
John Funk Community Leader Oct 12, 2020

Hi @starryeyes ,

Would this automation rule work for you?

screenshot.png

John Funk Community Leader Nov 02, 2020

Hey @starryeyes  - just checking in with you about this one

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events