Automations in errors after setting permissions to project

[Reply Test Group]

Hi, 

I created some automation to value some fields, and they worked when the project had no custom permission scheme or issue security scheme.

Now that I created a custom permission scheme for the roles in my project, setting for almost all the permissions key the values:

• Project Role (Administrators)
• Project Role (atlassian-addons-project-access)
• Project Role ([GVDDP] Project Rule)

, the same automations didn't work anymore, returning all these 2 errors:

Action details:

- Unknown fields set during edit, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - ...

- No fields or field values to edit for issues (could be due to some field values not existing in a given project): ...

In the related WorkFlow, I added the propriety:

    jira.permission.edit.role = atlassian-addons-project-access

too, because only some group can modify the issue in some status.

I've checked my custom field configuration, reusing the default field configuration scheme or the entire permission scheme, but nothing works.

Can you please help me? 

[Reply Test Group · Accepted solution]

Thank you @Eric, 

the jira.permission.edit.projectrole.1 = xxxxx (Role ID) did the trick!

Bye.

[Dirk Ronsmans]

HI @Reply Test Group ,

Could you add the "Automation for JIRA" user to the permission scheme?

One would think that it is covered by the addons role but it seems that's not always the case.

If you can try this and it works, we can escalate this further to make sure that it becomes clear what the issue behind is.

[Reply Test Group]

Hi @Dirk Ronsmans 

I leave a screen of the permission scheme, issue related, and as you can see I add in the Edit Issues key the single user "Automation for Jira" :

Should I add him in some other permission key?

P.S. I create an automation only for executing an issue transiotion when a comment is added and it works, so the problem should exist only in the field configuration zone or something.. 

[Dirk Ronsmans]

Not immediatly to edit issues but does he also have the browse projects/view issues permission? 

That is pretty much a pre-requisite to do the others. If you can't see the issues/access the project you can't edit them.

[Reply Test Group]

Hi, 

I added it to the browse projects/view issues permission, but nothing change.

I tried to insert the Automation for Jira user directly in the status property interested by the automation too:

, but even this fails..

[Reply Test Group]

Hi @Dirk Ronsmans ,

I (kinda) resolved the problem..

Pratically I removed all the property key-value on the workflow statuses, leaving setted the permissions and issue security levels, and the automations work again.

I verified that, if you insert the properties:

- jira.permission.edit.group.1 = jira-administrators
- jira.permission.edit.group.2 = [GVDDP] Contributors Group
- jira.permission.edit.group.3 = [GVDDP] Validators Group

, instead of:

- jira.permission.edit.role.1 = Administrators
- jira.permission.edit.role.2 = [GVDDP] Contributors Rule
- jira.permission.edit.role.3 = [GVDDP] Validators Rule

, ALL the automations will break with the errors written in my first post.

The problem now is that:

- writing "jira.permission.edit.group = jira-administrators" in a workflow status, actually locks the issue for being edited in that particular status except for the Jira Admin (but the automations won't work),

- writing "jira.permission.edit.role = jira-administrators" in a workflow status, DIDN'T lock the issue for being edited in that particular status except for the Jira Admin (but the automations work again)

I need to lock the issue editability based on his status for some people, but I also need the automations to work..

Did someone have an idea?

[Reply Test Group]

Hi @Dirk Ronsmans 

it's possible to have a link to a library of all the possibilities of the property key-value usable?

I searched on the web but I didn't found anything official or nowhere near complete.

TY

[Dirk Ronsmans]

Hi @Reply Test Group 

Such a library does not exist or at least not that I'm aware of.

I have seen some sources reference the javadoc (api) as those would be the same values set

[Reply Test Group]

This is really disappointing.. 

In every case, leaving the freedom to the user to write practically everything in those property slots is madness! 

The user should be forced to enter only tags to construct the keys-values permissions, like:

, in a way similar to the inserting of the Issue transitioned statuses for the automations:

Anyway, thank you for your time, @Dirk Ronsmans .

Bye.

[Eric]

Hi @Reply Test Group ,

Just wondering if you have you tried setting jira.permission.edit.projectrole.1 to the ID of atlassian-addons-project-access ?

Based on https://community.atlassian.com/t5/Jira-questions/Edit-permission-to-a-project-role-just-in-one-workflow-state/qaq-p/931911, seems like you need to specify project role ID.

Cheers,

Eric