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 to edit custom cascade field based on user permission

Natalia Trofimov

Hi, I need to create the automation to allow editing of a custom cascade field based on user permission (i.e. group)

Something like this

Screen Shot 2022-10-20 at 4.32.15 PM.png

Accepted answers

Alex Koxaras -Relational-

Hi @Natalia Trofimov

The best approach would be to:

Make the specific field read-only (meaning remove it from the edit issue screen)
On the workflow(s) of your issue type(s) create a self transition called e.g. "Change Field Value"
On that transition add a condition to be visible only for user who belong to your desirable groups.

All comments

Alex Koxaras -Relational-

Hi @Natalia Trofimov

The best approach would be to:

Make the specific field read-only (meaning remove it from the edit issue screen)
On the workflow(s) of your issue type(s) create a self transition called e.g. "Change Field Value"
On that transition add a condition to be visible only for user who belong to your desirable groups.

Natalia Trofimov

Hi Alex, I tried it, and yes, it works but it is messing up with all my other automations and the issue security levels that are based on that custom field. they stopped working

Alex Koxaras -Relational-

@Natalia Trofimov morning!

For your rule to work I would keep only the components to edit the old value. The rest, as I see it, are obsolete. Then edit the issue and use the advance editing field and enter the following JSON:

{
    "fields": {
       "YOURFIELDNAME": { "value": "{{#changelog.YOURFIELDNAME}}{{fromString}}{{/changelog.YOURFIELDNAME}}"}
   }
}

Replace the YOURFIELDNAME with your field.

Example of my rule below:

advance editing.png

Natalia Trofimov

Hi Alex,

the automation didn't work for me well so I used your first approach with the workflow transition. I just added the "transition" in addition to "edit" and "create" in other automation rules on the value changes and it worked!

Screen Shot 2022-10-21 at 12.59.06 PM.png

Thank you very much for your help!!!

Natalia

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud