Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-61588

Multiple assignees in a single issue

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 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.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      In Portfolio, it's possible to assign an issue with multiple members. However, this feature isn't available in JIRA hence it would be great to have this in JIRA as well.

            [JRASERVER-61588] Multiple assignees in a single issue

            Wes Novack added a comment -

            I'd also like to see this implemented, where you can assign multiple, specific people to an issue.

            Many orgs do collaborative programming, pairing, and similar, where a pair (or more) of folks work on a particular issue.

            I'd like to be able to reflect that on Jira issues.

            Example; if Sally Smith, and John Jameson are working on an issue, I'd like to see both of their names show in the Assignee field on an issue.

            Will these types of things ever be considered after they're CLOSED? Should we open a new one?

            Wes Novack added a comment - I'd also like to see this implemented, where you can assign multiple, specific people to an issue. Many orgs do collaborative programming, pairing, and similar, where a pair (or more) of folks work on a particular issue. I'd like to be able to reflect that on Jira issues. Example; if Sally Smith, and John Jameson are working on an issue, I'd like to see both of their names show in the Assignee field on an issue. Will these types of things ever be considered after they're CLOSED? Should we open a new one?

            Gosia Kowalska added a comment -
            Atlassian Update – 30 March 2018

            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 now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 30 March 2018 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 now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              5a593132c726 Abhishek Kaushik
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: