[#TMCT-13] status vs time timechart with same value for totals for all dates

JIRA Timecharts Plugin

status vs time timechart with same value for totals for all dates

Created: 10/May/07 10:44 AM Updated: 12/Dec/07 04:06 AM

Component/s:

None

Affects Version/s:

3.8

Fix Version/s:

None

Time Tracking:

Not Specified

File Attachments:	1. atlassian-jira.log (661 kB)
Environment:	« Hide JIRA Enterprise Edition, Version: 3.8.1-#210 Charting Plugin 1.3.5 Show » JIRA Enterprise Edition, Version: 3.8.1-#210 Charting Plugin 1.3.5

Labels:

Description

« Hide

Using the settings:
Filter : all issues
Summary field : status
Start Date : <empty>
End Date : <empty>
Interval : 30
Granularity : Day
Show Totals : Yes

The values seem to be off.
The total number of issues from Apr 12 was not 110, as reported by the chart.
Actually, 110 total issues is valid only on May 9. Prior to that date we had less total issues.
The other value that seems off is the number of of open issues.
For Apr 12, the report gives 83 open issues, but there weren't 83 total issues on that date.

Is there something I'm doing wrong or is this really a bug?
Thanks,
Asaf

Date Closed In Progress Open Reopened Resolved Total
Thu Apr 12 00:00:00 PDT 2007 4 2 83 1 20 110
Fri Apr 13 00:00:00 PDT 2007 4 2 77 1 26 110
Sat Apr 14 00:00:00 PDT 2007 4 3 74 1 28 110
Sun Apr 15 00:00:00 PDT 2007 4 3 74 1 28 110
Mon Apr 16 00:00:00 PDT 2007 3 3 73 2 29 110
Tue Apr 17 00:00:00 PDT 2007 4 3 72 1 30 110
Wed Apr 18 00:00:00 PDT 2007 4 3 72 1 30 110
Thu Apr 19 00:00:00 PDT 2007 5 3 72 1 29 110
Fri Apr 20 00:00:00 PDT 2007 5 3 72 1 29 110
Sat Apr 21 00:00:00 PDT 2007 5 5 70 1 29 110
Sun Apr 22 00:00:00 PDT 2007 5 5 70 1 29 110
Mon Apr 23 00:00:00 PDT 2007 5 5 70 1 29 110
Tue Apr 24 00:00:00 PDT 2007 5 5 70 1 29 110
Wed Apr 25 00:00:00 PDT 2007 5 5 70 1 29 110
Thu Apr 26 00:00:00 PDT 2007 6 5 69 1 29 110
Fri Apr 27 00:00:00 PDT 2007 6 6 66 1 31 110
Sat Apr 28 00:00:00 PDT 2007 6 8 64 1 31 110
Sun Apr 29 00:00:00 PDT 2007 6 8 64 1 31 110
Mon Apr 30 00:00:00 PDT 2007 6 8 64 1 31 110
Tue May 01 00:00:00 PDT 2007 6 9 63 2 30 110
Wed May 02 00:00:00 PDT 2007 6 9 58 0 37 110
Thu May 03 00:00:00 PDT 2007 18 11 51 3 27 110
Fri May 04 00:00:00 PDT 2007 18 12 50 3 27 110
Sat May 05 00:00:00 PDT 2007 18 10 50 3 29 110
Sun May 06 00:00:00 PDT 2007 18 10 50 3 29 110
Mon May 07 00:00:00 PDT 2007 18 11 48 3 30 110
Tue May 08 00:00:00 PDT 2007 21 10 44 4 31 110
Wed May 09 00:00:00 PDT 2007 23 9 43 5 30 110
Thu May 10 00:00:00 PDT 2007 24 10 40 4 32 110

Description

Using the settings: Filter : all issues Summary field : status Start Date : <empty> End Date : <empty> Interval : 30 Granularity : Day Show Totals : Yes The values seem to be off. The total number of issues from Apr 12 was not 110, as reported by the chart. Actually, 110 total issues is valid only on May 9. Prior to that date we had less total issues. The other value that seems off is the number of of open issues. For Apr 12, the report gives 83 open issues, but there weren't 83 total issues on that date. Is there something I'm doing wrong or is this really a bug? Thanks, Asaf Date Closed In Progress Open Reopened Resolved Total Thu Apr 12 00:00:00 PDT 2007 4 2 83 1 20 110 Fri Apr 13 00:00:00 PDT 2007 4 2 77 1 26 110 Sat Apr 14 00:00:00 PDT 2007 4 3 74 1 28 110 Sun Apr 15 00:00:00 PDT 2007 4 3 74 1 28 110 Mon Apr 16 00:00:00 PDT 2007 3 3 73 2 29 110 Tue Apr 17 00:00:00 PDT 2007 4 3 72 1 30 110 Wed Apr 18 00:00:00 PDT 2007 4 3 72 1 30 110 Thu Apr 19 00:00:00 PDT 2007 5 3 72 1 29 110 Fri Apr 20 00:00:00 PDT 2007 5 3 72 1 29 110 Sat Apr 21 00:00:00 PDT 2007 5 5 70 1 29 110 Sun Apr 22 00:00:00 PDT 2007 5 5 70 1 29 110 Mon Apr 23 00:00:00 PDT 2007 5 5 70 1 29 110 Tue Apr 24 00:00:00 PDT 2007 5 5 70 1 29 110 Wed Apr 25 00:00:00 PDT 2007 5 5 70 1 29 110 Thu Apr 26 00:00:00 PDT 2007 6 5 69 1 29 110 Fri Apr 27 00:00:00 PDT 2007 6 6 66 1 31 110 Sat Apr 28 00:00:00 PDT 2007 6 8 64 1 31 110 Sun Apr 29 00:00:00 PDT 2007 6 8 64 1 31 110 Mon Apr 30 00:00:00 PDT 2007 6 8 64 1 31 110 Tue May 01 00:00:00 PDT 2007 6 9 63 2 30 110 Wed May 02 00:00:00 PDT 2007 6 9 58 0 37 110 Thu May 03 00:00:00 PDT 2007 18 11 51 3 27 110 Fri May 04 00:00:00 PDT 2007 18 12 50 3 27 110 Sat May 05 00:00:00 PDT 2007 18 10 50 3 29 110 Sun May 06 00:00:00 PDT 2007 18 10 50 3 29 110 Mon May 07 00:00:00 PDT 2007 18 11 48 3 30 110 Tue May 08 00:00:00 PDT 2007 21 10 44 4 31 110 Wed May 09 00:00:00 PDT 2007 23 9 43 5 30 110 Thu May 10 00:00:00 PDT 2007 24 10 40 4 32 110

Show »

All

Comments

Work Log

Change History

FishEye

Crucible

Builds

Sort Order:

[ Permlink | « Hide ]

Matt Doar added a comment - 10/May/07 12:32 PM

What were the expected values? Less than 110 and 83, but how much?

And is your filter catching all issue types? Please would you add the Filter Summary details.

Does the current value (today) accurately reflect what you expect to see?

[ Permlink | « Hide ]

Asaf Matatyaou added a comment - 10/May/07 01:08 PM

The expected value for total issues on April 12 was 61.
The expected value for total issues on May 10 was 110.

The filter I'm using captures all issues in the database (all projects, all issues attributes, any status, user, etc.)

The current values do accurately reflect what I expect to see.

Please let me know what information I can provide that would be helpful.

[ Permlink | « Hide ]

Matt Doar added a comment - 11/May/07 11:56 AM

Thanks, Asaf. Would it be possible to get a backup of the data?The ordinary .zip backups that Jira makes would be fine. If that's not possible, then perhaps a copy of the logs/catalina.out logfile after the debugging has been enabled? Details of how to enable this are in the Troubleshooting section of http://confluence.atlassian.com/display/CODEGEIST/Timecharts

[ Permlink | « Hide ]

Asaf Matatyaou added a comment - 11/May/07 03:29 PM

I will be able to send the logs/catalina.out file, but won't be able to send a backup (at least for now).
I have updated the properties file, but I have to wait to shutdown the server over the weekend, for the changes to take affect.
I will send the logs by Monday.

[ Permlink | « Hide ]

Asaf Matatyaou added a comment - 14/May/07 04:34 PM

I updated the properties file with the following two lines (at the end):

log4j.category.com.packetmotion.jira.plugin.report.timecharts = DEBUG, filelog
log4j.additivity.com.packetmotion.jira.plugin.report.timecharts = false

I can't find any output in the logs/catalina.out file with "timecharts."

What output should I be looking for?

BTW, as an example of how the data changes, consider the following data from the same database a few days later.
The database now has a total of 114 issues on May 14 (relative to 110 on May 10).

You will notice that the numbers changed for Apr 12 (as well as the other dates) when compared to the data provided in the description of the issue.

Thu Apr 12 00:00:00 PDT 2007 4 2 87 1 20 114
Fri Apr 13 00:00:00 PDT 2007 4 2 81 1 26 114
Sat Apr 14 00:00:00 PDT 2007 4 3 78 1 28 114
Sun Apr 15 00:00:00 PDT 2007 4 3 78 1 28 114
Mon Apr 16 00:00:00 PDT 2007 3 3 77 2 29 114
Tue Apr 17 00:00:00 PDT 2007 4 3 76 1 30 114
Wed Apr 18 00:00:00 PDT 2007 4 3 76 1 30 114
Thu Apr 19 00:00:00 PDT 2007 5 3 76 1 29 114
Fri Apr 20 00:00:00 PDT 2007 5 3 76 1 29 114
Sat Apr 21 00:00:00 PDT 2007 5 5 74 1 29 114
Sun Apr 22 00:00:00 PDT 2007 5 5 74 1 29 114
Mon Apr 23 00:00:00 PDT 2007 5 5 74 1 29 114
Tue Apr 24 00:00:00 PDT 2007 5 5 74 1 29 114
Wed Apr 25 00:00:00 PDT 2007 5 5 74 1 29 114
Thu Apr 26 00:00:00 PDT 2007 6 5 73 1 29 114
Fri Apr 27 00:00:00 PDT 2007 6 6 70 1 31 114
Sat Apr 28 00:00:00 PDT 2007 6 8 68 1 31 114
Sun Apr 29 00:00:00 PDT 2007 6 8 68 1 31 114
Mon Apr 30 00:00:00 PDT 2007 6 8 68 1 31 114
Tue May 01 00:00:00 PDT 2007 6 9 67 2 30 114
Wed May 02 00:00:00 PDT 2007 6 9 62 0 37 114
Thu May 03 00:00:00 PDT 2007 18 11 55 3 27 114
Fri May 04 00:00:00 PDT 2007 18 12 54 3 27 114
Sat May 05 00:00:00 PDT 2007 18 10 54 3 29 114
Sun May 06 00:00:00 PDT 2007 18 10 54 3 29 114
Mon May 07 00:00:00 PDT 2007 18 11 52 3 30 114
Tue May 08 00:00:00 PDT 2007 21 10 48 4 31 114
Wed May 09 00:00:00 PDT 2007 23 9 47 5 30 114
Thu May 10 00:00:00 PDT 2007 24 10 44 4 32 114
Fri May 11 00:00:00 PDT 2007 24 10 44 4 32 114
Sat May 12 00:00:00 PDT 2007 24 10 44 4 32 114
Sun May 13 00:00:00 PDT 2007 24 10 44 4 32 114
Mon May 14 00:00:00 PDT 2007 24 10 44 4 32 114

[ Permlink | « Hide ]

Matt Doar added a comment - 14/May/07 05:34 PM

Hmm. Maybe it's going into atlassian-jira.log which will be in the directory where you last restarted Jira

[ Permlink | « Hide ]

Asaf Matatyaou added a comment - 14/May/07 06:54 PM

Attached is the atlassian-jira.log with the debug output.

[ Permlink | « Hide ]

Asaf Matatyaou added a comment - 21/May/07 01:57 PM

Matt,
I'm just checking in. Is there any other information I can provide that can be helpful?
Is the log file that I attached OK?
Thanks,
Asaf

[ Permlink | « Hide ]

Matt Doar added a comment - 21/May/07 02:44 PM

Asaf,

Thanks, the log file is just right. A time crunch at work means I haven't had a chance to look at it yet, sorry.

~Matt

[ Permlink | « Hide ]

Vincent Eggen added a comment - 30/Aug/07 12:11 PM

We are experiencing the same behavior.

In fact we saw a clear difference between the results provided by the pending stock chart and the time chart.

The pending stock chart is simply showing the number of unresolved issues over the time for a given filter.
And when we tried to have a similar output using the time chart (same filter, field = resolution), we had a clear difference in the output.

Several tests later and we had to confirm that the Pending stock chart was right, not the time chart.

Test made on Jira 3.10.

Vince

[ Permlink | « Hide ]

Divya Hari added a comment - 19/Oct/07 06:23 AM

We seem to have the same problem. We started our JIRA system on May 17th, 2007 and on that day we had just about 3 issues. Now we have about 402 issues in the system. But when the Time Chart is displayed, it shows the system to have about 361 issues on May 17th. And the total number of issues always remains the same even if new issues are added every day.

We use this system extensively and it would really help if you could tell us if there is a workaround for this problem, perhaps the section in the source code where things are going wrong.

We use JIRA 3.9.
Thanks a lot.

[ Permlink | « Hide ]

Wojciech Gdela added a comment - 11/Dec/07 05:09 AM

I've also encountered this problem and I analyzed what's wrong. The reason is that while the plugin collects data, and progresses backwards in time it ignores the fact, that issues may not existed at a certain point in time.

I.e. at tuesday I've created an issue with state open. Now i generate timechart report from monday till wednesday. The report shows:

wednesday: 1 open issue
tuesday: 1 open issue
monday: 1 open issue -> oops, haven't noticed that the issue had not existed at all at monday

I've managed to fix the code, but it is an ugly workaround, so i won't attach the patch.

[ Permlink | « Hide ]

Chris Cliffe added a comment - 12/Dec/07 04:06 AM

Is this likely to be resolved in the near future. This is a feature of the JIRA that we would like to use as part of our reporting procedure, but at the moment it is not possible. I am probably interested in the 'ugly workaround' if there is no official fix due soon.