Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
-
Jira Software, Jira Service Management
Description
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 the Project field of the Create Issue action only allows selecting a specific project from the drop-down menu and does not support smart values. This means we cannot dynamically select the project at runtime.
Desired Behavior
The Project field should accept smart values in the same way that fields in the Edit Issue action accept them.
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.