• 0
    • 2
    • 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.

      Scenario:

      • Activate account email is sent to mailing list
      • User clicks link to activate account and does not notice they are activating account for mailing list address.

      Suggested Change:

      I think a confirmation of what email address they want to use would make sense, so in this case, they would be asked, "is the email address <address> correct? If so, please check this box, if not, please enter your email address below". Then make it a mandatory field.

            [JSDSERVER-3966] Confirm email address on activate account page

            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

            Philip Colmer added a comment - luca.sokoll https://jira.atlassian.com/browse/JSD-4627  - freshly created  

            Is it possible to switch this to a bug report and increase the priority since it's been six months and no activity? We keep stumbling upon this behaviour due to SD's inability to handle CC'd groups. Ideally this should be a bug report.

            Is there an issue open regarding group handling? If so can this be linked to it?

            Thanks!

            Luca Sokoll added a comment - Is it possible to switch this to a bug report and increase the priority since it's been six months and no activity? We keep stumbling upon this behaviour due to SD's inability to handle CC'd groups. Ideally this should be a bug report. Is there an issue open regarding group handling? If so can this be linked to it? Thanks!

              Unassigned Unassigned
              tevans Tim Evans (Inactive)
              Votes:
              4 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: