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

No access to Project-Administration pages Versions, Components and Roles

XMLWordPrintable

      When a JIRA project is created with an invalid project key the project administrator won't be able to access the versions, components and roles pages.

      Steps to reproduce :

      1. Create a project with key '1234' (all numeric)
      2. Try to go to Project administration -> Versions, Components and Roles
      3. The page does not display and shows a progress bar infinitely.

      Resolution :
      Change the project key to a valid format

        1. Screen Shot 2014-03-20 at 13.37.23.png
          Screen Shot 2014-03-20 at 13.37.23.png
          22 kB
        2. Screen Shot 2014-03-20 at 13.42.36.png
          Screen Shot 2014-03-20 at 13.42.36.png
          42 kB

            [JRASERVER-37570] No access to Project-Administration pages Versions, Components and Roles

            Todd Hlavacek added a comment -

            Actually, how can "all bets be off" if we migrated from, say, JIRA 4.3.4, which allowed numeric project keys, to 6.3.11, which disallowed numeric keys. CHanging keys to an alphanumeric key is not possible because Atlassian's Subversion plug-in does not factor in the project key changes in displaying code commits. Either we retain the numeric key and the subversion commit history or we rename the key to an alphanumeric key and lose all commit history.

            That being said, how can this be all bets off when at one time Atlassian allowed numeric project keys only to change face and make a requirement that keys be alphanumeric?

            Thanks,
            Todd

            Todd Hlavacek added a comment - Actually, how can "all bets be off" if we migrated from, say, JIRA 4.3.4, which allowed numeric project keys, to 6.3.11, which disallowed numeric keys. CHanging keys to an alphanumeric key is not possible because Atlassian's Subversion plug-in does not factor in the project key changes in displaying code commits. Either we retain the numeric key and the subversion commit history or we rename the key to an alphanumeric key and lose all commit history. That being said, how can this be all bets off when at one time Atlassian allowed numeric project keys only to change face and make a requirement that keys be alphanumeric? Thanks, Todd

            Oswaldo Hernandez (Inactive) added a comment -

            Hi rtandon@atlassian.com,

            When an invalid format is used all bets are off and it is hard to predict what the system behaviour should be when an unsupported key format is used. Therefore, this is not really a bug, but rather a configuration issue on the JIRA instance.

            Cheers,
            Os.

            Oswaldo Hernandez (Inactive) added a comment - Hi rtandon@atlassian.com , When an invalid format is used all bets are off and it is hard to predict what the system behaviour should be when an unsupported key format is used. Therefore, this is not really a bug, but rather a configuration issue on the JIRA instance. Cheers, Os.

              Unassigned Unassigned
              rtandon@atlassian.com Ruchi Tandon
              Affected customers:
              0 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: