Can we target the Delivery field with Automation?
Asked by Gavin Steele:

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.


Answers:
author: Gavin Steele
body: 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>


author: Bill Sheboy
body: Hi [@Gavin Steele](/t5/user/viewprofilepage/user-id/5389241)

*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

comments: author: Gavin Steele
body: 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?


author: Bill Sheboy
body: 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.


author: Gavin Steele
body: Thanks Bill, I will look into the JSON approach


author: Pierre Liddle
body: [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) is it possible to share the details of the automation rule, would like to explore to see if we can do something similar to make the integration more seamless.


author: Bill Sheboy
body: Hi [@Pierre Liddle](/t5/user/viewprofilepage/user-id/4912460)

The steps for my test rule are exactly what I listed, although I used a scheduled trigger to exercise a specific JPD idea with JQL. The key is making this a global (or multiple-project) scope rule; that allow the link to succeed, thus updating both issues.

Kind regards,  
Bill


author: Chris Timms
body: Hi [@Bill Sheboy](/t5/user/viewprofilepage/user-id/1685313) ,

What you are asking for is very possible, if you adjust your approach.

Rather than linking the idea to the delivery ticket, when you create the delivery ticket, link it to the idea (i.e. the reverse of the sequence you have now). This removes any of the complexity around branching and fetching tickets from your automation.

This is fairly trivial in automations, all you need to do is link the created issue to the trigger issue using the 'implements' link. This will allow your delivery ticket to appear in the delivery tab in JPD

Regards,

- C


author: Bill Sheboy
body: Hi [@Chris Timms](/t5/user/viewprofilepage/user-id/1260719)

There was no branching or issue fetching in my suggestion. Did you perhaps post in the incorrect thread?

Kind regards,  
Bill


Tags: automation

delivery