Hello all,
We are trying to use a JIRA automation to assign a "Capability Start Date" to our capabilities based on the first fix version release date of it's linked features. We are utilizing an "implements" and "is implemented by" link type. We have tried several iterations of this automation and have been partially successful. We have gotten the automation to identify the features under the capabilities by the issue link but and to identify the min fix version date using the smart value {{lookupissues.fixVersions.startDate.min}} but cannot get the automation to then pull and assign the date to the capability. I'm not 100% sure that any part of our automation is correct even though it is coming back "successful". Any help would be appreciate on what automation we should use and what syntax will work best for the JQL queries or smart values.
Mat Pelchat
Hello @mathew Pelchat
Welcome to the Atlassian community.
When asking for help with an Automation Rule, it will enable us to help you better if you provide the following:
Hi @mathew Pelchat -- Welcome to the Atlassian Community!
Without seeing your entire rule, I hypothesize you are using the Lookup Work Items action to gather those linked features, and trying to find the date from there.
Please note the lookup result is a list of work items, and the fixVersions smart value is also a list of versions...leading to a nested list of lists. When you want the single minimum value for the startDate within all of the version lists, you may use the flatten function to combine all of the results into one list, followed by distinct to remove duplicates, before using the min function:
{{lookupIssues.fixVersions.startDate.flatten.distinct.min}}
Finally, depending upon how you are updating the other field, you may need to add .jiraDate to the end to force the formatting.
Kind regards,Bill
Hi Bill,
Thank you for that insight. This automation is currently on an air gapped system but I will try to get a view of everything we are doing. and upload it to this thread.
in the mean time here is basically what we have done.
Value Field Change: FixVersion
Issue Fields Condition: Issuetype=EPIC
Create Variable: Variable Name" EpicDate" Smart Value: {{issue.fixversion.startDate.JiraDate}}
Added a Log Action: Date+{{EpicDate}}
Added a Branch Rule: Related Issues; Implements
Added a log action: Capability Start Date ={{issue.customfield_10230}}
Added an Advanced Compare Condition: Condition: Less than, Second Value {{issue.customFeild_10230}}
Added Edit Issue: Start Date {{EpicDate}}
What is being returned in the audit when the fixversion for the Epic is changed is it finds tha changed epic, finds the date for the "new" fixversion but does not provide a value for the capability start date and it states that the capability (TT-3 in this instance) did not match the condition.
I am not overly familiar with JIRA automation so feel a bit like throwing stuff at a wall and seeing what sticks. Any suggestions you have about a better overall rule would be greatly appreciated.
Mat
Hi Trudy,
We are on an airgapped system so typing it out was the best I could do.
Thanks for that information, and...even though you cannot post images due to the air-gap environment, you could copy-and-paste the audit log details text showing the rule execution. That may provide more context.
Until we see that...
The correct smart value for the Fix Versions field is plural, and your value is not:
{{issue.fixVersions}}
Next, please re-read what I posted earlier, as the Fix Versions field is a list, and so this smart value:
{{issue.fixVersions.startDate.jiraDate}}
Could produce a result like this, with some fake dates for different versions:
2025-10-20, 2025-11-23, 2026-01-04
When there are multiple versions in the trigger issue / work item, which one do you want to use?
The goal is to get it to pull the first fix version date in the list and automatically update the start date for its linked capability.
It looks like you're new here. Sign in or register to get started.
