When Creating a Delivery Ticket it does not bring over the description, attachments, comments, etc.

[Ashebe.Pierre]

Product Discovery - When creating a delivery ticket it does not bring over all information

Ashebe_PierreJan 17, 2023

While using the Product Discovery Project Template - Under the "Delivery" tab and after selecting "Create a Delivery Ticket" it does not bring over all the information/details from the original ticket idea fields to the Delivery ticket (which I assign to a team). E.g., Description, attachments and comments. It only brings over the quick summary field (name of the idea) and linked issues. How to get the information from the Description field, Comments field and Attachments field to carry over to the newly created Delivery Ticket? 

[Tanguy Crusson]

Hi @Ashebe.Pierre , you'll have to use Automation rules. See details here: https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152

[Hannah Garvin]

Hey @Tanguy Crusson 
I used this

https://www.loom.com/share/18ece4f7301c4c2f82c55ad33b3cfbfd

When you set up the 'Issue fields' condition I changed it to 'Is one of' (and then selected the options), rather than 'equal' to as when creating delivery tickets from an Idea I either assign Story, Task or Bug issue type.

Hopefully this helps.

I'm still trying to work out how to automate custom fields into preset fields in Software projects e.g. I create an estimate/hrs field in Polaris and want it to populate in the original estimate field in the Software project - currently waiting for someone to get back to me as it's a bit different trying to automate custom fields from Polaris into Software projects.

Good luck

[CC]

***Caution on the automation*** I have a bug ticket pending.  I put the automation in place as described on the page and it worked great when I create delivery issues.  However, when you link an existing issue to an idea in JPD, the data on the JSW side is deleted. I delete a bunch of the descriptions on the JSW side and had to manually re-add them.  @Ashebe.Pierre @Tanguy Crusson

[Tanguy Crusson]

I believe @Hermance NDounga recently looked at how the automation rule should look like if you link existing issues (vs create) and treat that case differently. Is that right Hermance?

[Hermance NDounga]

@CC  

Indeed, if you set up this rule and sometimes you create tickets from within JPD, and sometimes you link existing tickets (with existing description), in both cases, the Jira Product Discovery *idea* description will be copied. 

In that case,you can simply add a condition, checking that the description is indeed empty, before copying the description. 

This is how it looks like on the rule 

Don't hesitate to check out our documentation regarding automation to find more about triggers, actions, and conditions to make sure you adapt your automation rules to your use case : Automation Overview 

Cheers, 

Hermance

[CC]

Merci Beau Coup!

[Deleted user]

Hi Tanguy! 

The Loom video in the article is outdated. most of the actions she's referring to are not possible in the current product version.