• Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • AgileBoard
    • None
    • 1
    • 1
    • 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.

      User Story

      As a scrum team member, I want to be able to add more than one avatar icon to one card, to indicate that more people are working on this card.

      The request for having more than one assignee has been made a couple of years ago (see links). All of them got rejected, due to the policy, that Jira sicks with 1 assignee.

      My request is not to break this, but to add a functionality to the agile board only, that for example, the username behind an avatar is part of a user picker (multi users) custom field. The assignee can stay as it is (first drag&drop of avatar will fill assignee, next goes into custom field).

      During the past years, working as an agile coach, I have seen many times that teams, working with a physical agile board, mark issues with multiple avatars (magnetic white-board, post-its and individual magnetic avatars).

      It absolutely make sense, because the whole agile movement is all about "individuals and their interaction". Reviews, knowledge transfer and pair programming (XP) are best examples for marking an issue with more than one worker. Not only the solo work on one issue.

      Implementing this feature will make Jira Software come very close to the physical boards.

            [JSWSERVER-16411] More than one avatar on an agile card

            This would be a great feature. It helps to see the Q&A people assigned to test a specific task.
            Also, for new developers in the team, we share tasks with senior developers to make sure people get on board quickly, these issues are always shared and there is no way to track it. Trello does this perfectly, would love to get same feature in Jira. 

            João Cordeiro added a comment - This would be a great feature. It helps to see the Q&A people assigned to test a specific task. Also, for new developers in the team, we share tasks with senior developers to make sure people get on board quickly, these issues are always shared and there is no way to track it. Trello does this perfectly, would love to get same feature in Jira. 

            As a QA this would be very nice to track who is developing the task and who is testing.

            Renan Ussami added a comment - As a QA this would be very nice to track who is developing the task and who is testing.

            RKR84 added a comment -

            No way to map pair programming reasonably is really a big deficit of jira.

            RKR84 added a comment - No way to map pair programming reasonably is really a big deficit of jira.

            This would be great, otherwise we would have to use other software to help see whos pairing with who at any time.

            Chris Wade added a comment - This would be great, otherwise we would have to use other software to help see whos pairing with who at any time.

            Yes please - we use pair programming and were used to this feature on our previous software. It is central to an Agile standup to see easily who is involved in what work that morning. Please raise the profile of this feature request. Thank you! 

            Anthony Leonard added a comment - Yes please - we use pair programming and were used to this feature on our previous software. It is central to an Agile standup to see easily who is involved in what work that morning. Please raise the profile of this feature request. Thank you! 

            Jim Miles added a comment -

            Seeing as Jira is a leading Agile SDLC tool, it makes sense to visually display all team members who collaborate on an effort. One task per person is not how Agile teams work. I just migrated a team from Trello (which allows multiple avatars per card) to Jira Cloud and it is a major sticky point. Many thanks in considering this!

            Jim Miles added a comment - Seeing as Jira is a leading Agile SDLC tool, it makes sense to visually display all team members who collaborate on an effort. One task per person is not how Agile teams work. I just migrated a team from Trello (which allows multiple avatars per card) to Jira Cloud and it is a major sticky point. Many thanks in considering this!

            This is quite literally the feature lack that I have to work around the most in Jira.  I have a whole class of problems that would be solved by just being able to have "stickers" for each of my team by a thing that people are working on, that I could put on cards.  The power of being able to visually see this is one of the main things a physical board provides that Jira has no way to replicate.

            Currently I mostly solve this by either using other tools (e.g., github projects) or creating a manual board (which, while forcibly remote, doesn't work well so I end up kludging it together in a Google Slide or Doc).

            Derek Groothuis added a comment - This is quite literally the feature lack that I have to work around the most in Jira.  I have a whole class of problems that would be solved by just being able to have "stickers" for each of my team by a thing that people are working on, that I could put on cards.  The power of being able to visually see this is one of the main things a physical board provides that Jira has no way to replicate. Currently I mostly solve this by either using other tools (e.g., github projects) or creating a manual board (which, while forcibly remote, doesn't work well so I end up kludging it together in a Google Slide or Doc).

            For our purposes, we have a custom field that we would also like to appear within the Backlog cards. 

            We use a custom field for "Project Lead", as we have multiple Developers working on all types of requests around the world.  Not ALL personnel are able to join our stand-up and we rely on the project lead to fill in gaps or define roadblocks that arise.  From the backlog view, it would be nice to see both Avatars on each card representing the Assignee and Project Lead.  This is NOT to delegate the same task to multiple people... instead, it would be used to help easily identify who Team Members would report back to OR be used by Management personnel by communicating through the appropriate channels (where possible).

            I've included a screenshot as an example...

            Again, this is not in an effort to highlight multiple people working on the same tasking.  We are keeping this agile, with 1:1 ratio (1 ticket, 1 user) but adding functionality to show project user hierarchy easily from the Backlog view.

             


             

            As for our current solution, we've added the Project Lead custom field to the card.  However, it's not showing as an Avatar but instead the single user's entire name.  This definitely clutters up the backlog view and has caused some confusion in the past.  It also forces the card to have 2 line levels (expanded) instead of the 1 line.  See screenshot below as a reference...

             


             

            Is there anything we can do to help solidify this request?  It would be nice to specify more data on the 1 line and by using Avatars (for User entries) where applicable.  It would be nice to specify on the cards if we want to see this entry in Avatar vs Full form as well.  

            Todd Whymark added a comment - For our purposes, we have a custom field that we would also like to appear within the Backlog cards.  We use a custom field for "Project Lead", as we have multiple Developers working on all types of requests around the world.  Not ALL personnel are able to join our stand-up and we rely on the project lead to fill in gaps or define roadblocks that arise.  From the backlog view, it would be nice to see both Avatars on each card representing the Assignee and Project Lead.  This is NOT to delegate the same task to multiple people... instead, it would be used to help easily identify who Team Members would report back to OR be used by Management personnel by communicating through the appropriate channels (where possible). I've included a screenshot as an example... Again, this is not in an effort to highlight multiple people working on the same tasking.  We are keeping this agile, with 1:1 ratio (1 ticket, 1 user) but adding functionality to show project user hierarchy easily from the Backlog view.     As for our current solution, we've added the Project Lead custom field to the card.  However, it's not showing as an Avatar but instead the single user's entire name.  This definitely clutters up the backlog view and has caused some confusion in the past.  It also forces the card to have 2 line levels (expanded) instead of the 1 line.  See screenshot below as a reference...     Is there anything we can do to help solidify this request?  It would be nice to specify more data on the 1 line and by using Avatars (for User entries) where applicable.  It would be nice to specify on the cards if we want to see this entry in Avatar vs Full form as well.  

            We'd like to put one or more stakeholder avatars on a card in board view.  Names take up too much board real estate.

            Attila Madarasz added a comment - We'd like to put one or more stakeholder avatars on a card in board view.  Names take up too much board real estate.

            Evan added a comment -

            In our workflow we have a QA verifier. It'd be nice if the verifier could have their avatar on the ticket as well, rather than a full name, which makes the board overly crowded.

            Evan added a comment - In our workflow we have a QA verifier. It'd be nice if the verifier could have their avatar on the ticket as well, rather than a full name, which makes the board overly crowded.

              Unassigned Unassigned
              8b31319ab581 Thomas Deiler
              Votes:
              49 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated: