I marked all tasks done. They are in Done (green) Status and Resolved with Resolved date. But when I complete the sprint they are incomplete.
How can I change them to complete?
Please see the screenshots.
The rightmost column of your board is discarded. As you did not share your workflow, I am not sure where discarded is in your workflow. I am not convinced that this should be a status (it might also be a resolution, similar to won't fix or won't do).
But anyway, to get back to the board ...
As none of your issues reached the end of your board, they are considered to be incomplete when you close your sprint. So make sure to make the Done column the rightmost column. Possibly, swapping the order of Discarded and Done on the board may do the trick.
I have the same situation hete. My last column is PACKAGING which is falling DONE status category only. But the difference is i have many other DONE statuses after PACKAGING..like STAGING,DEPLOYED,CLOSED all are falling under DONE status category.
During sprint completing some of my issues might have passed through last column PACKAGING and reached STAGING or further. In this case I'm getting message like there incomplete issues moved to backlog.
How do I solve this?
Yes..i have Done colums at far right..
PACKAGING ,STAGING , DEPLOYED and CLOSED statuses are in DONE category. Only PACKAGING is mapped into the last column of scrum board. Others are not mapped.
I have two board one is scrum and other is kanban
Scrum board columns will be like this:
TODO | DEVELOPMENT | TESTING | PACKAGING
Kanban board columns will be like this:
PACKAGING | STAGING | DEPLOYED | CLOSED
My developers will complete their sprint once all the issues reached in PACKAGING status.
Then the team responsible for releasing will be taking care rest of the process. They are following Kanban process.
So as and when they receive items in the PACKAGING column they start working irrespective of the sprint. They don't wait for the sprint to complete.
Is there any way around
No - column. Not columnS.
You say "Only PACKAGING is mapped into the last column of scrum board." - these will be the only issues considered done when the sprint is closed.
I think I see what you are doing here and why, although I'm not 100% sure. To make it do what I think you want, change the scrum board definition - the packaging column needs to contain packaging, staging, deployed and closed as well.
So you mean to say My last column should contain all statuses even though STAGING,DEPLOYED,CLOSED statuses are irrelevant to my dev team . In that case when they drop issues to DONE they have to choose PACKAGING. This seems to be okay..But I'm not convinced why one status is not enough to say it is DONE.
Let me try this tomorrow and get back to you.
Yes. That's right.
There is an additional thing you can do here though - if your developers and your release team are clearly separated somehow (like being in different roles), then you can add "conditions" to the transitions that go into staging, deployed and closed. If you use "must be in role 'release team'" on them, then your developers will not be able to select anything other than "packaging", which keeps the column cleaner for them
Thank You Nic. That is working..now when i say complete sprint all are issues are done. Thank you once again.
Even otherwise if it is other DONE statuses and when sprint completion says incomplete issues will be moved to backlog...but I couldn't find any such items in backlog. Is it just a message only?...
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
...+ reading Fantasy). The same is true for him at the bank he works for: Efficiency is key when time literally equals money. Read on to learn how Sergey makes most of the time he has by...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs