Crucible Linked JIRA Issue Field

[Jeff Storey]

Has the "Linked Issue" field from Crucible been removed? I'm using Crucible/Fisheye 2.7.12 and in my review details, that field is not available. I have attached a screen shot of that. In the documentation http://confluence.atlassian.com/display/CRUCIBLE/Using+JIRA+Integration+in+Crucible+Reviews, it says it should be.

[Jobin Kuruvilla [Adaptavist]]

If you go to JIRA, Do you see a link created between this Crucible project and a JIRA project, under Administration > Fisheye Configuration?

If not, do this:

http://confluence.atlassian.com/display/CRUCIBLE/Adding+Project+Links+between+Applications#AddingProjectLinksbetweenApplications-AddingaProjectLink

[Jeff Storey]

That worked, thanks. But in a related question I asked (https://answers.atlassian.com/questions/50990/link-jira-issue-to-crucible-review), someone commented that filling out this field doesn't actually show the revew in the Reviews tab of the JIRA issue (which seems to be correct) and only included the JIRA issue in the description of the crucible review adds the link. What is the purpose of this linked issue field then?

[JamieA]

It seems to be something related to creating a review from jira. God, I hate fecru.

[Jobin Kuruvilla [Adaptavist]]

I don't know the answer to that:) Maybe just an additiona feature to see that in Crucible. I would have thought it will show in JIRA too but I haven't tried it myself.

[Michał Borek]

Hello,

The problem is beause of the fact, that Jira Fisheye plugin (I guess it's fisheye plugin) uses this rest service:

https://crucibleIP/rest-service/search-v1/reviews?temp=$JIRA_KEY

instead of this one:

https://crucibleIP/rest-service/search-v1/reviewsForIssue=$JIRA_KEY

I don't know why they use a generic link if there is a specialized one in Crucible API. I think it's a bug of this plugin and should be fixed.

There are two ways of fixing it imho:

1. Change rest-service

2. Search for linked jira issue in the first rest query.