• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      As a product owner, I want to be able to reorder the fixversions in the version column so that I can move to the top the ones that I want to work with.

      Currently, right now, every version appears for the projects that my filter is associated with. So, I have 15-20 versions appearing and have to scroll to locate the versions that I want to focus on.

            [JSWSERVER-10916] Reorder fixversions

            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.

            Nikhil Gupta added a comment - 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.

            karie.kelly@phytel.com, thanks for the additional detail.
            I'm going to close this as a duplicate of GHS-10420, your additional information and use-case will be available via that issue through an issue link. Please follow GHS-10420.

            Regards,
            Martin
            JIRA Agile team

            Martin (Inactive) added a comment - karie.kelly@phytel.com , thanks for the additional detail. I'm going to close this as a duplicate of GHS-10420 , your additional information and use-case will be available via that issue through an issue link. Please follow GHS-10420 . Regards, Martin JIRA Agile team

            @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.

            Karie Kelly added a comment - @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.

            karie.kelly@phytel.com, thanks for your response. Unfortunately while the panels look similar there are some differences. Versions have an existing ordering in JIRA, determined in project administration and they will show unless released.
            It is unlikely that JIRA Agile will add another level of customisation to this list ordering and it's likely that one of the stories around filtering the list would be done.

            Martin (Inactive) added a comment - karie.kelly@phytel.com , thanks for your response. Unfortunately while the panels look similar there are some differences. Versions have an existing ordering in JIRA, determined in project administration and they will show unless released. It is unlikely that JIRA Agile will add another level of customisation to this list ordering and it's likely that one of the stories around filtering the list would be done.

            For me, the root cause is that fixversions don't work like epics. Epics that appear are only those associated with your filter and you can reorder them so that you can place the ones you work with most often at the top. Fixversions is completely different. All fixversions associated with the projects that are associated with your filter appear, regardless of whether there are any issues associated with those fixversions. So, I end up with 15+ fixversions in a single board for a team that works issues across multiple projects. And, I cannot reorder them, to put the ones I work with (or are really only associated with the board) near the top.

            You wouldn't show all epics associated with the filter projects; why show all fixversions? Why not have the two panels work the same way?

            Karie Kelly added a comment - For me, the root cause is that fixversions don't work like epics. Epics that appear are only those associated with your filter and you can reorder them so that you can place the ones you work with most often at the top. Fixversions is completely different. All fixversions associated with the projects that are associated with your filter appear, regardless of whether there are any issues associated with those fixversions. So, I end up with 15+ fixversions in a single board for a team that works issues across multiple projects. And, I cannot reorder them, to put the ones I work with (or are really only associated with the board) near the top. You wouldn't show all epics associated with the filter projects; why show all fixversions? Why not have the two panels work the same way?

            The ordering for each version is controlled by the order in the JIRA project administration.
            These are then grouped by projects in the case of a multi-project board.

            It would seem this request would probably be best answered with some kind of filtering ability in the version panel.

            Martin (Inactive) added a comment - The ordering for each version is controlled by the order in the JIRA project administration. These are then grouped by projects in the case of a multi-project board. It would seem this request would probably be best answered with some kind of filtering ability in the version panel.

              Unassigned Unassigned
              4f4250feead3 Karie Kelly
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: