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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

How to use Automation to assign a Closed issue back to Resolver

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 08, 2023

In our workflow when an Issue moves from Resolved to Closed (i.e. the Reporter or someone else checks the work of the person that Resolved the issue, and closes it if it satisfies their needs), we then prefer to assign it back to the Resolver (i.e. the person who transitioned it from In Progress to Resolved.

The idea being that if it needs to be Reopened, then it's automatically back on the person that did the work). This also easily allows people to see the work they've completed to satisfaction for a sprint (or a whole project), and other benefits.

I've looked at Automation rules, but in Assign Issue the only paths near to what we want are "Another field value or comment -> Previous Assignee", or to use a Smart value, which also only allows for things like Reporter or Assignee.  However, this solution only works if the flow is our expected Reporter->Resolver->Reporter, which sometimes gets interrupted as work gets passed around for who is doing the resolving (say, a QA person taking some confirmation work from another QA person).

Does this concept just not exist, because Workflows are not defined clearly enough as being done by a role concept? Or am I missing something?

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
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 08, 2023

Hello @tomivey 

Welcome to the Atlassian community!

Because of the highly configurable nature of Jira it is not possible to have a built in concept for "assign it to the person who did the work". There can be any number of customizations to the workflow such that Jira cannot automatically identify "who did the work".

You could use automation to record in another field who the assignee was when the issue was transitioned from In Progress to Resolved, and then use that other field to reset the Assignee field when you choose to do so (i.e. when it is transitioned to Closed).

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 08, 2023

That makes sense, and that's a clever workaround. I'll definitely try that! Thanks!

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events