Solve for cloned issue retaining sprint when creating scope reports?

[Philip Chiappini]

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?

[Brannon Fay · Accepted solution]

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.

Brannon