It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Changing parent issue ->loosing userstory in sprintreports

We had a successful sprint. All reports were fine. Yesterday we just did our backlog grooming and changed for one story the parent issue (epic). (We didn't change anything else, like status or resolving date...)

Now the story points from this story are not counted for the velocity anymore! Additionally the BurnUp report is senseless.

Do you know about this bug? Is the only workaround: Dont touch done stories in closed sprints?

I think in reality the usecase to recognize that you create a new epic after working on the first story, because the topic is getting bigger is not so theoretically.. 

 

Did i something wrong?

Any ideas?

Greetings from Berlin

Uli

 

Velocitiy_Bericht.PNGBurnUp_Sprint4.PNGFehlende_Userstory.gif

1 answer

1 accepted

0 votes
Answer accepted

The problem is only in sprint 4, sprint 5 is still running...

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

260 views 1 2
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you