automation rule for a JWM project

[KOBAYASHI HIROKAZU (JIT TRI)]

I am creating an automation rule for a JWM project. When I set the actor to Automation for JIRA, the following error message appears and I cannot create it. The rule actor for this rule does not have the following permissions required CREATE_ISSUES (project 10494) What could be the cause?

[Tomislav Tobijas]

Hi @KOBAYASHI HIROKAZU (JIT TRI) ,

As got from the error message, it appears that this system user doesn't have appropriate permissions. Just to confirm - are we talking about team-managed or company-managed project?

If talking about company-managed, navigate to Project settings > Permissions and check if Project Role (atlassian-addons-project-access) has the following permissions:

• Browse Projects
• Crete Issues

I would say this is a 'standard way' to configure permission schemes when it comes to system or third-party apps that need to access particular project and/or issues.

Hope this helps.

Cheers,
Tobi

[KOBAYASHI HIROKAZU (JIT TRI)]

@Tomislav Tobijas 

Thanks for the reply.
This is the automation we are using at team-managed.

[Tomislav Tobijas]

Hey @KOBAYASHI HIROKAZU (JIT TRI) ,

Apologies for the late reply - it's been a hectic few days.

I've just tested automation in one business team-manage project and it all works as expected (even if the project access is set to 'Private').

As @Bill Sheboy mentioned below, can you share screenshots of the automation audit log?

Also, few questions:

1. What's the project access set to (private, limited, open)?
2. What's the rule scope (is it a single project, multi-project or global; you can check that in "Rule details" tab of the rule)?
3. How's the create issues action configured?

It would be best if you could share some screenshots so we can try to find out what's going on.

Cheers,
Tobi

[Manoj Gangwar]

Hi @KOBAYASHI HIROKAZU (JIT TRI) You need to grant the create issue permission for the automation for Jira user by adding the "atlassian-addons-project-access" user in your permission scheme.

[KOBAYASHI HIROKAZU (JIT TRI)]

@Manoj Gangwar 

Thanks for the reply.

Authority is still attached.

[Bill Sheboy]

Hi @KOBAYASHI HIROKAZU (JIT TRI) 

When and where are you seeing that error message:

1. When the rule runs, and the rule has the Issue Created trigger, the error shows in the audit log
2. When editing the rule and changing the actor, the error immediately displays in the rule details

If it is the first one, that symptom can be caused by a known, racetrack error for the Issue Created trigger: the rule starts running before all of the data is available, leading to weird errors / unexpected behavior.  The fix for this is to always add the Re-fetch Issue action immediately after the Issue Created trigger.  This will slow down the rule a bit and reload the data before processing continues.

Kind regards,
Bill