How can we do visibility of fields should be configured according to roles of users?

[Suresh]

Hi All,

The visibility of fields should be configured according to roles of users.

And also some fileds should be disable once the status has been change?

Can any help on this..

Best Regards,

Suresh

[Nic Brough -Adaptavist-]

Jira does not do field level security, so you can't show/hide per group.

You can try tricks with javascript (which won't stop the fields going to the user, just tells the browser not to show it), or writing your own fields, but the general advice is to look at the Field Security plugin.

[RambanamP]

field level security not yet available in jira, check the following plugin it may help you

https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs

on which screen you want to configured for roles? on view screen or transition screens?

[Suresh]

Is there any option like to disable the fileds once status have been change?

I mean to make non editable fileds once issue moved to another status.

[Nic Brough -Adaptavist-]

Sort of. Jira has four uses of "screens" and you use them.

Put all your fields on the create and view screens, then use a cut-down edit screen only containing fields you always want to be able to edit, then you won't be able to change the fields you've left off the edit screen.

When you decide you do need to edit the fields, you use transition screens in the workflow. For example, if you have a field called "approved by", you'd only put it on the transition screen between "unauthorised" and "authorised". (Also, you can protect the transitions with conditions such as "user must be in role of developer")