My situation:
Problem:
Question:
Things I've tried:
Thank you!
Hello @Laura Xu
Welcome to the community.
Can you show us the Columns page under Board Settings?
When you complete a sprint, only the issues in the column farthest to the right on your board will be considered "complete". Are the Done and Abandoned statuses mapped to the right-most column of your board?
Additionally, an issue must not have any sub-tasks that are in the other columns (not "done" sub-tasks). Do the issues have incomplete sub-tasks?
When you complete a sprint, only the issues in the column farthest to the right on your board will be considered "complete".
^this is really useful to know! Can this be added to a visual tool guide somewhere?
I am aware about this one:
Additionally, an issue must not have any sub-tasks that are in the other columns (not "done" sub-tasks).
Here's how the columns are set up for our board. All subtasks under `done` are also marked as `done` when we experience the issue that the tasks does not get hidden after a sprint is "completed".
We are starting a new sprint next Monday, so this can be an opportunity for us to try something and see if it works after we "complete" the sprint on Monday. Do you have any suggestions for us on how to configure our board to achieve the desired behavior per above?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Laura Xu
I can't address your request about updating the documentation, as I am just another user of Jira. That is a suggestion you would need to submit to the Atlassian team. There should be a Feedback option under the Help button in your Jira instance.
Regarding changes to your board columns, you will need to have the Abandoned and Done statuses both mapped to the column farthest to the right. As you currently have it configured, the Abandoned issues would not be considered complete because that status is not in the right-most column.
If you still find that items in that right-most column are being moved to another sprint or the backlog when you complete the sprint then we would need to examine some of those items more closely to see if there is another reason for that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ah my bad. I had thought you worked for Jira and can report the unclarity somehow internally. First time posting.
Let me try your suggestion today during my sprint planning and see how it goes. If I still run into issues, I'll share it here and see if we can take alternative steps. Thank you so much for your help thus far!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.