I logged in as Tester role and attached few test cases for requirement
Then logged in as Developer role and navigated to this Requirement to update status.
There I am able to delete the attached test cases for the requirement which has attached by another person.
So tool is allowing to delete the attached/added elements for another users.
Note:- a) Developer role has assigned 'Updater' privilege to update the status of Requirements
b) all are assigned to same project.
Please advise me how to restrict 'delete' option for an added/attached element which has not added by own.
In your use case, Developer does not delete test case created by Tester.
He delectes only the link between the Requirment and the Test Case. This is not the same.
The test case still exists, but is not linked any more to the Requirement.
This is possible as long as Developer has update right on the requirement : he just updates the description of the requirement.
Even though link between the Requirement and the Test Case gets break, its an issue.
If any person attempt to do this (unfortunately) its very difficult to track number of test cases linked for a requirement.
And this is not only about the Requirement-Test cases linkage case. For all other types of linkage (such as Requirement-Tickets, Attachments, other elements..) cases also.
If any other linked elements deleted by some person then also its big problem.
So can we restrict this 'delete' option for a person (with updater privilege) if he has not the creator of the linkage.
Even though link between the Requirement and the Test Case gets break, its an issue.
If any person attempt to do this (unfortunately) its very difficult to track number of test cases linked for a requirement.
Yes, and it may be a real use case, not an issue.
If a resource starts working on a rquirement, any other alowed to work on the requirement
Fortunately you'll have the history of change to see that a link has been removed
And this is not only about the Requirement-Test cases linkage case. For all other types of linkage (such as Requirement-Tickets, Attachments, other elements..) cases also.
If any other linked elements deleted by some person then also its big problem.
No, it may be a real use case.
Gor instance on ticket, analyst first analysis ticket and add link to a document where he thinks the issue comes from.
Developer, when coding corrections, find the link is incorrect : he may fix it and remove the link.
So if delete rights set as for No element, how the delete option is enabling for any attached/linked elements ?
To add or remove a link, you just need update rights.
Delete rights concern the item.
Notes, Links and Attachments are parts of the item, and just require update rights on the item to be added / updated / deleted.
For instance with rights to read / update but not delete / create for test cases :
- user cannot create a test case
- user cannot delete existing test case
- user can update test cas : this includes add/delete note, links and attachments
En poursuivant votre navigation, vous acceptez le dépôt de cookies tiers destinés au bon fonctionnement et à la sécurisation du site (gestion de session, reCaptcha) et à une analyse statistique anonymisée des accès sur notre site (Google Analytics). Si vous vous inscrivez, les informations que vous fournirez ne seront jamais divulguées à un tiers sous quelque forme que ce soit. En savoir plus
Cookies settings
×
Functional Cookies
Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.
Session
Please login to see yours activities!
Other cookies
Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.