Closeddate not always populated
I am running some reports against the gemini db, and I had assumed that the closeddate would be filled in every time an issue was updated to a status which is marked as final. There seem to be a number of tickets whoose status we have marked as closed (and the final flag is set to true) but yet the closeddate is null. Is this expected? Is there another way to get the closeddate? Should I be using the reviseddate?
rlevine
· 75 |
|
Tuesday, September 27, 2011, 3:37:25 PM |
0
|
Closed date should be populated, can you check from the history when the status changed? Generally, looking at revised date should be good enough, but people might still change something after it was closed. |
||||
|
0
|
I totally agree with that. I am querying items that were closed in the past week. I have a number of such examples. |
||||
|
0
|
Can you ask the users how did they close these items? We would like to get to the bottom of it but cannot replicate it. |
||||
|
0
|
I am one of those users in this case. I can think of these 3 ways of how I may close an issue. 1) in the issue set the status to closed. 2) in a comment set the status to closed. 3) in a report of all items set the status to closed (in line) I have no idea which way I did each. |
||||
|
0
|
We have tested all options and it seems to work for us, does it still happen now when you close items? |
||||
|
0
|
Yes it does. I'm not sure how to replicate it, but I run a weekly report which includes all issues closed last week and not all issues that were closed (and currently marked as closed) are being returned. |
||||
|
0
|
I was just able to replicate it by setting the status to closed in the comment form (i.e. when adding a comment) |
||||
|
0
|
I understand Saar is having a remote session with you on Monday, can we conver this issue as well? (we can't seem to replicate it). |
||||
|
0
|
Sure, that works. Thanks |
||||
|