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?
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:
@Furkan Akduman I create this automation:
and it works perfectly!
I change my Idea status so a new epic is created and linked to my Idea:
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Ka Silveira
Somewhat off topic, but thank you for adding a new word to my vocabulary, had not heard the word 'vinculate' before! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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):
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Finalllyyy 🥳, I have solved the problem, here is the solution, the thing is not related with an actor,
I have edited the Epic creation screen & add to linked issue field, the automation is working now
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.