How to migrate the Delivery section in Product Discovery Space to Software Space/Project

[Sydney Swanson]

Hi, I am working on a company managed Jira cloud with full admin permissions.

Currently I am trying to solve an automation issue for migrating values from the Product Discovery Space (PDS) to a separate Software Space project within the same company managed Jira Cloud.

In the PDS, I have a set of Idea-type work items and within each Idea there is section/tab called 'Delivery' where all related Epics (and child items) are linked. I would like to find a way for Jira to read the Epics listed in this Delivery section and store in a new field in the Software Space for related Monday.com Deliverable-type work items. 

I created a custom field called 'Linked Delivery Items' as a global field and it is a written multi-line text type. I've tried automation, I've downloaded ScriptRunner and tried several lines of code, but I am still struggling with reading the related Epics from the Idea ticket, storing that in the Linked Delivery Item field and writing this information to Monday Deliverable work items within the Software Space. 

I would like the trigger to be related to when an Idea is linked 'as a dependent of' on the Monday Deliverable work item or when a Monday Deliverable work item is linked to the Idea as 'is dependent on'. Any ideas? Is this even possible? 

[Tomislav Tobijas · Accepted solution]

Hi @Sydney Swanson ,

This might be possible with automation, but I'm just wondering - from where are you linking the Monday Deliverable and the idea? I'm asking because if you use the Delivery section of the idea to link to another item, it will always use a specific link type. (if something hasn't changed since I've used this)

And also, 'Linked Delivery Items' is a JPD (global) field or a Jira field?

Cheers,
Tobi

[Sydney Swanson]

Hi, thank you for responding! So I created 'Linked Delivery Items' as a Jira field. 

I did find within the JPD space, there is a Linked Items field but it is a space field and has the description 'number of jira work items linked to an idea'. 

Does that help clarify?

[Tomislav Tobijas]

Hey @Sydney Swanson ,

So, I think I've got it (but feel free to correct me if I missed the point here).

Pre-requisites:

1. Create Jira custom field (paragraph type) - Linked Delivery Items
2. Added this field to software Jira space (to work item layout)
3. Meanwhile, create "Monday Deliverable" work type and added it to space (configured as defined in step #2)

Moving on to JPD:

1. Created one dummy idea and added 3 delivery items: 2 Epics and 1 Story

Next, automation rule (it's pretty basic and can be upgraded if needed):

• Scope: Single space (software space)
• Trigger: Work item linked
• Action: Edit work item fields > Linked Delivery Items (created in step #3 above)

Within the action, I've used the following syntax:

{{#destinationIssue.issuelinks}}
   {{#if(equals(outwardIssue.issueType.name, "Epic"))}}
      {{outwardIssue.key}}
   {{/}}
   {{#if(equals(inwardIssue.issueType.name, "Epic"))}}
      {{inwardIssue.key}}
   {{/}}
{{/}}

Which essentially looks at destination issue and all linked items, and only 'pulls' those which are type "Epic."

Now, to test this:

1. Navigate to JPD item (dummy idea created above)
2. Link an item in software space (used any link relation, but this can be limited within automation rule)
3. Navigated to linked software item to check "Linked Delivery Items" field

I did add a couple of log actions just to check which items are recognized as linked issues and what the #if part would return once it parses the results, so you can see that in the automation audit log as well:

Hope this helps.

Cheers,
Tobi