Is there any way to restrict values in the column list based on issue type?
Our instance has a large number of different projects some with the fields using the same name however used differently, e.g free text vs drop down etc. and there is no way to differentiate these.
Is there a way to restrict / hide specific fields in the columns like you can do in the field configurations when searching for issues. Would be nice if field configurations also controlled the fields in the column list.
No, the whole point of the search and display functions is that you can see any of it.
You could remove the "searcher" for a field, but that makes it completely non-searchable
The best thing you can do is sort out your "fielditis", rationalise, consolidate and simplify your field list, not try to bodge the display.
While in an ideal world that would be best, your talking about 15 different teams, with fields that can be the same name and different field types and the users are getting confused. Unfortunately using the same name when they are different field types is unavoidable.
Since there is no work around I believe the only solution is to rename all the fields to have appropriate acronyms at the start in order to differentiate between the issue types for each project. It just makes me laugh that the field configuration controls what you can search on but doesnt limit the columns to display in the same regard.
What good are those columns being displayed in the column list if they are hidden in the configuration?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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