-
Suggestion
-
Resolution: Timed out
-
None
-
None
I added an issue in the sprint on Day 8 and it appears as if it was in the Sprint from day one. This makes it very difficullt to figure out when issues were added or removed and why the chart appears as it is... On both chart and report, it is as if it was there on day 1 . Neither the chart and report reflect the fact it was added on day 8.
- is duplicated by
-
- Closed
- is related to
-
- Closed
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-436] Issues added mid sprint appear in charts and "Chart Data" CSV report as if they were in the Sprint from day #1
Chris Brookins
added a comment - Ahhh, got it! That is tough.
I won't presume to know what I am talking about, but that doesn't stop me from guessing at solutions 
What if you created the appropriate listeners to know when an issue was added, moved, deleted, etc, you could maintain a private table of the issues GH should consider when creating charts? Just a random thought...
Chris Brookins
added a comment - Ahhh, got it! That is tough.
I won't presume to know what I am talking about, but that doesn't stop me from guessing at solutions What if you created the appropriate listeners to know when an issue was added, moved, deleted, etc, you could maintain a private table of the issues GH should consider when creating charts? Just a random thought... The big issues that we came across here being dynamic are:
- Deleting an issue in JIRA deletes everything
no trace of the issue. - If we want to track the moving issues that would mean we will have to scan all issues from all projects
Just a question of performance.
But like I said in the thread we might be looking if we could find some solution.
Cheers,
Chris Brookins
added a comment - I see - in the thread you indicate you are OK w/an enhancment requirest to address this issue Please consider this the request. I guess I don't understand why the Dynamic chart can't make use of the date an issue was assigned to the Sprint? e.g. if I assign any issue to a sprint, that change is tracked in Jira, and I'd expect that date to be the date by which the chart should reflect it's existance...
Chris Brookins
added a comment - I see - in the thread you indicate you are OK w/an enhancment requirest to address this issue Please consider this the request. I guess I don't understand why the Dynamic chart can't make use of the date an issue was assigned to the Sprint? e.g. if I assign any issue to a sprint, that change is tracked in Jira, and I'd expect that date to be the date by which the chart should reflect it's existance... Hi Chris,
Yeah this is the drawback of Dynamic charts.
Not much we can do. Please see forum thread
Cheers,
That could be part of the solution Chris
We just dont want to add tables or alter in anyway the JIRA schema since we are taking today advantage of the backups and we dont have to bother for JIRA upgrades or migrations.
But you have part of the solution, we will seek for the persistence one
Leave us something to do Chris!!!
Cheers,