How to use delivery progress from JIRA product discovery in automation.

[_Ekta Lala]

I am trying to automate a customized field in JPD based on delivery progress. However, delivery progress , % progress and delivery status all are showing as none or no value during query while it shows value in Delivery view. 

 

PS - Automation is not working because values are none. 

[Bill Sheboy · Accepted solution]

Hi @_Ekta Lala 

Short answer: that cannot be done directly.

Jira Product Discovery (JPD) fields for delivery progress, calculated fields, etc. are only displayed in the UX and are not saved with the Idea.

A workaround for some of these fields is to dynamically re-calculate the value in an automation rule.  For delivery progress, this could be done using the Lookup Work Item Data action with JQL to identify the work items and perform the math.  Please note well: the rule scope will need to be multiple-project or global to allow access to items outside the JPD space (i.e., project) and thus the rule will need to be defined in the global rules list.

Kind regards,
Bill

[_Ekta Lala]

Thanks you Bill. I will try and share my findings. 

Meanwhile, Do you know what link relationship, I should use in automation to link items in delivery section of JPD? Currently, I am using 'implements' and it is just linking the item in overview but not doing any calculation of progress and others derived fields. 

Regards

Ekta 

[Kamila Czubaj]

Hey @_Ekta Lala 

You can use Project Automation to automatically change an idea (e.g., change a field value, transition to a status) when its delivery epics/issues are done. 

Demo: project automation in Jira Product Discovery

[Bill Sheboy]

Hi @_Ekta Lala 

Please see the information provided by @Kamila Czubaj for more information about the Polaris link type. 

Unfortunately, that type in the UX appears as "implements" and "is implemented by"...which is the same as another link type.  Thus, using the Polaris information or "implements" AND the work item types is key to finding the correct work items.

If that does not help, please post images of your complete rule, the rule actions, and the audit log details.  Those will provide context for the community to give better suggestions.

Thanks!

[_Ekta Lala]

Thanks Kamila and Bill

I am currently using linking issue type as 'implements'. The Epic is linking but not showing in delivery section and none of the calculation is happening.

 

[Bill Sheboy]

Hi @_Ekta Lala 

You are creating the Idea and so the linking is in the opposite direction: "is implemented by".  Please try these steps, with some changes to prevent other potential problems:

• trigger: Work Item Created
• action: Re-fetch Work Item Data
• fields condition: Issue Type equals Epic
• action: Create Work Item
  • Space and Issue Type are for your Idea
  • copy / set other fields...
  • Linked Issues
    • "is implemented by"
    • Trigger work item

Please note well: There are known racetrack timing defects with the Work Item Created trigger (and some other triggers).  This means the rule can start running before all data is ready...leading to errors and unpredictable condition results.  Atlassian knows about these defects, and has not announced when they plan to fix it.

The mitigations for this defect are:

1. Always add the Re-fetch Work Item Data action after this trigger; this will slow the rule slightly and reload the data before the steps proceed
2. Never use the new feature to add conditions directly to this trigger; the data could be incomplete, leading to problems.  Instead, add separate conditions after the re-fetch action.

[_Ekta Lala]

Thanks Bill, it worked with 'implemented by'. 

I am yet to complete automation for dynamic field calculation of delivery progress. I will come back with the outcome as soon as it is done. 

BR

Ekta