I'm trying to create an automation rule that will update the project target date in jira product discovery based on the fix versions of the tickets that are the children of the epic that is linked to the idea. The fix versions have dates against them but I honestly don't know where to start.
I'm trying to create a linked view that shows where work is actually landing based on work being done by teams rather than having to move the project target manually each time
Hi @Tom Head
Do you have your rule started yet? If so, please post images of the rule and the audit log details for context. Thanks!
Until we see that, let's break this scenario down into pieces as there are lots of moving parts:
#1) Your Ideas are in the JPD space (i.e., project) and the "delivery ticket", Epic (and its children) are in other ones. Thus, the rule must have multiple-project or global scope to access them. Your Jira Product Admin will need to help create a rule with scope changes.
#2) JPD uses its own format for date fields (different from Date or Date / Time picker), and that must be handled in the rule to save the value as JSON represented as text.
#3) Only the Epic is linked to the Idea. To get at they children of the epic, this must happen in a couple of steps, probably using the Lookup Work Items action with JQL to find them.
#4) The Fix Versions field can have multiple values. And so you are dealing with a list-of-lists situation: the Epic has multiple children, and each child can have zero-to-many values in Fix Versions. Which values do you want to use? For example, let's assume you want this:
GIVEN an Idea
AND the Idea has one linked, delivery ticket Epic
AND the Epic has multiple child work items
AND the children have zero-to-many values in the Fix Versions field
AND zero-to-many of the versions have a Release Date value
WHEN something happens
THEN get the maximum (?) Release Date from the child work items' Fix Versions to store that in the Idea's Project Target Date field
How does that align with what you are trying?
#5) One more thing: please note in my "WHEN something happens" above. There are many ways that final Project Target Date field could be impacted; thus, you may need multiple rules to handle this scenario, or one single rule which runs on a schedule (rather than immediate updates).
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.