Automating Epic Creation Issue When Idea Status Changes

Furkan Akduman March 21, 2024

I would like to set up an automation where changing the status of an idea in the Product Roadmap project triggers the automatic creation of a delivery ticket (Epic) for me. I've managed to create an Epic when the status changes, but it doesn't appear under the 'Deliver' tab, nor does it show the link in the Idea details. How can I configure this automation properly?

4 answers

0 votes
Pieter Helsen
Contributor
March 27, 2024

Hi,

My approach is a little different. Instead of automating the creation of the Delivery Ticket/Epic, I automate the status transition upon creation of a Delivery Ticket (along with some other tasks such as creating documentation in Confluence and creating some placeholder tickets under the delivery ticket).

The reason why: typically the title of my ideas is long and I typically summarize the Delivery Ticket name so that Epic badge in the engineering backlog is easily readable. 

For example:

Screenshot 2024-03-27 134732.png

  • Idea summary: Research what our customers want from a dashboard
  • Epic summary: dashboard research
0 votes
Ka Silveira
Contributor
March 21, 2024

@Furkan Akduman I create this automation:

2024-03-21_14-51-41.png

and it works perfectly!

I change my Idea status so a new epic is created and linked to my Idea:

2024-03-21_14-53-28.png

It's no necessary to pay a license for automation user! Please verify if your automation is configured by your two projects (Jira and JPD). Check if you are using the correct link (implements if you are editing epic, "is implemented by" if you are editing the Idea.

Furkan Akduman March 21, 2024

Thank you so much for your help 🙏🏼 I have understood the problem as i described below: I encountered an error due to the absence of the linked Issue field on creation screen. 

Like Ka Silveira likes this
0 votes
Ka Silveira
Contributor
March 21, 2024

Hey @Furkan Akduman the problem can be the link you used to vinculate your Epic and you Idea. The link used on JPD is a new "Polaris issue link" (Implemented by -> Implements). Take a look on this!

Karin van Driel
Contributor
March 22, 2024

Hi @Ka Silveira 

Somewhat off topic, but thank you for adding a new word to my vocabulary, had not heard the word 'vinculate' before! :) 

Like Ka Silveira likes this
0 votes
Nick Haller
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2024

Hi @Furkan Akduman ,

You should be able to find a similar preexisting automation template under each of your JPD projects' Automations tab for this exact use case.

You'll just want to select which Jira project the delivery is created under, as well the issue type (such as an Epic):

delivery1.jpgdelivery2.jpg

Furkan Akduman March 21, 2024

I have got an error (attached), do you have any idea about this, I have used the default fields come from the template but messages highlight field ignored (Linked Issues). 

image.pngimage.png

Nick Haller
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
March 21, 2024

I would switch the Actor of the automation to yourself (or someone that can create the Epic), then retest.

If that is successful, then it's most likely an issue with the A4J (automation for Jira) user, and them not having JPD permission. You'll have to open a ticket with the JPD support team to enable this user / permission: https://support.atlassian.com/contact/

Like Furkan Akduman likes this
Furkan Akduman March 21, 2024

Finalllyyy 🥳, I have solved the problem, here is the solution, the thing is not related with an actor,

  • The linked issue field is not included on the create screen

I have edited the Epic creation screen & add to linked issue field, the automation is working now    

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events