Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




closeddate not being set?

web-app

We are using Gemini v 3.1.2 (Build 2257).

I am seeing a number of cases where the closeddate column is not being populated even though the issue status is set to "closed."

On the viewissue web page, I discovered that if I simply click the Update link next to the Status field (it's already set to Closed, so I don't even need to change the value shown in the dropdown box), then requery the issue in SQL, the closeddate field then gets updated.

This is somewhat of a major problem for our workflow.

We have a couple of ways to deal with issues in our project. The norm is to set the Fixed For Version field to a known version/release we're working on.

However, as one could imagine, we have a number of "hotfixes" or "patches" and what not we put into production without a formal "version" being created.

So, I have a custom query I run in SQL Mgmt Studio for reporting on issues released with a version or were just plain "done" in a given time period.

But I noticed a number of issues were not being picked up by query. That's when I discovered the issues had NULL in the closeddate column.

MNoreen
· 1
MNoreen
Replies (5)
helpful
0
not helpful

Can you tell from the history what is different between the issues that have the closed date and those that have not?

We have retested this again and it seems to work.

Are you updating the SQL database directly?


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

I can't really tell by looking at the records in the gemini_issues table... they occurred over a variety of different days and by different people entering them from the web UI.

Is there a separate "history" table that I should look at as well?

At any rate, no I don't do any updates in SQL directly... I am only querying the data for reporting purposes.


MNoreen
· 1
MNoreen
helpful
0
not helpful

Please look at the history tab of the issue, it may point to a pattern.


Mark Wing
· 9108
Mark Wing
helpful
0
not helpful

I'm not sure if this is the case, but... I think it might be happening when the issue status is being set to Closed upon issue creation.

That is, consider this scenario. I want document the fact I just did a "quick fix." So, I surf on over to my Gemini issue system, click Create Issue, enter all the appropriate info and even before I click the "Create" (save) button for the first time, I set the status to closed.

Again, I'm not positive about that, but it's my current working theory. I also think this may be affecting the "Attachments (n)" label. That is, on some of these issues, an attachment does exist on the issue. But, the link on the ViewIssue page is saying "Attachments (0)".

If I edit an existing issue and set the status to closed, the closed date field gets set.

Similarly if I edit an existing issue and add an attachment, then the "Attachments (1)" label reflects the number correctly.


MNoreen
· 1
MNoreen
helpful
0
not helpful

Ok, it seems like you have found it. If you set the status on issue creation it will not set the closed date.

We will fix for the next patch: http://gemini.countersoft.com/Default.aspx?p=2&i=2856


Saar Cohen
· 5000
Saar Cohen