Since Issues are a Jira generic term to use for all sorts of items (whether client request, service request, enhancement, etc), we want to create issue types for other business units besides engr/dev. However, fields like affects or fixed versions, or components are not applicable.
Why are these not options to show on a screen and is there a way for me to hide them? I've created my own screens and associated to a screen scheme and defined for the issue types - so, these customizations I have made work fine. But, I just don't want these other fields as they cause confusion in View mode, even though they cannot edit them.
I have my Edit screen which is defined below as my default screen in the scheme.
All of these fields are showing up, in conjunction with those others mentioned.
My issue types are associated with an issue type scheme that is associated with my project.
Any my issue type screen has the correct screen schemes. Maybe I need a support ticket for this?
When I select this issue type, my create screen is correct. It's also correct when i edit. I just have these other fields which I expect are standard in my view - even though I don't have those on the screen for the view action. They are just not appropriate for this project and causes confusion.
Thanks for everyone's feedback and assistanc. I ended up inputting a support ticket. I'll update this based on what I find out from them.
The responses regarding setting up the screen schemes and issue type screen schemes are all correct and ones that I did.
The response provided by support was that I had to also set up a Field Configuration and then a Field Configuration scheme for my project.
I wanted to hide Priority, Affects Version, and Component. So, I created field configuration in which these fields are hidden.
Then I created a field configuration scheme and associated these issue types to that field configuration. I have one issue type that I need priority for so I'll create a separate field configuration for that.
Once I applied the field configuration scheme to my project, those fields were no longer visible in the Details section.
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