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

Creating and linking Ideas to a Jira Project using Automation

Guy Geron_fidbxy

Hi,

I'm trying to use automation to create an Initiative in a Jira project from an Idea in a JPD.

The creation is based on a status, and it works.

What I'm trying to do next is to link them.

On the idea side, I want it to show up in the Delivery tab, and on the Initiative side, I want it to have the implements link.

I've encountered an error in this process, and I'm hoping you can help me understand and resolve it.

I've added screenshots of the automation log error message and the permissions of the target project in my Jira Cloud Screenshot 2024-06-19 at 11.12.02 AM.png

Accepted answers

All comments

Angie Adams

Is the Actor configured in the rules details that is executing the task have permissions to link the issue in JPD? I found this was the error in my initial automations. I had to select a user with a creator license.

Guy Geron_fidbxy

Hi @Angie Adams ,

You are spot on! Thanks for helping 💪🏼

I wonder if I should create a dedicated user for Automation in that case.

Nick Haller

Hi @Guy Geron and @Angie Adams ,

We've noticed some customers running into the same issue, and their Automation for Jira (A4J) user not being granted JPD product access.

Unfortunately this cannot be adjusted on your end, and instead will need to be corrected by Atlassian support. Feel free to open a ticket with us, and we'll be happy to assist with this issue.

As Angie mentioned, the workaround until the A4J user has JPD permissions is assigning another user as the Actor who currently has JPD permissions.

Angie Adams

Thanks, @Nick Haller !

Guy Geron_fidbxy

Hi @Nick Haller ,

I've raised a support ticket

Cheers!

Guy Geron_fidbxy

This is a quick update for those who are following this thread. Atlassian has fixed the issue, and the Actor is set to "Automation for Jira," and it works fine.

Thank you, Atlassian! 🙏🏼

Welcome!

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

Quick Links

Find more posts tagged with

jira-cloud

automation

jpd