For example: I want to hide unnecessary things like sprints, assignees, story points, etc. from my bug reporters, and give them a very simple "name, summary, description, attachment" kind of form for quickly filing bugs.
No, JIRA does not do "field level security". What you see on the "create" screen is the full list of fields you put on it. If you simplify it by removing fields that you don't need, you simplify it for all users.
There is a function for individuals to remove fields that they personally don't care about - look to the top right of the screen for that
JIRA Service Desk can be used to present very simplified forms to end-users. It doesn't affect people who are supposed to be in the project as JIRA users, and it severely limits the end-user interaction (they raise a request with minimal information, see a status, SLA and progress, and that's about it - the rest of JIRA does not apply to them). See https://www.atlassian.com/software/jira/service-desk
There is a "field security" addon which can hide fields by user - see https://marketplace.atlassian.com/plugins/com.quisapps.jira.jfs (This is not 100% "secure", in that users will still be able to find out that fields are there in searches, but not the actual content. That is a very minor flaw that 99.99% of users don't have any issue with)
One option could be to create a transition with a role-based condition in which you show a page with the additional fields that the role should enter. That way only people in that role will be able to add those fields. You could even add a condition so that the transition button be shown only if that specific field is empty.
I hope this helps.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
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