QA Reviewers

[aapomm]

Spec

Teams have had issues with authors erroneously setting issues/content blocks as "published" and would prefer that Dradis put guards in place that would prevent anyone (with access to a project) to publish any issue/content block in that project.

Proposed solution
This task implements the following:

• Add a "reviewer" virtual role
  • This is represented by a "qa-review" permission to a project
• Add a way to assign authors as reviewers
• Hide the "published" state option for non-reviewers. This is hidden in the following views:
  • issues/content blocks #index
  • qa issues/content blocks #index
  • qa issues/content blocks #show
  • issues/content blocks form (submit_button)

Check List

• Added a CHANGELOG entry