Permissions

With introduction of Cross Linking feature (release 2.1), Cases from different Projects can be added to a Cycle. Users who do not have access to a project, will not be able to access the Case / Run from that project in the Cycle.

To indicate the access user has on different Entities - Case / Cycle & Run, Permission object will be returned in response.

Sample Permission object is below:

• Permission object has value and error properties.

• Value is a bit map where in bits from right to left represent the Delete, Write & Read permissions.
  7 - Full access (Delete, Write, Read)
  3 - Only Write and Read
  1 - Only Read
  0 - No permission

• Error is an enum indicating why user does not have access over the cycle.
  Error can be one of
  EVALUATION_FAILED - There was error while evaluating the permission value.
  JIRA_PROJ_NO_ACCESS - User does not have access on the entity as User does not have permission on entity’s Project.
  AIO_TESTS_DISABLED_PROJ - User does not have access on the entity as AIO Tests has been disabled for the entity’s Project.
  AIO_TESTRUN_REFSTEP_NO_ACCESS - User does not have access on the Run as one of the Referenced Step Case is not accessible.

• If user has permission (error value is null), then error will not be returned in the response.

Below table shows the Permission Values and Delete / Write / Read access it indicates.
If the bit is ON (having value 1), it means user has that permission for performing those operations.

Below table shows the Run permissions based on corresponding Cycle and Case access.

User who has Read only access to Run, will not be able to change the status of a run, but would be able to view its data. On trying to update such a Run using the API will return a 4xx response.