Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.

×
Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Update a Jira Product Discovery idea description when a Jira Software Epic description is updated

Zhifeng Koh May 16, 2023

I use Jira Product Discovery as well as (Company-managed) Jira Software. Currently, I only have 1 JPD and 1 Jira Software project each.

The process my team uses is that 1 JPD Idea <=> 1 Jira Software Epic. Oftentimes, details are written or updated in the Jira Epic over and above what has already been written in the Description field.

I am trying to create an automation that updates the JPD Idea Description field when the Jira Epic Description field is updated. However, my automation is not working (screenshots below).

  • What's wrong with my automation? All the rule details look correct.
  • My audit log is showing that my Branch Rule couldn't find any related issues
  • Are JPD ideas simply not supported by Jira Automation?

 

Audit log info

CleanShot 2023-05-16 at 15.44.39@2x.png

Screenshots of my automation rule

CleanShot 2023-05-16 at 15.42.00@2x.pngCleanShot 2023-05-16 at 15.42.06@2x.pngCleanShot 2023-05-16 at 15.42.21@2x.pngCleanShot 2023-05-16 at 15.42.58@2x.png

2 answers

0 votes
JCameron
Contributor
September 12, 2024

Did you ever get this to work? I'm trying a similar thing right now and my automation won't copy the description from my Jira issue to my JPD issue. It says that the "Description" field doesn't exist in my JPD issue. But I can't find any reference anywhere (including searching through Custom Fields) that indicate what it is actually called.

JCameron
Contributor
September 12, 2024

Answering my own question for future people - I had to set the automation actor to myself instead of "Automation for Jira". It was a permissions thing where their system apparently sees "Automation for Jira" as not having authority/licensing rights to modify JPD issues. Kind of silly.

Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 12, 2024

Hi @JCameron 

Well done solving your own question and please note Atlassian is aware of this symptom (according to other community posts).

By default, the Automation for Jira user has permissions to do most non-administrator things in Jira, but JPD is a different product and has a separate licensing model with named / configured users for Idea-issue create / edit actions.  If Atlassian granted those  permissions to the automation user, it would allow bypassing the licensing limits and controls for JPD.

Kind regards,
Bill

0 votes
Bill Sheboy
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2023

Hi @Zhifeng Koh -- Welcome to the Atlassian Community!

First thing, thanks for the details of the trigger, conditions, and actions.  Also, it can help to post an image of the entire rule to provide context for the parts.

Back to your question...Your JPD and Software Project are different, and your branch is limited to only linked issues in the Software Project (i.e., AUTHK).  I believe you instead want to branch to issues in the JPD project.  Please note this type of rule will need to be either global, or multi-project, in scope.

Kind regards,
Bill

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events