How to assign values to issues in lookupIssues or linkedIssues

Question

Hi, I have a Discovery Project where i want a custom field (LRE) to be updated when a linked issue (Epic) in another project has its Original Estimate updated.

For me it seems natural to use the trigger "issue updated" or "field value changed" on the source, i.e. the Epic. While having this setup I cannot figure out how to assign values to the destination project (Discovery Project).

Using lookup issues as shown below, the lookupIssues holds the right idea from the Discovery Project, but I can not figure out how to assign a value to idea, e.g. like {{lookupIssues.get(0).LRE}}. It seems like Edit issue will only operates on the Epic. I also tried using branch rule but without any luck.

Fredborg, Bo [EMR/MSOL/RYDK] · Answer

Hi again,

I found a fix, but it feels odd as I have to do every operation with reference to the issue from where the automation was triggered (not able to operate directly on the Idea).

This thing is now causing another problem.

When setting up a timer based (scheduled) automation I cannot figure out how to assign values to my Ideas.

I am able to identify all relevant Ideas to be updated, and generate the values (LRE) based on related Epic, but unable to assign values.

Error in the log

Fredborg, Bo [EMR/MSOL/RYDK] · Answer

Hi Marc,

Thank you for your answer. I think I need to elaborate a bit.

For each idea in the Discovery project there may be multiple Epics linked, each with an Original Estimate.

I want the LRE updated as a sum of Original Estimate for all related Epic. I cannot figure out how to iterate on all related Epic to the idea, when the trigger is place on the update of an Epic.

Secondly, seen from the perspective of the Epic, the relation to the idea is of type "implements", whereas from the perspective of the idea I have no clue... I have tried "is implemented by" and many of the others, but they seems all to return "".

Thanks,

Bo

Marc -Devoteam- · Answer

Hi @Fredborg, Bo [EMR/MSOL/RYDK]

M again, based on Original Estimate my above option will not function.

I have also a solution for this.

The trigger of the rule needs to be on the field "Time Tracking" and you need to create a field on the JPD project as well, based on text if you want the "Original Estimate" from the Epic to show the hour/day/week abbreviation besides the number

The rule stay the same from the start, jst make sure to use the "Time Tracking" field as the trigger.

Within the branch create a variable based on: {{triggerissue.timetracking.originalEstimate}}

The set the Edit to the new field on the JPD, by using the variable (in htis case, I named it {{time}}

Rule: