Making the field non-editable for few users

[Rahul Arora]

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.

[Rahul Arora]

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"?

[Nic Brough -Adaptavist-]

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?

[Rahul Arora]

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?

[Rahul Arora]

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?

[Nic Brough -Adaptavist-]

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.

[Rahul Arora]

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"?

[Nic Brough -Adaptavist-]

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.

[Rahul Arora]

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

[Nic Brough -Adaptavist-]

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