Warn users during the upgrade that project keys with numbers are no longer allowed

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Won't Do
    • None
    • Component/s: None
    • None
    • 2

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Currently if you upgrade JIRA from 4.x releases to the latest, all of your projects are properly imported, including those that contain numbers in the Issue Key. In the latest JIRA releases, projects with numbers in the key are no longer allowed to be created, and this can cause problems like:

      1. Commits in the SVN will fail with the error:
        commit -m "[SS10-1] Changes to Improve Code Quality for Wiki Documentation - making it so you don't have to hard code the XML list" C:/src/trunk/sdx-mv90-adapter/sdx-mv90-adapter-war/src/test/java/com/landisgyr/sdx/mv90/SmokeTestWithMocksXmlCopyJUnit4Runner.java
        Sending C:/src/trunk/sdx-mv90-adapter/sdx-mv90-adapter-war/src/test/java/com/landisgyr/sdx/mv90/SmokeTestWithMocksXmlCopyJUnit4Runner.java
        Transmitting file data ...
        A repository hook failed
        svn: Commit failed (details follow):
        svn: Commit blocked by pre-commit hook (exit code 1) with output:
        Committer: bherschberger
        Commit message: "[SS10-1] Changes to Improve Code Quality for Wiki Documentation - making it so you don't have to hard code the XML list"
        Commit rejected: No project accepts this commit. Project [SDXADMIN]: Commit message must contain at least one valid issue key. Project [SQ]: Commit message must contain at least one valid issue key. Project [SA]: Commit message must contain at least one valid issue key. Project [SC]: Commit message must contain at least one valid issue key. Project [SS]: Commit message must contain at least one valid issue key. Project [SK]: Commit message must contain at least one valid issue key. Project [SS10]: Commit message must contain at least one valid issue key. Project [SD]: Commit message must contain at least one valid issue key. Project [SX]: Commit message must contain at least one valid issue key.
        
      2. Quick Search for the issue key won't work

      Please create an advisory/project key renaming possibility to warn users during the upgrade that problems will occur if the project key continues to use numbers.

      Workaround

      1. Create a new project with a clean project key (only uppercase letters);
      2. In the issue navigator, search for all the issues of the SDXMV90 project;
      3. In the "Tools" icon on the right corner of the screen, choose the option "all (xx) issue(s)";
        Where 'xx' is the number of issues returned in the search;
      4. Choose the "Move Issues" option;
      5. Select the project you created in the first step to move the issues to;
      6. Finish the bulk operation;

            Assignee:
            Unassigned
            Reporter:
            Pietro Schaff (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: