You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
I have created own workflow but hours are counted incorrectly due to workflow items type.
Below I attach screen from my board view, my workflow schema and my board columns.
In my board view:
Any idea how to set these three sums correctly?
Thanks.
Welcome to the Atlassian Community!
There is a bit of a disconnect or misunderstanding here, and you're not alone with it.
The number in green is only supposed to be the sum of the estimates for Scrum items that are "done". This does not mean items in a green Jira status-category, it is only items in the last column of the board, as defined in Scrum.
In other words this is correct - Uzavřeno is your last column, which is the only column that means "done" (i.e. the team this board represents do not need to do anything more with the issues in here).
Hi @Nic Brough -Adaptavist- , thanks for reply. I thought sum in the blue is for all blue statuses in our scrum workflow, grey for greys, green for greens.
If not, why there are in Workflow these colors (eg. green) for more statuses, when as "Done" is taken the last one, independed the real status?
And is there any workaround how to switch these sums into what I need - sums greys into grey one, blues into blue one, greens into green one?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This is something I think Jira is not good at. I understand it, it's historical and trying to handle different ways of working, but it makes it bad for a lot of us.
Jira looks at two things for "done".
When you are doing Scrum, "done" is the last column on your board. Every other part of Jira looks to the resolution field for "done" - empty = not done, anything in resolution = done.
The status category is really helpful, but it does not define done. You (and a lot of the rest of us) need to look at our boards and processes in a lot more detail, to define where done really means done. And then replicate that into our issue trackers.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.