Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Product Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Sprint Burn Down Scope Change

SKAdmin
SKAdmin
Contributor
October 27, 2022

Is there a way to prevent logged spent time from being removed from the burndown chart when an issue is removed? 

 image.png

 

Answer
Watch
Like Be the first to like this
504 views

1 answer

0 votes
Patty Land
Patty Land
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Get recognized
October 27, 2022

If work has already been logged on an issue during a sprint, and you want to stop work and move the issue to another sprint but still credit the work logged in this one, you may want to split the issue, and adjust your estimate and scope for the work remaining. So, if I have a story with an original estimate of 8 hours and I've spent 2 hours in this sprint, I can split the story, put an original estimate of 6 hours on my new story and move that to another sprint, and then close my remaining 2 hour story in the current sprint.

View More Comments
SKAdmin
SKAdmin
Contributor
October 28, 2022

That is an interesting solution. Thank you.

Like
Reply

Suggest an answer

Log in or Sign up to answer
Jira
Jira
DEPLOYMENT TYPE
SERVER
TAGS
AUG Leaders

Atlassian Community Events

    See all events