Solve for cloned issue retaining sprint when creating scope reports?

I'm querying directly into the DB using the CHANGEGROUP and CHANGEITEM tables to create reporting on scope changes w/in sprints--i.e. stories added, removed, completed durring a sprint.

The major problem I'm having is solving for cloned issues that are retaining the parents sprint value.

This makes it look as though a story was removed from the parent sprint when technically a story within the sprint was cloned and that clone was moved to a different sprint.

Any ideas on how to solve for this?

I'm unable to just filter out all clones because there it a posibility that a story could be cloned and then left within the current sprint, right?

1 answer

1 accepted

Hi Philip,

This is a known issue, GHS-6541. Here is the solution I came up with last week:

Using the JIRA Suite Utilities, I added a post function on the Create Issue transition. It uses the Clear Field Value for both the Sprint and Story Points custom fields.

Hope it helps.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,319 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot