If a particular field needs to be hidden at all times, it is easier to hide the field in the relevant field configuration than remove it from all screens.
Can anyone explain how we can do this? also how to know which field was been hidden at all times by other administrator.
@Fahad Siddiqui , you will have to context this question to a project on which the screens and field configuration schemes are applied. You cannot get this done for all the projects in the jira instance unless they are sharing the same schemes.
coming to the answer, the field that is removed from the view screens are not displayed on the respective screen but can still be made available on the reports (existing issues data/ field data set using some post functions)
If you choose to use the field configuration 'hide', the hidden field is not available to the project's use at all.
And it will be easy for the admins to check on the field configuration scheme to see which fields are hidden in the project.
Thank you
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As @Fazila Ashraf said, you just need to Create or go to your project Field Configuration Scheme and edit it for each Issue Type of your project.
There you can define if you want to hide it, made it required, optional, or simply edit the information.
You can just remove the field of the screens on the Screen Schemes without hide them, and as said above, however, if you want to edit it for each issue in your project you'll need some automating plugin that edits it without needing it to be present in the screen, like Automation for JIRA .
Best Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.