Data access functionality - hide selected requirements and test

[Jesper]

Should be able to hide requirements and test (MT,QT,AT,TS) with same functionality (data access) functionality which is already available in CP8.

Use case:

When testing with customers/vendors they can work in same workspace without seeing our stuff. We can remove access totally to a module, but not certain reqs, test......

[Sigal_Ishay]

Hi Jesper,

Supporting Data Access for entities is on going agenda on our backlog. we have started with providing Data Access support for Defects as that was the most commonly requested entity to answer most of the data hiding use cases described by our customers.

we are now considering what is the next highest priority for supporting data access - User stories, features, requirements, tests etc.

i am changing the status of this idea to Waiting for Votes as we would like to get feedback and understand what is the most requested need (in terms of which entities) for data access as the next phase in this agenda.

regards,

Sigal

[Jesper]

Hi

Thanks for your answer - If I had to prioritize I guess this would look like this:

1. Manual test/test suites (as we do have share/hide certain test for the customers and we are to have many customers in same workspace doing testing.

2. Requirements

3. ....the missing backlog items like US/QS

br jesper

[Jesper]

We have many project areas in the need for this ASAP. Most often we work in close cooperation with customers/vendors and they get access to our Octane solution to do acceptance testing and record defects.

That's why we would like to see Manual test delivered first. We would like it to work similar to defects so the permissions can be controlled with same data access.

br jesper

[Jesper]

Any ETA on delivery of this? We need to be able to hide own MT for customers working in same workspace!

[Jesper]

I see it might be a huge job for complete access control. ....

Howabout making it possible to create a rule for Manual test which can prevent access to the detail screen (see steps, see runs etc)

Some messagebox saying no access allowed based on some field parameter - similar to rule you can create if users try to delete a test. 

br jesper

[Sigal_Ishay]

Hi Jesper,

Indeed support for Data Access per each entity is a very big agenda. this is because data access must apply throughout the entire system and relate to entity relations, all links coming to the entity, API's, Dashboard widgets etc.

in the case of data access for tests it should include also hiding of runs as they expose the test steps. as you probably understand this is not an agenda which we can provide a partial solution for.

However, we do consider the option to control hiding of a specific field - which might provide you the solution for the case you described below (hide only certain fields of a test like 'Description') .

Data Access for Tests is planned on our backlog with high priority but with no ETA yet.

Regards,

Sigal

[Jesper]

Looking forward to this😊

What we need is hiding of 

• Test steps
• Test runs

for certain roles...or preventing them basically from access the detail screen if possible - by clicking the Manual test id

br jesper

[Jesper]

Any updates on this?