0004161: Relations to private issues must only appear to user with appropriate access level - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0004161	mantisbt	relationships	public	2004-07-21 07:39	2004-08-29 02:10

Reporter	vboctor	Assigned To	masc
Priority	normal	Severity	major	Reproducibility	always
Status	closed	Resolution	fixed
Product Version	0.19.0a2
Fixed in Version	0.19.0rc1

Summary	0004161: Relations to private issues must only appear to user with appropriate access level
Description	If a public issue is linked to a private one, and a user with only access to view public ones, the relations section shows the issue id of the private issue but not the status or the summary. In this case the relationship should not appear at all. Ideally, the history should also not show this relation, but that is not possible with the current implementation of history (so I would treat this as a different issue since it also applies to issue like private notes, ...etc.)
Tags	No tags attached.
Attached Files	relationship_api_4161_4146_patch.zip (4,577 bytes)

masc 2004-07-21 07:59 reporter ~0006208	Victor, I'm sure this is the right solution. Although the related bug is private, the relationship exists. So I list the relationship because it's present, but with no information because the user can't have access (the meaning is "there is a relationship but you are not grant to access to it"). If you prefer I can easly implement your proposal hidding the line.

vboctor 2004-07-21 08:21 manager ~0006209	"private" things (whether notes / relationships) are not to be visible (even in terms of existence, not just contents) to users without the appropriate access level. This is part of the privacy of being private! Also your current solution may be confusing to some users (for example, see last note in 0003948).

masc 2004-07-21 08:42 reporter ~0006213	Now it's clear. I'm going to update the API.

masc 2004-07-21 10:12 reporter ~0006216	Fixed. See patch attached. The relationship line is skipped if the user is not grant to view the related bug