NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.
Steps to reproduce
- Create a board with 2 sprints and 1 story
- Move the story into the first sprint. Start the sprint.
- Close the sprint. The story should now be in the backlog
- Create a Portfolio plan based on the board
- Assign the issue to the board team. Commit.
- Assign the issue to the second sprint.
- We see "1 Uncommitted change" at the top. Click the button
Expected:
- We see the issue's sprint assignment in the commit dialog
Actual:
- No changes are shown
Workaround
There are 2 workarounds:
1. Change the issues team to calculate, then change it back to the proper team. Then assign the sprint. Then commit the issue.
2. Assign the issue to a sprint manually inside JIRA. The commit dialog should then show the uncommitted change of the issue's sprint.
- is related to
-
JPOSERVER-1527 Uncommitted changes indicator shows changes, but none are visible in commit dialog
-
- Closed
-
- relates to
-
-
- Closed
-
[JPOSERVER-1568] Sprint assignments don't show up in the commit dialog for issues that are assigned to closed sprints
We have identified the cause of the bug and it will be fixed in our next release.
Thanks,
Shafqat Bhuiyan
Portfolio for JIRA | Development
Shawn Moore
added a comment - I just tried to manually assign to a sprint and the issues are still orphaned. Both work-arounds do not work.
Shawn Moore
added a comment - I just tried to manually assign to a sprint and the issues are still orphaned. Both work-arounds do not work. Shawn Moore
added a comment - The work around does not seem to work and what is best way to manually assign? Is there a way in portfolio to sort by sprint? Otherwise it is hard to go through timeline and find each issue.
Shawn Moore
added a comment - The work around does not seem to work and what is best way to manually assign? Is there a way in portfolio to sort by sprint? Otherwise it is hard to go through timeline and find each issue. Shawn Moore
added a comment - Can we get this escalated to a major issue? This is causing a major pain for people getting started with portfolio.
Shawn Moore
added a comment - Can we get this escalated to a major issue? This is causing a major pain for people getting started with portfolio.
Hi shawn245682741,
With the first workaround, even though you change both the team and the sprint of an issue, only the team change shows up in the commit dialog. However, on commit both the team and the sprint get set.
With the second workaround, did you manually assign the sprint using JIRA or Portfolio? If you assigned the sprint using JIRA/Agile the change in the issue's sprint should show up in the commit dialog.
Let us know if these workarounds still do not work for you.
Thanks,
Shafqat