I have an approver field turned on, but can't find the field in my automations to make them assignee

[Vanessa Scherstrom]

I have added a user picker field for "Manager Name" in my "Request for leave" request type in a team managed project. This is also my Approver field in the workflow. I wanted to set up an automation that would assign the issue to the person named in the "Manger Name" field, but when I try to build that automation the "Manager Name" field does not appear.  

[Lisa Forstberg · Accepted solution]

Hi @Vanessa Scherstrom ,

Do I understand you correctly that when the request is created you want to: 

1. assign the request to the user picked in the field "Manager name"

2. also have the manager be the approver of the request.

In order to be assigned to a ticket the user needs to have an agent license. Maybe this is not needed? If the user in the manager name field is the approver they will get an email and need to approve the request. 

Also I am a bit curious on what custom field type the Manager Name field is. Are you working in a company managed project or a team managed project?

br

Lisa

[Vanessa Scherstrom]

Both assumptions are correct. All of the people in the Manager Name field have a license. It is a team managed project.  Would you recommend a company managed? We would only have about 15 employees making requests. 

[Vanessa Scherstrom]

I think stakeholders want to be able to see in the Que who has an open request to complete, which is why we want the assignee and the approver to be the same.  So they can transition to approved/declined by emails and also view who has open requests in the Que.

[Lisa Forstberg]

Ok, I am more used to Company managed, thats all. 

So can you not find your manager name field in the automation if you just use the edit issue action?

This is a test (from my company managed test project)

[Vanessa Scherstrom]

Now I don't have the option "issue to copy value from". 

[Lisa Forstberg]

I think you have run into this limitation:  https://support.atlassian.com/cloud-automation/docs/limitations-in-team-managed-projects-for-automation-rules/

User picker fields in Team managed projects can't be set in automations. 

Are you a Jira admin? If you create a standard user picker custom field for Manager name and use that in a TM project you can copy from (three dots) and find that field to automate setting assignee.

all the best

Lisa

[Vanessa Scherstrom]

That does seem to be why that won't work. 

[Vanessa Scherstrom]

I did accept the answer as User picker + automation doesn't work for team managed, but would you mind further explaining "If you create a standard user picker custom field for Manager name and use that in a TM project you can copy from (three dots) and find that field to automate setting assignee"  I tried retrieving the smart value for the user picker field and that did not work.  

[Vanessa Scherstrom]

Should we do this answer in a different question @Lisa Forstberg