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,465,232
Community Members
 
Community Events
176
Community Groups

How to lock field values?

When I create an issue, all values can be changed anytime.

Is it possible to lock specific fields on given condition?

E.g. we have larger workflow to manage issues.

At the first section of this workflow, full editing is welcome. Upon a specific status (e.g. approved) some field shall be unavailable for editing, but shall be visible in the issue.

I've seen following "possible" solutions:

  • adding to each status-transition an condition, that my specific field-values shall not be changed
    -> this is awful due to X-times copy and paste of conditions
  • adding read only custom field as target field for the values which shall not be changed up from a given status. Populate values via automation (oder workflow post-processor) and setup different screens to hide the edit field and display the copy field
    -> awful solution and fake, because changing values is possible.
  • split the workflow into 2 parts like "edit" and "fulfill" and create a new issue after the "edit" one is completed, sending the data to read-only fields of the new "fulfill" issue.
    -> this breaks the end-to-end view (and reporting) of the process

 

Is there another approach available to lock fields?

 

2 answers

2 accepted

1 vote
Answer accepted

Hi @Ingo Wenke _ RTI Group 

On cloud and on Jira software you can't lock field on conditions. You either place them on the create/edit screen (for users to edit them), or you don't.

If you want these fields to be on the created screen, then you should work with validators, to ensure that a specified condition should exists (e.g. user belongs to a certain group, or on a specific role).

Another thing you could do is:

  • to remove them completely from the create screen
  • Create a new screen and place them there
  • Create a new self transition and add the above screen to the transition
  • Add a condition to the self transition so that certain users can use it.

Doing the above will ensure that only certain users can use the above transition, meaning that only certain users can edit these fields.

On Jira cloud, there isn't a "field locking" permission. If you were on prem Jira, you could lock them using scriptrunner, but again you had to write some script.

0 votes
Answer accepted
Sachin Dhamale Community Leader Dec 05, 2022

@Ingo Wenke _ RTI Group ,

 

You can add the self transaction on each stratus and add the transaction screen on that self transaction with those field which you want to edit on that transaction screen.

For example - On In Progress Status you can add transaction from In Progress to In Progress and attach the transaction screen to that transaction and mention field which you want user to edit.

 

Accept the answer if it helps

 

Thanks,

Sachin

Suggest an answer

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

Atlassian Community Events