About Jira Product Discovery
Transform product ideas into business impact.
While Jira Product Discovery doesn't have specific automation templates yet, it is possible to automate some actions in the delivery panel. Implementing these rules will reduce the need to manually work between Ideas and Epics.
Tip
If you are new to Jira automation you can start here.
Single project automation in a Software project
When: Issue linked > Link Type "Polaris issue link"
Condition: Issue field Condition > Issue type = Epic
Then:Edit issue > Field to set "Description" > ... Copy from "Destination Issue"
Global automation from the Software project
When: Issue transitioned > To Status > Done
Branch rule / related issues: Linked issues > Implements
Then:Transition issue > Destination status = Done
When 1 Idea is linked to 2 or more Epics
When an Idea is linked to 2 or more Epics, you need to link the epics together with the link type "Relates to"
Detail of the rule:
Global automation from the Software project
When: Issue transitioned > To Status > Done
Condition: Issue matches JQL: issuelinktype != empty AND issuetype = Epic
AND Linked issue match > Type: relates to > Match: StatusCategory = "Done"Branch rule / related issues: Linked issues > Is idea for
Then: Transition issue > Destination status = Done
View the rule in our public library
Detail of the rule:
Single project automation in a software project
When: Issue transitioned > To Status > Done
Branch rule / related issues: Epic (Parent)Conditions: Issue field conditions > Status does not equal Done
AND: Related Issue conditions > Related issues : "Stories or other issues in this epic", Condition : All match specified JQL, Matching JQL: Status = "Done"
Then: Transition issue > Destination status = Done
As some Jira Product Discovery fields aren't fully supported by Automation for Jira at the moment, here are known heads up on formatting for some fields:
1
2
3
4
5
6
{
"fields": {
"customfield_0000":"{\"start\":\"{{now.jiraDate}}\",
\"end\":\"{{now.jiradate}}\"}"
}
}
1
2
3
4
{
"fields": {
"customfield_0000":1 }
}
Was this helpful?