Uploaded image for project: 'Jira Software Cloud'
  1. Jira Software Cloud
  2. JSWCLOUD-20268

issue Key is not updated when issue changes project key

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? 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. JSWCLOUD-19089 Issue Link not updated after move between projects.

          • Low - Low priority issues
          • Closed
          is duplicated by

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

          • Closed
          is related to

          Suggestion - JPOSERVER-473 issue Key is not updated when issue changes project key

          • Closed
          relates to

          Suggestion - JSWCLOUD-20222 Keep Sprints in sync with JIRA Agile

          • Closed

          Activity

            People

              Unassigned Unassigned
              mfernandezbadii Mauro Badii
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: