Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-4124

Add ability to create user account for the user in CC field when email is sent by an authorised user

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • None
    • None
    • 0
    • 1
    • We collect Jira Service Desk 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 Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Problem Definition

      When the public signup is disabled and an authorised user sends an email to create issue and at the same time CC a non-existing email address. The ticket will be created but the email address in CC field is ignored without any notification.
      Currently JIRA can only create user account for new email address in CC field when public signup is enabled. However some customers do not want to expose the service desk project to every user (when public signup is enabled every user can have access to this project).

      Suggested Solution

      Add an option in JIRA so that when the public signup is disabled and an authorised user sends an email to create a ticket while CC a non-existing email address, a new user account should be created or a notification should be sent out to notify the sender.
      The feature request JSD-988 has been raised to notify the sender in this situation.

            [JSDSERVER-4124] Add ability to create user account for the user in CC field when email is sent by an authorised user

            Charlie Marriott added a comment -
            Atlassian Update – 1 March 2021

            Hi,

            Thank you for raising and watching 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 engagement with this suggestion (number of votes, number of watchers).

            We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here, and how we prioritise what to implement here.

            To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues, and current work and future plans.

            Regards,

            Jira Service Management, Server & Data Center

            Charlie Marriott added a comment - Atlassian Update – 1 March 2021 Hi, Thank you for raising and watching 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 engagement with this suggestion (number of votes, number of watchers). We hope you will appreciate our candid communication and our attempts to become more transparent about our priorities. You can read more about our approach to highly voted suggestions here , and how we prioritise what to implement here . To learn more about our recent investments in Jira Service Management and Data Center, please check our public roadmap and our two dashboards containing recently resolved issues , and current work and future plans . Regards, Jira Service Management, Server & Data Center

              Unassigned Unassigned
              cmao Chen Mao (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: