nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Reviews do not show up in Issue's "Reviews"-tab (in JIRA)

Reto Conconi

We are creating reviews using smart commits. We mention the JIRA issue key in the commit message as well. In the mentioned issue we can then look at the changeset in the "Source"-tab. There we see that the smart commit successfully connected the changeset to the JIRA issue and also created a review. The review shows also up as a Link in the source tab too. But surprisingly the "Reviews"-tab of the same issue is empty. Why does JIRA not display the review there? What kind of configuration is needed to make this work?

We are using: JIRA 4.4.1, Crucible 2.7.4, Fisheye-Plugin 3.4.7

Best regards

Reto Conconi

Accepted answers

Reto Conconi

I think I found the problem:

When creating the review using smart commits we have to mention the JIRA issue key as the first thing in the whole commit message. This then automatically links the JIRA issue to the newly created review and also creates the link from the JIRA issue to the review issue in the JIRA issue's "Review" tab. (I think this works because the first line of the commit message becomes the title of the review. This then triggers Crucible to create the two-way linking... I am just guessing...)

It's kind of weird though that JIRA finds the changeset automatically and also links the review in the "Changeset tab" of the JIRA issue but does not create the link in the review tab based on the same heuristics. But with the mentioned trick above we can work around this issue.

All comments

Felipe Kraemer

Hi Reto,

Could you please make sure that you have a Project Link between the JIRA project and the Crucible Project?

This should do the trick.

Please let us know how it goes.

Kind regards,
Felipe Kraemer
Atlassian Support

Renjith Pillai

And in the Fisheye instance which is linked in Jira, mark the Jira project against the appropriate Crucible project name.

Reto Conconi

I think I found the problem:

JMTyler

I was just having this same issue, thank you so much for figuring this out!

This seems like a serious drawback of Crucible, that a review's name needs to be equal to JIRA's issue key in order for JIRA to link it... Considering that there is already a linking feature between review's and issues. Doesn't make sense to me.

Anyway, thanks for answering your question with your findings! You didn't have to, but it just saved me many headaches.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

fisheye-crucible