Making the field non-editable for few users

Can we make custom field during issue creation non-editable for some of the user on the basis of Project role condition as I believe there is no option to hide the particular field.

2 answers

0 votes

No. This is pretty much the same as your earlier question about field security.

You CAN do this by moving edit into the workflow, but that workaround doesn't apply to the create transition. I could explain more if it might be useful, but it would only help you if you are willing to accept that the field would not be entered on create, just become available to the power-users after create?

yes but if I go with workaround for edit transition too.I would then use a workflow action to basically specify the value, correct? Then same value will be appear in the issue and can be edited by few users, correct?

yes but if I go with workaround for edit transition too.I would then use a workflow action to basically specify the value, correct? Then same value will be appear in the issue and can be edited by few users, correct?

You could set it with a post-function on create-issue if you wanted to, yes.

After creation, it'll appear on-screen for everyone, but not on edit screens for anyone. You then protect the edit of the field with conditions in the workflow.

Do you mean that it is not necessary to specify it under workflow action and can just saved the issue once created (With the screen where specific Custom field is not present)? .

If yes, will it show some default value on screen later on which can be edited by few users on the basis of Project role Conditions?

All the above, I would like to understand the role of Workflow transition to make the fied "Protected"?

Sorry, your first paragraph makes no sense to me, which makes the second a bit hard to answer as well

The trick with the workflow is simple - don't put the field on create or edit screens. Only put it on view and a transition screen. Then protect the transitions you want to change it on with conditions.

Last part of your statement helps me to comprehend. Thanks!!

Ah good, I wasn't sure it made much sense, as I'm not sure of the question, but if it does, great!

Do you mean that it is not necessary to specify it under workflow action and can just saved the issue once created (With the screen where specific Custom field is not present)? .

If yes, will it show some default value on screen later on which can be edited by few users on the basis of Project role Conditions?

All the above, I would like to understand the role of Workflow transition to make the fied "Protected"?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,095 views 13 18
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot