Tracking unplanned release work

[Inna S]

Hi, 

our team is looking for the way to track unplanned work for release.

That is work items added to the release scope AFTER the scope has been finalized.

I'd say this can be redefined in the Jira term as 'issues added to a fixVersion after the fixVersion start date'.

I'm coming from Rally, where we had 'scope creep' on both the Sprint and the Release levels as a basic report. Jira does not have anything like this and I wonder how to get the information.

Any suggestions?

Thank you.

[Rebekka Heilmann _viadee_]

Hi @Inna S 

the only solution I can think of will involve API calls and some scripting.

1. Get all issues of the version you want to inspect, Also get the version including all details
2. Get the change log (issue history) of each history and check for the entry where the issue has been added to the version - check the date of that entry
3. Is the date after the start date of the version? -> unplanned

There might be Marketplace Apps out there, that do exactly that.

[Inna S]

Thank you, @Rebekka Heilmann _viadee_ .

They want to have it in the Jira context.

This sounds like a lot of work for the very basic function that should be in the product core.

I was thinking about adding an extra field to the issues to mark them whenever they are added to a version past the version's start date. This way the team could easily query for such issues whenever they need to, inside Jira and not going elsewhere.

[Inna S]

The API results for the change log is a joke: the history of the issue shows the change of the fixVersions value almost instantly. It messes the order of the change (new value first, removal of the previous one later), but at least it is there.

The toString in the history results is missing the latest change. I've given it 5 min delay before calling the API to get the history, and the latest value is still not there. It would appear there once the next change is made though.

Unbelievable.