[Automation] - How to Set an Assignee using 'Create work item with Request Type' action.

[Zeroocool]

Assignee, despite being associated with the request type under "Work Item View", is not available to set when using the "Create Work Item with Request Type" action.

The documentation clearly states

---------------------------

Create issue with a request type

Available fields include all fields that are not hidden and added to the request type. Hidden fields aren’t supported.

Source: https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Create-issue-with-a-request-type

----------------------------

This however appears to be completely false.

When you make 'Assignee' available on the "Request Form" tab, it is set to hidden automatically. This setting cannot be changed.

Only then does it becomes available when using the "Create issue with a Request Type" automation.

Can anyone explain this or is this just a poor design choice.

[Zeroocool · Accepted solution]

I was able to confirm with support that it is just a poor design choice and bad documentation.

To add a field it has to be present on the "Request Form" and not just associated with via the "Work Item" view.

In the case of Assignee, marking it as "hidden" would be the correct supported approach to prevent an end user from accessing it directly.

Notably, sometimes this view fails to update properly, and removing and adding the field back can resolve this problem.

Truly the laziest implementation of something I've ever seen.

[Kai Krause]

Hi,

t hink a assignee can only be used hidden on a request type and youz can set a default JSM agent as assignee or left it unassigned.

In my opion it can also only be used by licensed persons in the portal. In case of an automation, i would create the new issue with a request type and a second automation when this requesttype is created to set the assigne on the issue. 

BR
Kai