I've setup a simple automation rule using Automation for Jira to create two sub-tasks when a new defect is created.
This initially failed in the target project with the following error:
Error creating issueAccount is required. (customfield_14040)"
Having extended the rule to be in my test project and made some tweaks etc it eventually worked as it was originally setup. Upon investigation the difference was that account wasn't in face required in the test project for Sub-tasks. However - the account field is filled out by default via the standard "inherit from parent" which appears to be the default setting for sub-tasks.
I don't want to change the field config for the original target project as account is indeed a required field, however am unable to get the JSON working correctly to set the account field on the new sub-task based on the parent issues account field using the following:
{"fields": {
"Account": {{triggerIssue.account}}
}
}
I have managed to get similar JSON working but when setting a specific Account rather than trying to link to the trigger issue.
Any help greatly appreciated!
Hi Lewis,
Is this the Tempo Account field? If you're running the latest version of Automation for Jira, then you should be able to just add that field using the simple form (Click on "Choose fields to set...") and hit the '...' menu. Then you should be able to select 'Copy from trigger issue'.
Hope that helps!
Cheers,
Andreas
It is, our Jira instance does need an update generally so i'll expedite that,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi, did you finally manage to find a solution to this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.