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; } } }

Fetch the assignee at a particular status

Jira Billing

I’m using Jira Data Center for managing tickets.

In a particular workflow, I have a transition from All to several statuses, including the TODO status.

I want to assign the issue to the last assignee when the issue was in the TODO status. The assignee can change when the issue is transitioned out of the TODO status say to In Development.

Specifically, when transitioning the issue from All to a status like Product Dependency, I want to assign the issue to the user who was assigned when the issue was last transitioned to the TODO status.

Kinldy help me with how to achieve this behavior.

Accepted answers

Bill Sheboy

Hi @Jira Billing

Do you have Jira automation rules installed in your instance? If so, you could create an automation rule to save the current Assignee in a custom field when transitioning from the "Todo" Status and use it later with another rule (or in a workflow action).

Kind regards,
Bill

All comments

Radek Dostál

I think you contradicted your requirement there at the end.

Nevertheless this isn't something you could do because the "last assignee in a particular status" just simply isn't tracked. At best you would have to go by issue history, go through each individual change, to figure out when the status was last in a particular status, and in parallel you also need to go through that same history to find out who the assignee was.

It wouldn't be difficult to figure out how to write the searchers, but it would end up being custom code in Java API, because you won't get this data from anything else other than issue history.

Bill Sheboy

Hi @Jira Billing

Kind regards,
Bill

Jira Billing

Thanks @Bill Sheboy ,

I've used this method at last though I'm looking for an alternate where I don't need to use any custom field.

Bill Sheboy

To do this without a custom field, a rule could...

Save the value with an entity property instead, or

Call the REST API with the Send Web Request action to read the issue history to find assignee. This would likely be a more complicated rule as it will need to test multiple conditions and potentially need to page through repeated calls.

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

data-center