Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being committed to a repository.
Please note, the version of Crucible running in JIRA Studio may differ from the latest released version of Crucible. Please refer to JIRA Studio Application Versions for that latest version information. |
On this page:
Working with Reviews
|
To work with reviews,
|
Crucible User Documentation
|
The guide listed below contains information on how to use Crucible. Please note, this guide does not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone Crucible). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions. |
JIRA Studio-specific Documentation
|
Project review permissions are inherited from Crucible's default permission schemes. However, they are modified according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions that apply to a project's source also apply to that project's reviews. |






