-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
Severity 3 - Minor
-
NOTE: This bug report is for JIRA Portfolio Cloud. Using JIRA Portfolio Server? See the corresponding bug report.
It looks like the "text" of the issue link isn't updated when issues are moved between projects. If you import an issue and move it to a different project, the text of the issue link shows the old id (which no longer exists). The link still points to the issue correctly.
I'm not sure if this has any other consequences (i.e when pushing updates from Portfolio), but I haven't observed any as yet.
Steps to Reproduce
- Create an issue under one project
- Import into Portfolio
- Move issue to another project
- Workaround*
- Remove the Issue and re-import
Expected Behavior
- Issue link should be updated when loading the plan post issue move.
- is duplicated by
-
JSWCLOUD-20268 issue Key is not updated when issue changes project key
- Closed
- is related to
-
JPOSERVER-523 Issue Link not updated after move between projects.
- Closed
-
JSWCLOUD-19574 Issue links should work correctly when an issue has been moved to a new project in JIRA
- Closed