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.
×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).
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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.