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

Question

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

Screenshots of my automation rule

Bill Sheboy · Answer

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

JCameron_8s6jjj · Answer

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.

JCameron_8s6jjj · Answer

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.