how to assign a ticket to person who has updated a specific field

[Muhammad Akram Sharifi]

Hi Everyone, 
I have a project where multiple users are working in one ticket, Now I have a requirement to assign the ticket to one of those who has updated the Description field.  

when the ticket workflow status changes to "Rejected," Assign the ticket to the user who updated the "Description" this user might not be the reporter or the current assignee. 

everyone's input is appreciated. 

[Bill Sheboy]

Hi @Muhammad Akram Sharifi 

What problem are you trying to solve?  That is, "why do this"?  Knowing that may help the community to offer alternative solution approaches.

Until we know that...

Do you want the last person who updated the Description field, or something else?

If it is the last person, that could be one of two people:

1. if the Description has not been updated since the issue was created, it would generally be the Reporter (i.e., the person who created the issue)
2. if the Description was updated later, the user could be found in the issue history, or by saving the user in a custom field when the Description is edited

Both of these cases could be managed using automation rules and a custom field:

• add a custom field to track the user, for example named Description Last Updated By
• add an automation rule, triggered on issue creation, that sets the custom field to either the Reporter or the person who created the issue: {{initiator.accountId}}
• add a second automation rule, triggered on an update to the Description field, which updates the custom field to {{initiator.accountId}}

When you need to re-assign the issue, use that custom field as the source for the Assignee.

Kind regards,
Bill

[Muhammad Akram Sharifi]

Hi Bill, 
Thanks for the reply actually we don't want to add a user field to keep the "description field update initiator info. 

I would like to know if its possible to get that information from the history of the ticket. 

[Bill Sheboy]

You could manually look at the history for each issue, or you could use the REST API endpoint to check the issue history. 

Using the endpoint will require searching the results to find changes to the Description field and may require multiple calls with paging results if the issue has changed many times.