-
Suggestion
-
Resolution: Duplicate
-
None
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.
- duplicates
-
JSWCLOUD-19089 Issue Link not updated after move between projects.
- Closed
- is duplicated by
-
JSWCLOUD-19574 Issue links should work correctly when an issue has been moved to a new project in JIRA
- Closed
- is related to
-
JPOSERVER-473 issue Key is not updated when issue changes project key
- Closed
- relates to
-
JSWCLOUD-20222 Keep Sprints in sync with JIRA Agile
- Closed