Create delivery tickets does not copy description, attachments etc to Jira ticket
Asked by Roeland Schoppers:

Hey,

When I have a JPD Idea and I click ' Create delivery tickets' all it does is create a ticket in Jira with the same title. It doesn't copy over the description and attachments etc.

<br />

Is this a bug or the way the system works?

<br />

Seems like you would have to do a lot of double work, copying over everything into the delivery tickets. When from my perspective, the whole idea is that you prepare all info in JPD and then when it's ready for development, push it into Jira - with all the info - to start the development process?


Answers:
author: Nick H
body: Hi [@Roeland Schoppers](/t5/user/viewprofilepage/user-id/4275673) ,

It's currently a known limitation - with the workaround to use an automation to copy the idea's description, attachments, etc. to the delivery ticket when created. You can find that configuration at the top of this other Community page: [Product demo: Automation for Delivery](https://community.atlassian.com/t5/Jira-Product-Discovery-articles/Product-demo-Automation-for-Delivery/ba-p/2057152) - but it might look something like this:

![desc1.jpg](https://community.atlassian.com/t5/image/serverpage/image-id/304651iA24380058D37873E/image-size/large?v=v2&px=999 "desc1.jpg")

We have an open feature request for this functionality out-of-the-box entered with engineering so hopefully it considered in the future.

That ticket for reference is **JPD-149**. Our feature requests are not publicly available at this time like other Atlassian products, so following the Community for product updates would be our suggestion.

comments: author: John Magro
body: [@Roeland Schoppers](/t5/user/viewprofilepage/user-id/4275673) I have been using the automation that Nick describes above for a several weeks and works like a charm until there's a new improvement baked in


author: Roeland Schoppers
body: Thanks [@Nick H](/t5/user/viewprofilepage/user-id/2540930) Nick this works!


author: Roeland Schoppers
body: [@Nick H](/t5/user/viewprofilepage/user-id/2540930) one issue i ran into with this automation is that when I link an existing jira ticket with a description to a JPD idea then the automation removes the existing description and replaces it.   

Our use-case is that when you create a delivery ticket from JPD idea - that should contain the info from the JPD idea. Not if you link existing tickets to it. (Create delivery vs add a delivery ticket).   

I couldn't find a clean way to do this in the automation - if I use ' issue created' as a trigger and set condition that it implements a related ticket - then I can't tell the automation where to copy the description from - since the only options are ' trigger' ' parent' ' child' ' destination' ' current issue' and none of those refer to the JPD idea it's created from unfortunately.   

I tried for this rule to set a label 'JPD-delivery' as label and then have the trigger be 'issue linked' like your suggested automation rule - and add a condition IF label is ' JPD-delivery' but unfortunately that rule will run before the 'issue created' rule has added the label.   

The only workaround I could think of is to set a condition ' IF description is empty' - should cover it but I can imagine it's still going to lead to some annoying edge cases.


author: Gergely Feh?r
body: In our environment there are 2 ways to work with ideas - then initiatives, epics. Some of the teams keep the business reasoning in the ideas, they create initiatives/epics totally separately and do not want to have the same informations in those tickets - the link is totally enough for them. Some other teams always create an epic from an idea, in that project we set up automations that copies the info needed on both tickets. So for me, it seems ok - you can work in both ways with the existing functionalities.

comments: author: Karie Price
body: Similar sentiment here. Breaking down an idea into epics/stories is separate for us as it allows us to break the work up in a way that best supports our development team. Linking back to the idea is good enough for us.


author: Rohan Swami
body: Hi all, thanks for the feedback. We're exploring how we can improve in this area of the product. We'll share more in the Community when we're ready!

In the mean time, [@Roeland Schoppers](/t5/user/viewprofilepage/user-id/4275673) [@Abby Kiesling](/t5/user/viewprofilepage/user-id/5096665) would you like to discuss your pain points over a short Zoom call so we can incorporate your feedback in our solution design? Here's my [Calendly link](https://calendly.com/rswami-atlassian/customer-calls).

comments: author: Abby Kiesling
body: Done! Thank you!


author: Abby Kiesling
body: Agreed. This is super annoying.