nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Rule to reassign tickets to project lead

Joe Gomez_c4k9i1

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.

Accepted answers

Laurie Sciutti

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

All comments

Laurie Sciutti

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

Joe Gomez_c4k9i1

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.

Laurie Sciutti

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.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud