Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-11098

Add assignee avatars to work mode and allow per user filtering when clicking them

    • 2
    • 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.

      With this new version, we've avatars showing on planning board. It would be a great improvement to:

      • Show this avatars on working board and clicking on it, select only issues affected to this user
      • Also, it would web a great improvement to have a multiselect of issue status, to select all issues resolved, or any status defined on the workflow of the project

            [JSWSERVER-11098] Add assignee avatars to work mode and allow per user filtering when clicking them

            Atlassian Update – 10 October 2019

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here.

            To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans.

            Regards,
            Jira Server and Data Center Product Management

            Gosia Kowalska added a comment - Atlassian Update – 10 October 2019 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid and transparent communication and our attempts to become more transparent about our priorities. Making tradeoffs and saying no is never an easy task to perform. You can read more about our approach to highly voted server suggestions here . To learn more about our recent investments in Jira Server and Data Center, please check our two new dashboards containing Recently resolved issues and Current work and future plans . Regards, Jira Server and Data Center Product Management

            this would be an awesome and much needed improvement!

            Rutger Buijzen added a comment - this would be an awesome and much needed improvement!

            ryanewtaylor, GHS-5389 is for plan mode but the issues are very similar.
            Kind regards,
            Martin
            JIRA Agile

            Martin (Inactive) added a comment - ryanewtaylor , GHS-5389 is for plan mode but the issues are very similar. Kind regards, Martin JIRA Agile

            Our team could definitely use this capability as well. We were doing some pre-sprint planning and wanted to see only those issues that were assigned to a specific individual in plan mode and the work mode. We use this to help understand which issues are assigned to each individual without being overcome by the sheer number of issues in the system. For instance, our manager may want to see which issues are assigned to me so that she may quickly ask about and/or identify any roadblocks I may have with my issues.

            Currently, this is only achievable by making quick filters for each of our team members. But this is a sloppy solution as we have upwards of 12 members on our team. This is 12 additional quick filters on top of the existing ones. The quick filters quickly take up a large amount of the screen. In addition, our team composition changes regularly so we'd need to update our quick filters fairly often (as often as once a month).

            Being able to filter what issues are shown simply by clicking on the users avatars would seem to be an elegant solution to this problem.

            Also, is GHS-5389 a duplicate of this issue?

            ryanewtaylor added a comment - Our team could definitely use this capability as well. We were doing some pre-sprint planning and wanted to see only those issues that were assigned to a specific individual in plan mode and the work mode. We use this to help understand which issues are assigned to each individual without being overcome by the sheer number of issues in the system. For instance, our manager may want to see which issues are assigned to me so that she may quickly ask about and/or identify any roadblocks I may have with my issues. Currently, this is only achievable by making quick filters for each of our team members. But this is a sloppy solution as we have upwards of 12 members on our team. This is 12 additional quick filters on top of the existing ones. The quick filters quickly take up a large amount of the screen. In addition, our team composition changes regularly so we'd need to update our quick filters fairly often (as often as once a month). Being able to filter what issues are shown simply by clicking on the users avatars would seem to be an elegant solution to this problem. Also, is GHS-5389 a duplicate of this issue?

            You can see in screenshot attached the quick filters I used, there are a lot of. The problem is that you can't click on more than one, for example, you can't click on issues in progress and issues resolved.
            And you can't see the number of tasks per carril, like kanban dashboard.

            Marcial Atiénzar Navarro added a comment - You can see in screenshot attached the quick filters I used, there are a lot of. The problem is that you can't click on more than one, for example, you can't click on issues in progress and issues resolved. And you can't see the number of tasks per carril, like kanban dashboard.

            Martin (Inactive) added a comment - Could this second point be achieved with custom swimlanes or Quick Filters? https://confluence.atlassian.com/display/AGILE/Configuring+Swimlanes https://confluence.atlassian.com/display/AGILE/Configuring+Quick+Filters

            About the second point:

            • You ha've a big team and a sprint with lot of histories with lot of task
            • There are roles on the project to resolved issues, test issues resolved, validate issues tested and close issues validate
            • You've to scroll a lot of if you want to search issues tested, for example, to validate them

            And it would be a great improvement to have the number of isssues associate at every state, like kanban.

            Marcial Atiénzar Navarro added a comment - About the second point: You ha've a big team and a sprint with lot of histories with lot of task There are roles on the project to resolved issues, test issues resolved, validate issues tested and close issues validate You've to scroll a lot of if you want to search issues tested, for example, to validate them And it would be a great improvement to have the number of isssues associate at every state, like kanban.

            matienzar2 thanks for your suggestion, this is something we'd discussed as an addition and I'll use your issue as the placeholder for the feature.

            Regarding your second point, could you please clarify the need for this request? Additionally, It would be better to create a separate issue for that request.

            Regards,
            JIRA Agile team

            Martin (Inactive) added a comment - matienzar2 thanks for your suggestion, this is something we'd discussed as an addition and I'll use your issue as the placeholder for the feature. Regarding your second point, could you please clarify the need for this request? Additionally, It would be better to create a separate issue for that request. Regards, JIRA Agile team

              Unassigned Unassigned
              a534d383ac2f Marcial Atiénzar Navarro
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: