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

Username with uppercase letter unable to create Service Desk

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 1.1.6
    • 1.1.1, 1.1.4
    • None

      Summary

      Username with uppercase letter unable to create Service Desk

      Steps to reproduce

      • Create admin user with uppercase letters in username (ex. "TestUser")
      • Login in as TestUser
      • Create Service Desk

      Expected Results

      • Service Desk created, screen is redirected to the newly created Service Desk. The default configurations for queues, SLA, metrics are there.

      Actual Results

      • Unable to get past first dialog page
      • If you check your projects, the new project was created, but there are no configurations added (queues,SLAs,metrics,etc).

      Workaround

      • Rename the user to have all lowercase letters. (from example: "TestUser" to "testuser")

            [JSDSERVER-209] Username with uppercase letter unable to create Service Desk

            Jim Cork added a comment -

            JIRA version - JIRA v6.2.3
            Service Desk version - JIRA Service Desk v1.2.5
            Auth is LDAP
            OS is CentOS 6.4

            I think my bug is different. The problem is not related to raising tickets, it's to do with the way the notifications come through to members of the service desk project.

            All of our usernames are lowercase, following the firstname.lastname format.

            Notifications from some people come through as 'Anonymous (JIRA)' and for others, the come through fine as Firstname Lastname (JIRA).

            It seems to be totally random, as all the users seem identical in terms of their group memberships and setup.

            Jim Cork added a comment - JIRA version - JIRA v6.2.3 Service Desk version - JIRA Service Desk v1.2.5 Auth is LDAP OS is CentOS 6.4 I think my bug is different. The problem is not related to raising tickets, it's to do with the way the notifications come through to members of the service desk project. All of our usernames are lowercase, following the firstname.lastname format. Notifications from some people come through as 'Anonymous (JIRA)' and for others, the come through fine as Firstname Lastname (JIRA). It seems to be totally random, as all the users seem identical in terms of their group memberships and setup.

            Ed Zhang (Automation) added a comment -

            Could everyone commenting on this issue please provide the following information:

            • JIRA version
            • JIRA Service Desk Version
            • If you have any external authentication configured (such as crowd)
            • OS your JIRA server is running on

            Ed Zhang (Automation) added a comment - Could everyone commenting on this issue please provide the following information: JIRA version JIRA Service Desk Version If you have any external authentication configured (such as crowd) OS your JIRA server is running on

            Jim Cork added a comment -

            This appears to not only be related to uppercase users or users with special characters.

            I am an admin for our SD project, some Issues see email notifications come through from "Anonymous (JIRA)", even though the reporter field is set correctly in the Issue itself.

            Jim Cork added a comment - This appears to not only be related to uppercase users or users with special characters. I am an admin for our SD project, some Issues see email notifications come through from "Anonymous (JIRA)", even though the reporter field is set correctly in the Issue itself.

            RomainD added a comment -

            Hi,

            I'm using Service Desk 1.1.6 and there is still an issue when login is in uppercase.

            Cheers,

            RomainD added a comment - Hi, I'm using Service Desk 1.1.6 and there is still an issue when login is in uppercase. Cheers,

              ezhang Ed Zhang (Automation)
              pkirkeby Pelle Kirkeby (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: