Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,545
Community Members
 
Community Events
176
Community Groups

User Is In Group Custom Field

We found this Condition "User Is In Group Custom Field" on Workflows.

It seems this only allow user can modify the custom field on Development mode 

Would you can help provide step or video in details  to teach us about only allow user can modify the custom field on Development mode 

1 answer

1 accepted

0 votes
Answer accepted
Fabian Lim Community Leader Dec 19, 2021

Hi @Wolf_Chen2

Welcome to the community!

Can you explain what you mean by development mode?

Regards 

Please see mark red in below picture

 

Test.jpg

Fabian Lim Community Leader Dec 19, 2021

Here is a video that shows how conditions work: 

https://youtu.be/1ZKVN0VeaB4

Regards 

We has add some custom field “Duplicate Steps and Long Description” on my bug as below screen

Would you can guide us that how to allow user only modify Duplicate Steps and Long Description but cannot modify other custom field via use this condition “User Is In Group Custom Field”

 

t1.jpg

Workflow conditions are used to control who can use a particular transition; they cannot be used to restrict editing of specific fields directly.

Indirectly, you could:

  1. Make a new screen with your two custom fields
  2. Put that screen on an "any" to "any" transition (i.e. the source and destination statuses are "any", so that when you transition the issue, it ends up in the same status it was in).
  3. Put a condition on that transition to restrict it to the user(s)\group(s) you want.

This results in a new transition that does not change status, but allows this set of users to edit the fields.

Hi Haddon,

Thanks for your help and suggect.

Would you can help close this tick on your  side?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events