Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Jira automation rule to prevent user from modifying a field unless a member of a group

I've been trying to figure out how to reset the value of a single select dropdown to its previous value if a user who does not belong in a certain group, changes the field.

So far this involves a field value changed trigger, and then an if block to check if the user is not in this group.

The Edit Issue action I would hope would set the value back to what it was, but I havent got that far yet.

This is for cloud standard, on a classic project.

 

 

3 answers

1 accepted

0 votes
Answer accepted

Took me some days but I created a Field Value Changed trigger on the Severity field (for all operations), added an If Block user condition with the user who triggered the event with a check to see if they were not in the specified group. Then, and and Edit Issue field on the same field, with a smart value rule of 

{{fieldChange.fromString}}

The downside is that if the user can't change the field, they think they have but next time the screen is refreshed it will revert to the old value. 

Mykenna Cepek Community Leader Jun 14, 2021

You could also consider notifying the user who attempted the change, to let them know that their attemped change was reverted. An "Email" action would do that.

Hi @Steven Rhodes 

Yes, and...to the answer: This seems like an opportunity for a conversation with people changing things when not in the team's group.  What problem were they trying to solve by doing so?  Understanding that may help them and your team.

Best regards,

Bill

0 votes
Mykenna Cepek Community Leader Jun 10, 2021

Seems pretty straightforward, but I admit that Jira Automation can be a bit confusing.

Which specific part of this are you stuck on?

@Steven Rhodes Why do you want others who is not in your group to edit the field. Cant u set the permission to restrict the user from this group to edit the ticket.

Mykenna Cepek Community Leader Jun 10, 2021

My assumption was that most users can edit the ticket (and the specific field in question), whereas there is a group of users who should not be able to edit that one field.

Perhaps @Steven Rhodes can validate this assumption?

Standard Jira Cloud permission schemes do not have field-level granularity.

The assumption is that people with access to the project can create and edit issues, but only members of the project team should be able to change the field. 

In this case, it is a "Severity" field. I'm hoping that the smart values here will help me

https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvaluesgeneral---eventType--

---

{{fieldChange}}

Available anywhere smart values are supported, to access the value of a field that has changed. For example, if the Assignee of a field changes, you could add a comment to the issue to note who the previous assignee was, and who the new assignee is.

When there are multiple fields that have changed, {{fieldChange}} only contains the first changed value. If multiple values are changed, use # to iterate over these. For example, when setting multiple Fix Versions, then you can iterate over these using {{#changelog.fixVersion}}{{toString}}Learn more about using smart values with sections and lists.

Available properties

  • {fieldChange.fromString}} - Returns the previous value as displayed.
  • {fieldChange.toString}} - Returns the new value as displayed.
  • {{fieldChange.from}} - Returns the previous raw value, e.g. for a select field. 
  • {{fieldChange.to}} Returns the new raw value, e.g. for a select field.
Like Vikrant Yadav likes this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Marketplace Apps & Integrations

BigPicture 8.1 is here❗️🎉

In BP 8.1 you will find lots of new features on the way to boost your PPM and enhance your experience. To be on top of your game,  check our overview page for more details.

47 views 0 2
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you