automation - change assignee to a person from a custom field

[Scott Thurston]

I have searched for the solution to this but just have not been able to figure it out.  I want to have rules as an issue transitions that the assignee is changed to the value from another custom field.  There is a custom field for Developer, Tester, Approver etc.  I have not been able to reassign the assignee field.  I am sure there is an easy solution to this but have not been able to figure it out.  Can someone tell me what action to use and how to enter the value?

Thanks,

[Joe Hankin · Accepted solution]

OK. I have the answer...

You Assign Issue, and select Smart Value.

But you write it like this...

{{issue.[custom field name].accountId}}

eg. {{issue.editor.accountId}}

I also think this will work too...

{{issue.customfield_XXXXXX.accountId}}

[Scott Thurston]

@Joe Hankin thanks for your help!

[Rashmi Ratnani]

Hi @John Funk, 

I want to be able to do the opposite i.e. edit a custom field to copy the assignee when the status of an issue changes. Should I use trigger issue or current issue? Doesn't seem to be working. 

For e.g. If Bug changes from To Do >> In Progress  Then Custom Field == Assignee

[Scott Thurston]

Do I use smart value and pick {{issue.QA Resource}} ?

[Joe Hankin]

Hi @Scott Thurston 

This is my understanding too, as in here: https://community.atlassian.com/t5/Jira-Service-Desk-questions/Automation-for-Jira-Change-the-Assignee-from-a-custom-field/qaq-p/1398101 but it doesn't work for me.

[John Funk]

Hi Scott,

Do you have a rule built already using Automation For Jira?

If so, use the Edit Issue action and not Assign User action. Then Select Assignee and copy the value from another field. 

[John Funk]

I would just use Copy from Current Issue. 

Then click on the words Current Issue and that will give you a popup where you can select the QA Resource field. 

[Scott Thurston]

Here is what I have so far.  Will this work?

            When: Issue transitioned

                 TO

               Business Sign-Off

             Then: Assign the issue to

                {{issue.Product Owner}}

[Scott Thurston]

@John Funk I don't see how Edit Issue action would work as it does not let me update the assignee field to a value from another field on that same issue.

[John Funk]

Can you share a screenshot of that?

It should look something like this:

[Joe Hankin]

Hello @John Funk ,

I'm having the same issue.

When I select Edit Issue, and Copy From Issue, the fields available are only:

1. Assignee
2. Creator
3. Reporter
4. BAU / Project Lead
5. Owner

No custom fields available.

However, when I change to Assign Issue and select Smart value, I can add some smart value content like {{reporter}}, but I want to use {{issue.Editor}}, but it isn't working. Even when I use the custom value too, like {{issue.customfield_XXXXX}} I just get an error.

It would appear possible here: https://community.atlassian.com/t5/Jira-Service-Desk-questions/Automation-for-Jira-Change-the-Assignee-from-a-custom-field/qaq-p/1398101 but I can't get it working.

Any help would be much appreciated.

[Joe Hankin]

@John Funk this is the screenshot, showing that we can't use Custom Fields:

[John Funk]

Hey Joe - It's probably because the field is not available to either the project or the edit screen. Check the field Owner to see what is different about it because it is a custom field, too. 

[Joe Hankin]

Hi @John Funk I thought this might be the case too. But I wasn't sure because this is a Next-Gen project,  and created via the project settings interface which means the field is automatically in the project edit screens on the board etc.

I added my way around it below. 

Would be good to get a little clarity as to whether or not this is the only way?

[John Funk]

Hey @John McKiernan  - can you bring any clarity to the custom fields for Next-gen not showing as available to copy to the Assignee field?

@Joe Hankin  - Isn't the Owner field a custom field? What's different about it than the other custom fields that aren't showing?

[Joe Hankin]

Hi @John Funk 

Yes this is in fact a custom field. But it wasn't set from inside the project, it seems to have been setup at a high level. Is my work around below not an easy way around it?

Here are the details on the custom field called Owner.

Default Configuration Scheme for Action Owner

Default configuration scheme generated by Jira

This field will be available on issues of any typein all projects

[John Funk]

If your work around does what you need it to do, by all means use it! :-)

But it shouldn't be that difficult and you shouldn't have to use smart values as your only option.