Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Rule to reassign tickets to project lead

Joe Gomez
Contributor
May 24, 2024

After a user is deactivated how can we automate a global rule of reassigning all the tickets of a user to the respective project lead? I have searched google and combed over the various rules and options but can't find any way to do this. I saw a script suggestion using a 3rd party tool but this should be something that's built in.  Any suggestions? If this is possible, I might need some hand holding here since I'm fairly new to automation rules in general. 

1 answer

1 accepted

2 votes
Answer accepted
Laurie Sciutti
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 24, 2024

Hello @Joe Gomez ~ I have a rule that does just that!  Trigger = Scheduled using a JQL expression like below (I have it run every Sunday evening), with an Edit issue action as shown below.  HTH!

 

assignee in inactiveUsers() AND statusCategory != Done

 

Capture.PNG

Joe Gomez
Contributor
May 24, 2024

Beautiful, thank you Laurie! Did you leave the option checked for "Only include issues that have changed since the last time this rule executed?" I'm trying to think through possible reasons to uncheck it.  Also, I had been using this jql to search for such tickets: assignee not in membersOf("jira-software-users") and statusCategory != Done
They both return the same # of tickets in validation but curious of the difference.  

Like Laurie Sciutti likes this
Laurie Sciutti
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 24, 2024

Hi @Joe Gomez ~ I left that option unchecked .  I suppose if the Project Lead was changed from the time the rule was last run, that that might have an impact so my thoughts are to leave it unchecked so all open issues assigned to an inactive user would be included.  Your JQL is essentially the same but I suppose you could have an active user that isn't a member of the software users group that may have open issues assigned to them.  I used the inactiveUsers() option as a catch-all.

Like Joe Gomez likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events