In Crucible you can review all of the code commits relating to a single story created in a project/issue tracking tool like Rally, Jira or YouTrack.
Revizor needs this functionality too as it's an efficient way of achieving story sign-off.
When code is committed it should have a unique identifier assigned to it which indicates the story the code relates to. This unique identifier would be picked up by Revizor.
Code commits should include:
1) development code
2) bug fix code
3) test code
4) any other code commits relating to the story, e.g. code configuration changes
In Crucible you can review all of the code commits relating to a single story created in a project/issue tracking tool like Rally, Jira or YouTrack.
Revizor needs this functionality too as it's an efficient way of achieving story sign-off.
When code is committed it should have a unique identifier assigned to it which indicates the story the code relates to. This unique identifier would be picked up by Revizor.
Code commits should include: 1) development code 2) bug fix code 3) test code 4) any other code commits relating to the story, e.g. code configuration changes