0024513: Relationships as separate right in Workflow Threshold - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update
0024513	mantisbt	administration	public	2018-05-31 10:03	2018-06-06 00:39

Reporter	Rost	Assigned To	atrol
Priority	normal	Severity	feature	Reproducibility	N/A
Status	closed	Resolution	duplicate
Product Version	1.3.15

Summary	0024513: Relationships as separate right in Workflow Threshold
Description	Sometimes QA are quite smart to find related issues, like product features, regression things etc. However they can't link anything because section Relationships is protected to read-only and linked to right 'Update an issue'. In the same time, 'Update an issue' for Developers isn't a good practice, because in this case Developer may silently update original issue with absolutely irrelated data with breaking QA processes. Removing this right from Developer breaks ability to change relationships. So I suggest adding right 'Change relationships' to page Workflow Threshold with ability to manage things on administrator level.
Tags	No tags attached.

atrol 2018-05-31 12:25 developer ~0059993	Known feature request see 0011203

Rost 2018-06-01 03:47 reporter ~0059997	Before making the report I review all things similar to relationships. I also saw the 0011203, but the following reasons forced me to create the separate report: original report 0011203 isn't actual. Today developer may change relationships and nobody will up (and implement) the issue nowadays nothing made since the 2011 the discussion is moved to separation of ADD/DELETE functionality between roles current mantis rights set is in concept 'one complex rule' rather separation of each action regarding permission I feel the similarity, but here are enough user groups to differentiate users with such right. Current mantis rights don't allow separation of CRUD concept and if it may be adopted to one of them (relationships, for example), it may move system huge and complex even for proper administration rather for impossible development with current development speed and many actual directions. So I think that request would be reopened and confirmed, rather old 0011203.

atrol 2018-06-04 02:29 developer ~0060008	@Rost Our way to triage incoming issues is to resolve new issues as duplicate of older ones. This helps to keep all related information at a single place. The reporter of the new issue is added to the monitoring list of the old issue, so he is notified of any changes. I recommend to add any additional information you have as a note to the old issue. nothing made since the 2011 I don't expect that someone will start to implement this feature request soon. It depends on priority and a developer or community member deciding to spend their time on a specific issue. Contributions are welcome.