[#JRA-4502] Comment Viewable By not (always) logical when Security level is used

JIRA

Comment Viewable By not (always) logical when Security level is used

Created: 08/Sep/04 03:22 AM Updated: 02/Jan/08 09:38 PM

Component/s:

Comments, Permissions Security

Affects Version/s:

2.6.1 Enterprise

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-12347 Ability to hide comment visibility

Participants:	Mark Chaimungkalanont [Atlassian], Owen Fellows and Ray Oei [Furore]
Since last comment:	3 years, 22 weeks, 4 days ago
Labels:

Description

« Hide

The 'Comment viewable by' option displays all groups the user is a member, seems logical. But when the issue itself has been restricted by a security level the choices might not be logical.
For instance: a security level 'restricted' has been defined containing usergroups 'groupA', 'groupB' and 'groupC'
A user from groupA is also member of groups 'groupD' and 'groupE'.
When an issue has the level 'restricted' this user can add a comment and set the 'Viewable by' for 'All users', 'groupA', 'groupD' and 'groupE'.
It seems to me that 'All users' would translate to 'groupA' and the choices for 'groupD' and 'groupE' would not be usefull because members of those groups have no access to this particular issue.
So this option should not be available in this case.

Is the user also member of groupB it seems logical the 'Viewable by'
would display 'All users' (being groupA and groupB), groupA and groupB
So the comment can be restricted to a particular group within the security level.

Does this make any sense?

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Owen Fellows added a comment - 10/Sep/04 11:26 AM

This does make sense and you are correct the available options should take into account the Issues Security Level.

[ Permlink | « Hide ]

Ray Oei [Furore] added a comment - 30/Sep/04 07:29 AM

In second thought: you would probably want to be able to give permissions to any combination of groups which are defined in the security level of the issue.
So the user from groupA should be able to select a group within the security level (groupA, groupB, groupC or any combination of these groups) although the user is only member of groupA.

This changes when the issue itself had no security level set...

[ Permlink | « Hide ]

Ray Oei [Furore] added a comment - 14/Mar/05 04:08 AM

Any idea íf or when this is behaviour will be improved?

[ Permlink | « Hide ]

Mark Chaimungkalanont [Atlassian] added a comment - 15/Mar/05 05:44 PM

Unfortunately, it won't be in the upcoming 3.2 release. We're making some internal changes to our processes. Hopefully this will mean that we can fix issues such as this more effecitively.