The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Creating a delivery ticket: automation to append the summary

Martin
Contributor
August 2, 2024

Good day,

 

I am familiar with automation. I am creating a new JPD project and new JS projects for a new team.

When creating an EPIC as a Delivery Ticket, I want to append the name automatically and insert the ID of the JPD ticket. 

 

I know I have to use the JSON configuration, but so far, I can only append using the EPIC key, but I need the key of it's parent (polaris). Any idea?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Hermance NDounga
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
August 5, 2024

Hello Martin, 

I'm not sure why you'd need to use JSO for this. 

You can start from the two template that have been created for Jira Product Discovery and that can be found under global automation to see how you can flow data from the idea to the epic. 

Where do you want to include the ID of the JPD ticket (or for which reason)? 

Best Regards,
Hermance
Product Manager @ Jira Product Discovery

 

Martin
Contributor
August 5, 2024

Hi Hermance,

 

When the portfolio team creates an Epic (Delivery Ticket), they want to always have the ID of the JPD idea in the name. For sure, we can do it manually, but we want to automate it. So the rule is, when created, rename the ''summary'' with the Summary + idea Key.

 

I'll check the templates.

TAGS
AUG Leaders

Atlassian Community Events