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; } } }

Automation of Status between Jira and Jira Product Discovery

Tim Sanford

I need help figuring out what is going wrong in my automation. I'm using a global automation template so that when a linked feature is moved to Generally Available (Done) the rule will then change the linked Idea in JPD to Done. The rule runs but gives the following error each time. It identifies the changing Feature, as well as the linked Idea from JPD, but does not transition the Idea's status to Done.

Accepted answers

Nick Haller

Hi @Tim Sanford ,

An automation like the one below should work for your use case:

^ When a Jira issue is transitioned to Done, the rule then transitions any linked issues / ideas to Be Gone! Note the Scope of this rule is set to Multiple projects with both the Jira and JPD projects selected.

Another thing we're noticed with other customers is their Automation for Jira (A4J) user not being granted JPD product access. This is a known bug, and engineering is currently working on a fix.

In the meantime, the workaround would be to adjust the Actor of the rule to a user who has JPD permissions (creator).

All comments

Nick Haller

Hi @Tim Sanford ,

An automation like the one below should work for your use case:

Another thing we're noticed with other customers is their Automation for Jira (A4J) user not being granted JPD product access. This is a known bug, and engineering is currently working on a fix.

In the meantime, the workaround would be to adjust the Actor of the rule to a user who has JPD permissions (creator).

joachim ramberg_2o8afx

Hi,

When I move something to Done in my company-managed project the idea it implements is moved to the last step in JPD with the automation below. Hope it can help you in some way.

Screenshot 2025-01-16 at 21.23.32.png

Bill Sheboy

Hi @Nick Haller

Thanks for your answer, as this question is getting asked more and more :^)

Please consider changing your link for Scope to the one in the documentation to explain the differences: https://support.atlassian.com/cloud-automation/docs/create-and-edit-jira-automation-rules/#Edit-the-details-of-a-rule

Kind regards,
Bill

Isaiah Lee

Hi @Nick Haller ,

Is there a tracking link for the bug fix for this bug where the A4J user is not granted JPD access?

Thanks,

Isaiah

Kh_Safal

@Isaiah Lee, this topic has been locked because the thread has become a bit dated. If you’d like to keep the conversation going or have additional questions, we encourage you to start a new topic. You can read more about necro posting (“raising threads from the dead”) in our Community Guidelines.
Thanks!

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-product-discovery

jpd