Not Including Hour Estimates for Tasks that are Closed at Beginning of Sprint

We currently have one Artezio board for each member of our team. Our team has a tendency to roll over stories from one sprint to the next. When this happens, some of the sub-tasks that are already completed are included in the sprint along with sub-task s to be completed. 

Is there any way to not include the hour estimates for sub-tasks that are already done at the beginning of the sprint? Having them included leads to a large spike at the beginning of the graph, and for some reason the tasks are not included in the Data tab so it's very confusing to someone not familiar with the plug-in. 

1 answer


1) It is possible that you have remaining estimate for completed sub-tasks. Would you please
confirm it?
2) You may try to avoid this problem by creating chart with new filter which includes sub-tasks
related to new sprint only (example: with labels or fix version).
3) Would you please send us more information (screens, detailed description) highlighting the problem at ""? It will help us with investigation.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Nov 29, 2018 in Marketplace Apps

How to set up an incident workflow from the VP of Engineering at Sentry

Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...

1,711 views 3 11
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you