You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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).
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.