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

Ability to choose a username on public sign on instead using an e-mail address as username.

XMLWordPrintable

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

      Currently, using the public sign on feature in JIRA Service Desk it forces to use the username as your e-mail address. We'd like the ability to be able to choose an username instead of using an e-mail address as username.

      Thank you!

      victor.bucur@novartis.com

          Form Name

            [JSDSERVER-1197] Ability to choose a username on public sign on instead using an e-mail address as username.

            Charlie Marriott added a comment -
            Atlassian Update – 19 Feb 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 – 19 Feb 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

            Ignacio Pulgar added a comment -

            Please, vote for JSD-4551.

            It is a similar suggestion to this one, but reflects how now it has now much more impact on all Service Desk Cloud instances, now that Agents can always create new customer accounts disregarding the security settings on the SD project.

            In other words, the scope now affects all Service Desk projects on all Service Desk Cloud instances, as per the implementation on 04 Jul 2016 that grants all Agents with the ability of creating new customer accounts:

            https://confluence.atlassian.com/cloud/what-s-new-686863216.html#What'sNew-servicedesk

            Thanks!

            Ignacio Pulgar

            Ignacio Pulgar added a comment - Please, vote for  JSD-4551 . It is a similar suggestion to this one, but reflects how now it has now much more impact on all Service Desk Cloud instances, now that Agents can always create new customer accounts disregarding the security settings on the SD project. In other words, the scope now affects all Service Desk projects on all Service Desk Cloud instances, as per the implementation on 04 Jul 2016 that grants all Agents with the ability of creating new customer accounts: https://confluence.atlassian.com/cloud/what-s-new-686863216.html#What'sNew-servicedesk Thanks! Ignacio Pulgar

            Andre Coetzee added a comment -

            Agreed. I have had the experience where customers eventually become Jira users and cannot be added due to the email address that was already in use as a Service Desk Customer. My workarround was lengthy and involved deleting / recreating a project etc.

            Andre Coetzee added a comment - Agreed. I have had the experience where customers eventually become Jira users and cannot be added due to the email address that was already in use as a Service Desk Customer. My workarround was lengthy and involved deleting / recreating a project etc.

              Unassigned Unassigned
              lfagundes Luciano Fagundes (Inactive)
              Votes:
              6 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: