Hi,

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.

Hi,

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.

Thanks in advance

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.

But we have configured 'Updater' privilege as below for Developer profile:

read rights: Elements of own projects
create rights: No element
update rights: Elements of own projects
delete rights: No element.

And description for 'Updater' privilege is showing as "Read and Update only his projects".

So if delete rights set as for No element, how the delete option is enabling for any attached/linked elements ?

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

Ok, I understand this.

In such case, if I still want to restrict only the attached links not to be delete with 'Update' privilege whether can I achieve this by changing the code?
If yes then which code needs to change and how?
Please suggest..

Thanks.

in view/objectDetail.ph, function drawLinksFromObject()