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..
Jira does not do field level security, so you can't show/hide per group.
field level security not yet available in jira, check the following plugin it may help you
on which screen you want to configured for roles? on view screen or transition screens?
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")
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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!
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