@Martin - thank you for the response; however, the reason for this request is because of these differences. From a usability standpoint, when panels all look the same, it should intuitive as to how they work. As mentioned, we are trying to solve the problem, not only of usability, but of data that is appearing that is not applicable to the team's boards. One project can have many, many versions (we have one with over 25 active versions because it is an implementation project and a fixversion is a specific customer implementation). We have two teams who also work issues and provide support across several projects; they end up with 30-50 versions in that panel and it is no longer usable. However, the fixversions actually applicable to their team is only about 4-5 because they are defined based on labels.
This current solution is not conducive to teams that work across projects or when using JIRA outside of just product development (e.g. for implementation projects, marketing projects, etc.) – the latter is something that Atlassian promotes and should be a good thing as it expands the 'market' of the product; thus, Agile product owners need to not just be focused on scrum product development and only how they have implemented it. To attract the broader use, the product needs to be flexible and intuitive.
We have 500+ versions and I want to see only relevant version to my filter. I am not exactly looking for reordering the fixversions. As simple as filtering the version from left panel (e.g. fixVersion="V2*) will be very helpful. Thanks.