Alrighty then - as we know, by default users are shown ALL the fields available for a screen and they have to go in to the Configure Fields menu to hide the ones they don't want to see (as some are only relevant in certain cases).
Is there a way to make it I can specify which fields are actually shown by default and then users can use the Configure Fields option to show any additional fields they want, as opposed to hiding the ones they don't need?
For now, I would recommend that you do the following on the feature request ticket :
* Vote, so that it will receive more attention
* Watch it, so that you will receive any and all updates
* Comment, and give your opinion on the matter
Please note that the implementation of new features and improvement requests falls under Atlassian's Implementation of New Features Policy.
It depends on what screen do you want to make those fields default for, as you can specify the fields which are associated with each screen by default. For example, you can customize the Create Issue screen to only include those fields that you require for your project, and hide other that are not required. You may refer to the following links for more details:
Please let me know if I missed anything, and I will be happy to assist further. ;)
Ah right, some context is useful here.
So we've got a few fields that are useful for certain people when creating an issue, but not everyone.
As with all users, they hate change and they are being pathetic at using the 'Configure Fields' menu - I keep getting "but why do I have to hide what I don't want??". It seems like a fair question I guess.
So what I want to do (or have the option to do) is have is so that I can specify which fields, from the ones that are available for a certain screen (let's say it's bug creation screen) are displayed for everyone, then any additional fields could be available under the 'Configure Fields' menu for people to turn them on when they need to.
In this scenario, about 90% of users only need the smallest set of fields.
Does that make sense? I know you'd think "well, just limit the available fields to the ones that are needed" but in the act of covering all the bases and making it as frictionless as possible, that's what we've done. Unfortunately it's added more friction for the people who don't need some of the custom fields.
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