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