I'm really needing advice on automation rules here, I can't even get the log action to show me the value of a custom field..
Goal: Using Jira Premium with the Hierarchy set to OKR -> Epic -> Feature -> Story -> Subtask. CCR is a Feature issuetype. I need to write an automation rule so that when a CCR (Feature) is approved and Proposed End date is populated; The parent (Epic) card 'Updated Planned End Date' field is updated with the Feature (child/CCR) Proposed End Date value.
Help needed: How to get Proposed End Date to show in the audit log? Is this the right logic to update a parent field (Updated Planned End Date) with the field value from a child card (child card field is Proposed End Date)?
Here is the rule:
Here are the audit log results:
First thing, smart values are name, spacing, and case sensitive. And, they often do not exactly match the displayed name of the field on the Jira pages. When an incorrect smart value is used, it just returns as null / empty.
To identify the correct smart value (or custom field ID) for your field, please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/
Next, when you branch to the parent to copy the field from the trigger issue, please use that smart value as the source. For example:
{{triggerIssue.yourSmartValueName}}
Kind regards,
Bill
Clearly I have no idea how to read JSON code. The links article for how to find the smart value of field says to use a URL (https://<yourinstanceurl>/rest/api/2/issue/<issuekey>?expand=names). When I replace <yourinstanceurl> with my instance and <issuekey> with an issue key, the result is a the following error:
Hmmm… can't reach this page
comerica.atlasssian.net took too long to respond
Any other suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Here are some simplified steps for that how-to article:
yourJiraURL/rest/api/3/issue/yourIssueKey?expand=names
From what you describe, that would be this:
https://comerica.atlassian.net/rest/api/3/issue/CET-93?expand=names
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.