[#JCHART-241] The "TimeInStatusCFType" does not keep the database and index consistent.

JIRA Charting Plugin

The "TimeInStatusCFType" does not keep the database and index consistent.

Created: 09/Sep/08 02:34 AM Updated: 09/Sep/08 02:35 AM

Component/s:

Chart Types

Affects Version/s:

1.3.13, 1.4

Fix Version/s:

None

Security Level:

public (Anyone can view the issue)

Time Tracking:

Not Specified

Database:	MySQL 5.x
Labels:

Description

« Hide

The TimeInStatusCFType values are only stored in the database when an issue is resolved. If the issue is reopened, this value is immediately removed from the database. While this works fine for the database, the index seems to think that the custom field still has a value. This can lead in inaccurate graphs.

There is a logic error in TimeInStatusCFType.getValueFromIssue. The code:

else if (issue.getResolution() == null && dbString != null)
        {
            clearDatabaseValue(field, issue, dbString);
        }

        if (NULL_STRING.equals(stringValue))
        {
            return null;
        }
        else
        {
            return stringValue;
        }

It clears the value from the database but still returns the old value which is subsequently indexed.

All

Comments

Work Log

Change History

FishEye

Crucible

Builds

Sort Order:

There are no comments yet on this issue.