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

      By design JIRA can only have 1 assignee at a time to a given issue.

      To help address this issue we have posted several workarounds based upon the comments to this issue - please read this page for more information: Setting Up Multiple & Group Assignees In JIRA

            [JRASERVER-1397] Assign issues to multiple users or a group

            It is annoying that this is not added as an option, pair programming gets hard to represent this way.

            Johan Mollevik added a comment - It is annoying that this is not added as an option, pair programming gets hard to represent this way.

            Hi,

            We just released a new plugin "Groupee Group Assignee" to make groups assignable. Please give it a try and if you need more feature, let us know.

            Regards,

            Omer

             

            White Software added a comment - Hi, We just released a new plugin " Groupee Group Assignee " to make groups assignable. Please give it a try and if you need more feature, let us know. Regards, Omer  

            In our case the permissions on the projects tasks allow every assignee to see only his own tasks. How can i use the workarounds in this case? 

            John Patounas added a comment - In our case the permissions on the projects tasks allow every assignee to see only his own tasks. How can i use the workarounds in this case? 

            Eric Mertens - never. Atlassian are never going to do this. See status and resolution.
            For pair programming, you'll have to use custom fields.

            Nic Brough -Adaptavist- added a comment - Eric Mertens - never. Atlassian are never going to do this. See status and resolution. For pair programming, you'll have to use custom fields.

            +1 when is the feature going to be ready ...... or more in general: Pair Programming made possible in JIRA ??

             

            Eric Mertens added a comment - +1 when is the feature going to be ready ...... or more in general: Pair Programming made possible in JIRA ??  

            I have to agree with Dan Copeland. If JIRA is going to be used by a pairing team, it needs to support more than one assignee.

            None of the suggested workarounds are tenable for a development team doing pairing. They're either combinatorially ridiculous (setting up a group or account for each possible pair on a team gets out of hand quickly), too non-specific (story owned by whole team or in a queue makes it difficult to track individual progress or responsibilities) or too specific ("Okay, you're the driver while we pair, so create a subtask for that and assign it to yourself. Oh, wait, let's switch"?)

            Glen Aultman-Bettridge added a comment - I have to agree with Dan Copeland. If JIRA is going to be used by a pairing team, it needs to support more than one assignee. None of the suggested workarounds are tenable for a development team doing pairing. They're either combinatorially ridiculous (setting up a group or account for each possible pair on a team gets out of hand quickly), too non-specific (story owned by whole team or in a queue makes it difficult to track individual progress or responsibilities) or too specific ("Okay, you're the driver while we pair, so create a subtask for that and assign it to yourself. Oh, wait, let's switch"?)

            Got this answer from an Atlassian partner https://www.isostech.com/solutions/
            and then later from Atlassian

            Objective:
            Want to set who does the works for each step on an issue

             

            Summary:
            Use a plugin to copy values from custom fields into the assignee field whenever the issue transitions to a new step.

            How:
            1. Install the Suite Utilities plug-in
            This plug-in adds a bunch of new functionalities to workflows.

            You will use the plug-in to copy the value of a custom field to the assignee.

            2. Create a custom field as single user picker for each role i.e., dev, tester, reviewer to be assigned at different steps in the issue

            3. Add these fields to the issue type's screen

            4. Modify the post-function on the workflow transition between each step
            Add a "Copy Value From Other Field" post function and set it to copy the value from the appropriate user custom field into the assignee field.

             

            Suzanne Capener added a comment - Got this answer from an Atlassian partner https://www.isostech.com/solutions/ and then later from Atlassian Objective: Want to set who does the works for each step on an issue   Summary: Use a plugin to copy values from custom fields into the assignee field whenever the issue transitions to a new step. How: 1. Install the Suite Utilities plug-in This plug-in adds a bunch of new functionalities to workflows. You will use the plug-in to copy the value of a custom field to the assignee. 2. Create a custom field as single user picker for each role i.e., dev, tester, reviewer to be assigned at different steps in the issue 3. Add these fields to the issue type's screen 4. Modify the post-function on the workflow transition between each step Add a "Copy Value From Other Field" post function and set it to copy the value from the appropriate user custom field into the assignee field.  

            I still see no good solution for a team doing pair programming with weekly pair rotation. I consider this a major problem for JIRA adoption for my team.

            I want an issue to be owned by two individuals, not a group. It's important to know that two developers are working / worked together on an issue, and it's not really acceptable to make one of them the "real" owner.

            I'm confused by the fact that you publicly support pairing and yet JIRA does not support multiple owners.

            Dan Copeland added a comment - I still see no good solution for a team doing pair programming with weekly pair rotation. I consider this a major problem for JIRA adoption for my team. I want an issue to be owned by two individuals, not a group. It's important to know that two developers are working / worked together on an issue, and it's not really acceptable to make one of them the "real" owner. I'm confused by the fact that you publicly support pairing and yet JIRA does not support multiple owners.

            The way we handle this is that we use the Tempo Team Custom Field to assign the issue to a team and then we can create filters and subscriptions to issues matching the team field and other criteria (e.g, needs triage).

            Cheers,
            Vidar (Tempo)

            Viðar Svansson [Tempo] added a comment - The way we handle this is that we use the Tempo Team Custom Field to assign the issue to a team and then we can create filters and subscriptions to issues matching the team field and other criteria (e.g, needs triage). Cheers, Vidar (Tempo)

            the way we handle this is to create a user with a dummy email address. Then create a subscription along the lines of "hey, we have some unassigned issues, please go take a look" that goes to the JIRA group. No double emails and ensures proper behavior by making sure things get actually assigned to a human.

            Kyle Guichard added a comment - the way we handle this is to create a user with a dummy email address. Then create a subscription along the lines of "hey, we have some unassigned issues, please go take a look" that goes to the JIRA group. No double emails and ensures proper behavior by making sure things get actually assigned to a human.

              Unassigned Unassigned
              a42693d97279 Ben Christensen
              Votes:
              413 Vote for this issue
              Watchers:
              255 Start watching this issue

                Created:
                Updated:
                Resolved: