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

Create users that do not exist from the CC list of e-mails

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

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

      Currently JIRA can create a new user based on the From: field of an email, but not the CC: field.

      This is related to JRA-9983 which extends the ability to add CC: recipients on an email as watchers on an issue. This has been implemented and is scheduled for a JIRA 4.0 release, however if any of the CC: recipients are not currently users of JIRA then that recipient is silently discarded from the watcher list.

      It would be useful in some circumstances that when an issue is being commented on via email, an existing user could then add a CC recipient to the email and then the JIRA handler, provided configured, could then create and then add this user via JRA-9983, so that this new user would be able to comment and follow the progress of that issue.

      However this introduces a problem of what permissions to give the new user..

            [JRASERVER-14329] Create users that do not exist from the CC list of e-mails

            So this is closed as "Won't Fix", but this is the exact feature I would like to see implemented. As for permissions to give the new user, I'd suggest making the behavior align with incoming mail queues, which means the functionality would be restricted to only mail queues that allow new user creation – but that makes perfect sense to me.

            Right now when an email is sent to our JIRA support handler address with CCs, they're silently discarded and to anyone else on the thread (other than the sender) it appears no further communication happened. This can lead to duplicate work when dealing with cross-team projects that don't all use JIRA.

            Tony Malkowski added a comment - So this is closed as "Won't Fix", but this is the exact feature I would like to see implemented. As for permissions to give the new user, I'd suggest making the behavior align with incoming mail queues, which means the functionality would be restricted to only mail queues that allow new user creation – but that makes perfect sense to me. Right now when an email is sent to our JIRA support handler address with CCs, they're silently discarded and to anyone else on the thread (other than the sender) it appears no further communication happened. This can lead to duplicate work when dealing with cross-team projects that don't all use JIRA.

            Hi,

            This is a bulk update to specific issues in the JIRA (JRA) project

            As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today.

            Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com

            If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close.

            Best regards
            Josh Devenny and Roy Krishna
            JIRA Product Management

            Josh Devenny added a comment - Hi, This is a bulk update to specific issues in the JIRA (JRA) project As part of an effort to ensure we are transparent about the JIRA issues on jira.atlassian.com, we have decided to resolve those that have been open for multiple years with minimal activity and with a low number of votes. In light of the fact that JIRA is rapidly changing and that this issue may not be a valid request any longer, we will be resolving it today. Votes are not the only metric that we use to determine the requests that are implemented, however they do factor in to our decision making process. We have decided that the combination of this issue being open for a long period of time, and it's low number of votes means that we are unlikely to implement it. If you would like thoughts on how we use jira.atlassian.com, please see: https://answers.atlassian.com/questions/110373/how-does-the-jira-team-use-jira-atlassian-com If you have believe this issue is still relevant, please comment on the issue and we will respond. We are watching all these issues that we bulk close. Best regards Josh Devenny and Roy Krishna JIRA Product Management

              Unassigned Unassigned
              pwhite Peter White [Atlassian]
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: