Jira Software Cloud Automation Permissions

[Rich Steenwyk]

I'm trying to enable my first Automations on a Jira Software Cloud instance and the rules are consistently failing, I believe for permissions related issues, but I can't prove that.

The rule should create a new custom Issue Type named 'Project' when a new Version is added under the same Project's Releases.

The problem I have is that I always get an error stating "Project or Issue Type not set".

I'm having a hard time understanding what that error means.  The rule is explicitly scoped to a single project and the "Create a new" action definitely indicates the Issue Type it should create.

I initially thought that this was a permissions problem, and based on other community posts I've already confirmed that the Default Permission Scheme that's assigned to my Classic Project has the 'Project Role "atlassian-addons-project-access" set for all of the Issue Type permissions.

Any help would be much appreciated!

[Rich Steenwyk · Accepted solution]

Atlassian support solved this problem.   The rule's Create Issue Action needed to have Project set to "Same project as trigger" and not simply (the default) "Same project" -- which, at first glance, appears equivalent.

[Sachin]

Hello Rich,

I have tried it on my instance and I was able to make this work by changing Same Project to ProjectXYZ, and also assigning a Parent issue XYZ-1 unde the create a New issue action. This is because creating issue Issue type "Project" is a sub-task and needs a parent issue key or id. 

Hope it helps.

[Rich Steenwyk]

'Project' in my case is a custom issue type but it is not of type 'SubTask', it merely happens to re-use the same icon.

[Bill Sheboy]

Hi @Rich Steenwyk 

Are there any required fields that are normally set when you create an issue of that type? If so, were they set in your action for creating the new issue?

Best regards,

Bill

[Rich Steenwyk]

Other than the standard "Summary" field, no other fields are required.  I'm uspplying a static value for the "Summary" field in the Rule configuration, having backed off from a dynamic field in order to get something to work.

[Trudy Claspill]

Hello Rich,

Welcome to the community.

Unfortunately, I can't provide a solution, but I can confirm that I see the exact same thing when I constructed the same rule.

[Rich Steenwyk]

Reached out to Atlassian for support on this one