nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Product demo: Automation for Delivery 🤖

Hermance NDounga

Hi everyone 👋🏽

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 manual work between Ideas and Epics:

Copy Description from Idea to Epic ✍🏼

Watch the demo video

Detail of the rule:

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"

Transition an Idea to Done when the Epic is Done 🚀

When 1 Idea is linked to 1 Epic

Watch the demo video

Detail of the rule:

Global automation from the Software project

When: Issue transitionned > 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 transitionned > 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

Transition an Epic to Done when all linked issues are done ✅

View the rule in our public library

Detail of the rule:

Single project automation in a software project

When: Issue transitionned > To Status > Done

Branch rule / related issues: Epic (Parent)
Conditions: Issue field condtions > 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

Sync issues between dates in Jira Software and dates in Jira Product Discovery

See this discussion

Best practices regarding formatting

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:

Edit/populate a Jira Product Discovery date field

{
    "fields": {
        "customfield_0000":"{\"start\":\"{{now.jiraDate}}\",\"end\":\"{{now.jiradate}}\"}"
}
}

Edit/populate a Jira Product Discovery checkbox field

{ 
    "fields": { 
        "customfield_0000":1 } 
}

For more info for how to use Automation with date fields (e.g. to calculate a project's end date based on start + effort + % allocation), check out this great video by Robert DaSilva: Dates, Automation and JPD

Add watchers to ideas from People fields?

Details in this post. They will receive notifications whenever the idea changes.

Thank you for this solution @Aaron Mosny 👏

Questions, comments, suggestions? Let's discuss in the comments below!

Cheers,

Hermance

Comments

Matt Schroyer_9wcb58

Does #1 work for any issue type like is we use higher level initiatives? UPDATE: nvm it does

Hermance NDounga

Hi Matt,

Yes, it actually work with any Issue type you'd have in that Software project, just like from Jira Product Discovery, you can create any issue type from the delivery tab of an idea. So this rule is indeed to be adapted to the Jira Software issue type you'd like to create from a Jira Product Discovery Idea

Nikki DuBois

@Hermance NDounga is there plans of implementing automation especially to gain customer feedback that then automates that data to review?

Mike Gargano

Hey @Hermance NDounga ,

The video links don't seem to be working for me. Are we able to get some updated links?

I am very interested in automating task between ideas and other jira projects, but keep running into snags with selecting the proper fields.

Hermance NDounga

@Mike Gargano the links have been fixed, sorry for the inconvenience !

Ronald de Groot_lplwmn

@Hermance NDounga thanks for the video. I followed all the steps but I get an error 'The following issues did not match the condition:'

See attached. I have no idea what is going wrong. Can you help me with this?

Hermance NDounga

Hey @Ronald de Groot , sure! Could you please open a ticket, using the "Give feedback" tab on the left panel of Jira Product Discovery, so we can start discussing via email ?

Don't hesitate to include more details about the projects you're setting up and more screenshots of the rule

Ronald de Groot_lplwmn

@Hermance NDounga I have send in the feedback, I was not able to send some screenshots. Attached the screenshots

Schermafbeelding 2022-11-29 om 14.14.23.png

Louise Baker

I am trying to set up automation for 1 or more epics linked. This is the condition listed above to apply:

Condition: Issue matches JQL: issuelinktype != empty AND issuetype = Epic
AND Linked issue match > Type: relates to > Match: StatusCategory = "Done"

That is pretty intense. Where are all the steps to complete this? How does one build this out? Can we have a video walk through of this?

CC_pcyuge

I had an issue with #1. I submitted a bug ticket. I found that when I Added an existing JSW issue to an idea, the description was deleted on the JSW side.

CC_pcyuge

@Hermance NDounga I had an issue with #1. I submitted a bug ticket. I found that when I Added an existing JSW issue to an idea, the description was deleted on the JSW side.

Jamey Hawkins_x1599y

I'm attempting to use the advanced fields option with date population. How can we find out the custom field id for PD specific fields? I tried to use the Custom Field name and it bombs. Thanks.

Ok found the customer field id, but I am now receiving the following error:
Error while parsing additional fields. Not valid JSON.

I used the example above for date fields and it continues to throw the error. Any insight?

Summary: I am trying to get a date when an idea is transitioned to a certain status and then eventually push it over with the epic in delivery.

Thanks!

Hermance NDounga

@Jamey Hawkins , Hi !

Based on your screen shot it seems you wrote everything correct... Could you please open a support ticket support.atlassian.com so they can check what might be the issue?

Can you please let me know why you are looking to have the date of an idea updated written on an epic? Just for me to understand what's the use of the data afterwards, so I can think about an alternative?

Abby Kiesling_nd9vyp

@Hermance NDounga How can I determine the custom field ID for discovery fields? They don't show in global settings under custom fields and even exporting all ideas with all fields doesn't show it. I also tried editing the fields and seeing if I could derive the ID in the URL, but that doesn't work either.

Michelle Yip_vmosd9

Hi @Hermance NDounga !
Thank you for sharing this.

Will the team at Atlassian consider to add more automation templates to the JPD library?

discovery automation.PNG

Timo Fitzner_kyrakh

@Abby Kiesling I still don´t know how exactly but I found a workaround. If you create a normal custom field for testing (e.g 10000) or you know by any chance the last custom field you created remember the ID.

Now create a custom field in PD; since it´s the newest, it has the ID 10001. Now you can use it.

But it´s not practical if you want to have the IDs from other custom fields. I hope someone can explain to us, how to obtain the ID from PD fields.

Abby Kiesling_nd9vyp

Hi @Timo Fitzner , someone else helped me with a link that gave me ALL my custom fields, PD included. It's great. Here's the format:

https://YOUR-COMPANY-URL.atlassian.net/rest/api/2/issue/ISSUE-KEY?expand=names

Replace YOUR-COMPANY-URL and ISSUE-KEY of some ticket in the pd project. Then copy/paste the output into a JSON tool to make it pretty or convert it to CSV. Viola!

Timo Fitzner_kyrakh

@Abby Kiesling Nice! Thanks a lot!

Kyren Cabellon

Thank you for this! At first I did not understand the last automation but it made sense when I read it again haha

Omar Bennani

Hi! Any suggestions on how to update custom fields between JPD and the rest of an instance just like the description? I have the exact same automation setup for a custom multiselect (Brand) field that I tried to make as 1:1 as possible but it doesn't copy anything.

jira automation screenshot.png

Hermance NDounga

Hi Omar,

The Description field is a *shared* field , so it's the same between Jira Product Discovery and other Jira products. For custom fields - unfortunately I'm not an advanced user of Automation for Jira - you might need to open the "More options" JSON editor

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Nathan Belen-Carmody

Similar to @Jamey Hawkins comment on April 23, 2023. I am also receiving an error with the following JSON.


Error while parsing additional fields. Not valid JSON.

@Hermance NDounga do you know if a ticket was created for this issue?

Context: I created an automation rule to record today's date whenever a specific custom field is updated.

Thank you!

Dana Weinbaum

Hi Hermance,

Perhaps you can help with how I can create an automation that will update a custom field "Bubble up" with a date in the future (3 months from today) when an Idea is transition to a certain status?

I can't find the custom field in the list of fields.

(This is taken from the great video of 'How one team in Atlassian uses Jira Product Discovery - part 1 (ideation & triage)'

Thanks

Dana

Sebastian Pechhold

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 transitionned > 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

I dont understand it i guess.. Can you please explain the condition settings in detail? I am stuck at conditions for multiple delivery issues. When i try to copy paste your conditions it leads to errors. I am not an expert in JQL yet.

PLEASE HELP

Mirko Grahnert_p1eahn

@Hermance NDounga on the first automation (Copy Description from Idea to Epic ✍🏼):

What condition would I have to set up so that the automation only triggers if the idea is in a specific status?

Hermance NDounga

@Mirko Grahnert

The Condition "issue field condition" and the field status. this is the first one presented n the documentation : https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/

To learn more about automation, please check this automation guide : https://www.atlassian.com/software/jira/guides/automation/overview#rule-status

Mirko Grahnert_p1eahn

Thanks @Hermance NDounga This is what I had tried initially, but it led to the automation not being triggered because one of the issues that was linked wasn't in the status that I had specified. 🤔

Dana Weinbaum

@Hermance NDounga Hi and Happy New Year!

I'm trying to implement the automation to transition an idea to done when it's linked to 2 or more Epics and I can't work around the query. When I pasted the condition it returned an error.

If I try to break it down:

issuelinktype != empty ==> ok, means that the issue that was transitioned to done has at least one linked issue to it.

issuetype = Epic ==> clear, I'm looking for Epics only

linked issue match > type: relates to ==> that search text returns an error. I'm able to replace it with issuelinktype = 'related to' ==> the Epic has a linked issue of that type

> match: statusCategory = "Done" ==> I know what I'm looking for - validate that the linked issue of type related to is Done, but that query doesn't work and I don't know how to replace it.

What am I doing wrong?

Thanks!

Hermance NDounga

@Dana Weinbaum unfortunately the reason it works or not can be multiple just from top of my head I can think of team-managed projects vs company managed projects, custom issue types in you JSW projects, or even conditions on your workflows statuses. Could you please open a support ticket so our support engineers can take a look at the logs in your rule (if you can mention specifically which projects and which rule it would be awesome -> support.atlassian.com/contact

Tim Sanford

@Hermance NDounga - it appears that this rule can no longer be used because the Idea is no longer a linked issue?.....just asking because I cannot get the rule to work.

Transition an Idea to Done when the Epic is Done 🚀

When 1 Idea is linked to 1 Epic

Here is the error in my log:

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

automation

delivery