Issue Summary

Use Case

A service desk agent triggers a Jira Automation rule to create a related escalation issue in a different project by selecting a Tier 2/3 team from a user input prompt. The rule does a lookup by team name (either in a lookup table within the rule or an Assets lookup) to determine the appropriate project for the escalation issue.

The Create Issue action in the rule should create the escalation issue in the project it found in the lookup action.

Constraint
 
Currently, a smart value will only populate a Project if the value is the ID of the project. It will not work if the smart value is pulling the Project Key.
 
Desired Behaviour

The Project field should accept projectKey smart values in the same way as projectId smart value is accepted.

Workaround

As mentioned in this thread from five years ago the workaround is to use the Send Web Request action instead of the Create Issue action. This is an unsatisfactory solution because it will be beyond the capabilities of many project administrators and it more difficult to maintain as the API token must be updated every year when it expires.

Another validated workaround is to use the project field ID smart value to set the project field in the issue create action:

{{issue.customfield_10842.id}}

• customfield_10842 is a project picker custom field.