Assign all unassigned tickets to creator

[Anton Garri Fagerbakk]

Hi, I want to assign all (Globally) current unassigned tickets without the state "Done" to the creator of the ticket. 

I have the required rights to execute it and I have also created a global rule for it, but it is not retroactive. How and where do I run queries like this?

Thanks!

[Walter Buggenhout · Accepted solution]

Hi @Anton Garri Fagerbakk,

You can indeed either use a scheduled trigger (if you want to run it on a regular basis) or trigger the rule manually if this is a one-off operation.

In the latter case, your rule could look like this:

When you open any issue (that ideally matches the condition of your query), locate the Automation > Rule executions pane from the Details section on your issue screen. Right there, you should be able to trigger the rule:

 

Hope this helps!

[Anton Garri Fagerbakk]

This worked thank you so much!

[Jack Brickey]

Hi Anton, you could create a global manual automation rule to assign all current issues. 

• trigger - manual
• branch JQL - assignee is empty and status!= done
• condition - optional but can limit execution of action as needed
• action - edit issue , Assignee - {{issue.reporter}}
  
  

The above is from current memory, so I suggest that you create a test scenario with a single issue until you get it to function like you want. For example, you could take one unassigned issue and add a label to it and add a condition to your rule, to ensure only that issue was action. 

[Anton Garri Fagerbakk]

I ended up going with Walters solution, but thank you very much!

[Rilwan Ahmed]

Hi @Anton Garri Fagerbakk ,

Did you try using trigger Scheduled in automation ? 

For creating Global rules, go to Admin settings --> System --> Global Automation --> Global rules --> Create Rule

[Anton Garri Fagerbakk]

I've currently made three different rules that provide this solution globally. One when a ticket is made, one when a ticket is changed and one that runs on a schedule. 

The two first ones work, I've tested them, but the third one does not seem to trigger any tickets even though the JQL is valid and is showing that it affects the relevant tickets.

Not certain what stops it from triggering.

[Rilwan Ahmed]

@Anton Garri Fagerbakk 

Please check the rule audit log for any errors and please share us the screenshots of your rule. 

[Bill Sheboy]

Hi @Anton Garri Fagerbakk 

I am curious: what problem are you trying to solve by doing this?  Specifically, what value does it provide to assign an issue to someone who asked for a thing to be done?

Kind regards,
Bill

[Anton Garri Fagerbakk]

Hi @Bill Sheboy 

I have noticed that across our projects a lot of tickets get created with no assignee to finish the task and at some point become quite old. These tickets have commonalities such as that they are forward-looking, "nice to haves", or ideas. The intention behind the ticket creation is good, but the outcome is that you end up having a massive backlog without assigned tickets which ends up in a stale, parking lot/graveyard state.  

So the rationale is to have the ticket creator take responsibility to assign someone to complete the ticket and/or reflect on the necessity of said ticket.

In essence cleanup.

I also created a global rule to comment on old tickets to combat this problem as well.

There are probably several ways to solve this problem. Let me know if you have any!

Kind regards,

Anton 

[Bill Sheboy]

Thanks for that information, Anton.

I understand the concern about a backlog becoming "stale", with older requests never proceeding and stakeholders/requestors losing interest.

One helpful practice is to be intentional about work intake and backlog refinement.  When a product owner/analyst actively manages ideation and work intake they can assess how to handle requests, including when to work on them or abandon them.  They can also provide a wholistic view to balance stakeholder requests for prioritization.

When first starting with such practices, it may help to do some "house cleaning", such as abandoning anything older than a threshold timeframe in the backlog, refine the remainder, and then start anew with work intake.