I have a JIRA ticket with a linked Crucible review. In the "Development" panel of the JIRA ticket, the review is labeled as "OPEN":
If I then click on "1 review", the window opens, showing me more details about that review: ID, Title, Status, etc. The Status there says "CLOSED". And indeed, following the ID link to the review, in Crucible, the review is labeled "CLOSED". So why does the Development panel in JIRA say it's OPEN?
Searching for JIRA tickets with the following query also includes this ticket:
issue.property[development].openreviews > 0
Why are the development panel and this JQL query reporting a review as OPEN when it is closed?
I have the same problem.
issue.property[development].openreviews > 0, returns a lot of false results.
I already re-indexed the Jira project... no luck.
I am currently re-indexing the Crucible reviews, but I don't expect any better luck.
I have an issue with 9 code reviews. When started the re-indexing of the reviews, the list of reviews in my issue became empty, as expected. However, Jira still said there are 2 open code reviews in that issue (while the list was empty!). The list is now being re-populated, and Jira still says I have 2 open code reviews in that issue (where all reviews show as closed!). I also noticed that my issue is linked to code reviews that are not linked back to it (they only reference my issue in the review objectives... maybe this registers the review with the issue?)...
I've searched Fisheye/Crucible for the issue key everywhere. I see all commits and code reviews, as expected, and I have no idea why Jira says there are 2 open code reviews.
I found the cause.
I am in version 4.5 of Crucible.
Crucible links the review to all Jira keys it finds in the smart commit comments, also shown in the review objectives.
Only the first key is considered the main issue to link the review to.
That first issue shows the review as closed, as expected, while all other issues incorrectly show the review as open.
Then I found this https://jira.atlassian.com/browse/CRUC-5837. Maybe this bug might have been fixed in version 4.6.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am also using v4.5.0.
In my case, the review only references one JIRA ticket, and it does so in the 'Objectives'. This seems to be the reason the review is listed under "Development" in the JIRA ticket. So I don't observe that the first issue (the only issue in my case) shows the review as closed.
To experiment, I removed the JIRA ticket # from the comment, and added it as a linked ticket. It didn't change the behavior in JIRA.
It is nice to know that I'm not the only person observing this behavior.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.