I'm with swoo that it would be nice if more permissions relating to test object management were added, but this change is a nice short term mitigation to help folks out and is much appreciated.
I do have 2015.1 installed locally, but all is not well... :( (Specifically, build version 2015/04/03 10:36 on our test instance of Jama)
I have test automation code that logs in via an Active Directory service account.
My test automation service account belongs to two projects (that are worth discussing): A and B.
In project B (which is the Jama project the unit tests for the automated code uses) the service account has manage project access and all of the createNewTestCycle SOAP API calls succeed.
The reason for this permission setup in project B is historical in nature, and the service account really should have create/edit permissions only. The service user only cares about testing related artifacts at present.
In project A however, (which is where the unit test results need to get published) the service account has only create/edit permissions.
When the service user calls the createNewTestCycle SOAP API against project A it fails with a permission error.
However, when I login into the Jama web UI as the service account user and try and create a test cycle for project A (using as close to the same parameters as possible with the web UI) the test cycle is successfully created.
Fyi,
Bill