Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-473

issue Key is not updated when issue changes project key

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None

    • JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

    Description

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

      When moving an issue to another project, the Project Key is not updated in Portfolio to reflect the changes.

      The change has to be done manually.

      Attachments

        Issue Links

          duplicates

          Bug - A problem which impairs or prevents the functions of the product. JPOSERVER-523 Issue Link not updated after move between projects.

          • Low - Low priority issues
          • Closed
          is duplicated by

          Suggestion - JPOSERVER-496 Issue links should work correctly when an issue has been moved to a new project in JIRA

          • Closed
          relates to

          Suggestion - JPOSERVER-10 Keep Sprints in sync with JIRA Agile

          • Closed

          Suggestion - JSWCLOUD-20268 issue Key is not updated when issue changes project key

          • Closed

          Activity

            People

              Unassigned Unassigned
              mfernandezbadii Mauro Badii
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

              Dates

                Created:
                Updated:
                Resolved:
                Archived: