nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Can we target the Delivery field with Automation?

Gavin Steele_3lp75h

When I move an idea into a new state, I trigger an automation that creates a Story in another Jira project.

Once created, I would like to get that new Story key and use it to populate the Delivery field in the Discovery Idea ticket so that we can start tracking delivery status right away.

Currently, I have to copy the URL created for the new story into the idea after the automation has run.

Accepted answers

Gavin Steele_3lp75h

It looks like this is a known 'limitation' with JPD right now.

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648

All comments

Bill Sheboy

Hi @Gavin Steele

First thing, I have not tried what you ask and my suggestion is based on what I know about automation rules. With that out of the way...

I suspect your scenario is possible. When an issue is created in a rule, the {{createdIssue}} smart value refers to that issue and {{createdIssue.key}} (or most recently created issue from the dropdown list) could be used to link to it. https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--createdIssue--

For JPD and issues in other projects, the rule would need to be global or multiple-project in scope to link to it. The reason is the new story would be edited by linking, and that cannot be done with a project-scope rule. Please work with your Jira site admin on that because they will need to create the rule (or change its scope).

The only other thing to figure out is the correct link type, which appears to be Implements, based on looking at an issue linked to a JPD idea.

Kind regards,
Bill

Gavin Steele_3lp75h

So JPD to Jira Project is working successfully

My automation:

Creates a Story
Links the JPD idea in the related issues
Creates a number of sub-tasks

But there is no way to update the Delivery field on the JPD idea. This field is specifically for linking to other projects.

Delivery is a 'special' type of filed, that seems to require manually being updated?

It seems odd to have to add another automation in the destination project to go back to the JPD idea and update the Delivery filed? If that is the suggestion?

Bill Sheboy

Not two rules: I was suggesting to try to add the linking in the same rule, although it may require doing this with advanced edit using JSON rather than with issue linking.

UPDATE:

I just tested this and it worked with a multiple-project rule, including the JPD project and the Jira Software one. No need for the JSON edit. For example:

trigger: some trigger, including the JPD idea (i.e., issue)
action: create a story in the Jira software project
action: link issues, selecting the type of "is implemented by" and the issue is "Most recently created issue"

This linked the issues and added the Jira software project issue to the Delivery Tickets for the JPD idea.

Gavin Steele_3lp75h

Thanks Bill, I will look into the JSON approach

Gavin Steele_3lp75h

It looks like this is a known 'limitation' with JPD right now.

https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Known-limitations-of-Jira-Product-Discovery/ba-p/2069648

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation

delivery