As above. If users go to add a quick ticket to the backlog, they get this ridiculous screen with every possible field on it. I understand that with multiple projects it could be hard to know what fields to show, but showing every single one is not a solution. In any case, all of these projects are configured the same, with very few fields on the create screen and only 2 obligatory.
How can I have the ticket create from board just show fields relevant to the projects on the board?
>it could be hard to know what fields to show, but showing every single one is not a solution
So how does it know which fields you want? Although, if all the projects are configured the same, then they'll be using the same lists of fields.
I think you need to take a look at your issue create screens for the projects, and maybe field configurations too,
Thank for your reply Nic. I guess I'm trying to get an understanding of what exactly prompts JIRA to remove the quick ticket feature where you don't need to fill in a create screen (I'm getting "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue.")
All the projects on the board have the same Issue Create Screens (same ITSS's) so it's not that and they also all have the same Create screens. I guess when I said 'it could be hard to know what fields to show' I was trying to imagine the cause, but I can't really figure it now. What could I change in Field Configurations to fix it?
I currently have no FC schemes configured and the only existing FC is the default one (new instance of self-hosted JIRA).
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