This is the documentation for Crucible 3.3. View the latest version of

Unknown macro: {spacejump}

or visit the latest Crucible documentation home page.

Skip to end of metadata
Go to start of metadata

Note that your Crucible and JIRA instances must be linked to make use of these JIRA integration features. See Linking Crucible to JIRA.

(question) The Crucible project requires a linked JIRA project before issues can be linked to reviews. 

See all the Crucible reviews related to a JIRA issue

In a JIRA issue, the Development panel shows the number of reviews that are linked to the issue. Click the reviews link to see details of those reviews.

Link your Crucible review to a JIRA issue

When creating, or editing, your review, Crucible will suggest a JIRA issue that can be linked to the review, if a JIRA issue key is found in the review title. You can:

  • click the suggested JIRA issue key, to link it to the review
  • delete the suggested JIRA issue and specify a different issue key and click Link to save it.

Create a JIRA issue from a review comment

When viewing any review comment (genaral, file, inline), you can click Create Issue in the comment to create a JIRA issue. Crucible suggests the JIRA instance, project and issue type, but you can modify these. This requires JIRA 5.0, or later, and is disabled if Crucible is integrated with an earlier version of JIRA.

See Creating JIRA issues from the review for more details.

Transition JIRA issues from within Crucible

For Crucible reviews that have linked JIRA issues, you can advance the JIRA workflow for the issue from within Crucible. You can do this at any time by clicking the linked issue, or when you close the review:


See Transitioning JIRA issues for more details.

See issues from multiple instances of JIRA

Crucible can link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA instances, or a single team can link to issues across multiple JIRA servers.

  • No labels