Run an automation that assigns all unassigned tickets to the reporter for existing tickets

Carl Alde September 29, 2024

Hi, I would like to assign all existing unassigned tickets (globally) that are not in the 'Done' state to the creator of the ticket

4 answers

1 accepted

1 vote
Answer accepted
Marcus Jacobs
Contributor
September 29, 2024

 

Here you go Carl,

you insert a trigger, manual or scheduled. Use an IF Block with something like "statusCategory NOT IN (Done) AND assignee IS EMPTY" and then assign the issue.

But keep the limitations for automations in mind.Bildschirmfoto 2024-09-30 um 07.11.03.png

Marcus Jacobs
Contributor
September 29, 2024

You can also use the "ISSUE REPORTER" in the assign the issue to. That would maybe fit more.

Marcus Jacobs
Contributor
September 29, 2024
2 votes
Prachi Bolar
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 29, 2024

Hi @Carl Alde ,

Welcome to Community :) 

You can even use a scheduled trigger and set this up so that it will run as per the scheduled time set and assign the ticket 

Screenshot 2024-09-30 at 11.14.08 AM.png

 

You can check this article: https://confluence.atlassian.com/jirakb/jira-automation-rule-to-auto-assign-issues-based-on-role-or-group-1384127370.html on how to auto assigned issues based on role or groups.

 

Things to Note:

  • The users who are auto-assigned issues should have Browse Projects and Assignable User in the Project.
  • If the above permissions are missing the user will not be able to view the issue and automation may throw an error like 

    Error assigning issues

    XXX-123: (Unable to assign tickets to user 'userid'. (assignee))

 

Thank You,

Prachi

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 30, 2024

Hi @Carl Alde -- Welcome to the Atlassian Community!

Doing such an assignment with an automation rule is easy, although it will potentially consume much of your monthly automation usage allocation if your site has many such issues, given your Standard license level.  If that happens, all of your rules will halt processing for the remainder of the month!

 

However, I wonder: why do this?

What problem are you trying to solve by doing this?  Knowing that may help the community to offer better suggestions.

 

Kind regards, 
Bill

0 votes
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 29, 2024

Hi Carl - Welcome to the Atlassian Community!

I create a generic "bulk update" rule that I keep handy. When not running right then, I just disable it. 

Create a rule with a Scheduled trigger. Chose any time period that you want. 

Add a JQL for what you are dealing with, like in your case: project = ABC and assignee is empty

Then add an action for Edit Issue. I think this gives you better results in a case like this than the Assign Issue action. Select the Assignee field. 

Click the 3 dots to the right of the Assignee field and select Copy

Then click on the resulting words of Current issue. You will get a popup. 

Change the Field to copy value from to Reporter. 

Update/Turn on your rule and give it a name. 

The click the 3 dots menu at the upper right next to Return to rules and choose Run rule to run immediately. When it is done, just toggle off the rule so it doesn't run all of the time. 

In the future you can change out the field that you are copying values to/from for any easy bulk update with rules. 

Screenshot.png

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