[#JRA-5276] Allow default issue security level at user/users-group level

JIRA

Allow default issue security level at user/users-group level

Created: 18/Nov/04 05:22 PM Updated: 26/May/08 05:55 AM

Component/s:

Permissions Security

Affects Version/s:

3.0.2

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Part

This issue is incorporated by:

~~JRA-9108~~ Create post-function to set security level

Reference

This issue relates to:

JRA-3838 Allow default issue security level at component level

JRA-4794 Allow default security level to be set per issue type

This issue is related to:

JRA-9014 Add "Reporter Group" Permission

JRA-3619 Validate email addresses of users who sign up

~~JRA-11125~~ JIRA 4.0 Enterprise Requirements

Participants:	=Neal Applebaum, Andrew Michalec, Jeff Turner [Atlassian], Nick Menere [Atlassian], Patrick Trigwell and Ray Oei [Furore]
Since last comment:	2 years, 3 weeks, 5 days ago
Support reference count:	10
Labels:

Description

« Hide

It would be nice to have possibility to define default issue security level for each user/group.

This could be helpful in situation when customer (one group) creates issues with normal security level and 'internal' developers (other group) create issues within 'private' scope.
Current model requires from developers manual setting 'private' security to hide issues from customer – it is at least annoying.

This is extension to current issue security model so it is relatively simple to implement

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Jeff Turner [Atlassian] added a comment - 31/Jan/05 06:16 PM

Yes, this request seems to be very popular recently. It could be implemented as a workflow post-function (which checks the group and sets the security leve):
http://confluence.atlassian.com/pages/viewpage.action?pageId=11764

[ Permlink | « Hide ]

Ray Oei [Furore] added a comment - 25/Mar/05 04:53 AM

It would be very helpfull to assign default security levels to groups and/or users. Currect ability to set the level manually per issue leaves the door wide open to issues with the wrong level.

[ Permlink | « Hide ]

Andrew Michalec added a comment - 10/Apr/05 01:39 PM

Solution that Jeff was talking about has been already implemented in our JIRA environment.

Nevertheless I was thinking about ability to set "issue security level" (combobox) on issue form to different initial values, that depends on reporter's membership (provided default value is associated with groups).
For exaple: given three levels "levelOne", "levelTwo" and "levelThree" user A creating issue has initially level at "levelOne" but user B has initially level at "levelTwo" despite the fact that both can set any of these three levels.

What is it all about? First, the possibility of mistake - if someone has to set every time level "secure" it is more probable that he/she will forget it than to forget to change from default "secure" level to "everybody". Second, coherent with current model - if reporter has no "set security level" permission, assigned default level appropriate to his/her membership will be more precise; more than single global default level of security scheme associated with project.

[ Permlink | « Hide ]

=Neal Applebaum added a comment - 09/Aug/06 08:54 PM

I just installed the user-contributed extension to this. It seems to work great for me, so far. Haven't used it in live yet, but in testing it looked like a pretty good workaround.

[ Permlink | « Hide ]

Patrick Trigwell added a comment - 08/Nov/06 05:18 AM

You've marked this as a duplicate of ~~JRA-8624~~ (configuring the default "Viewable by" drop-down when adding a comment). This is not a duplicate of ~~JRA-8624~~. Please can you therefore reopen ~~JRA-8624~~.

[ Permlink | « Hide ]

Nick Menere [Atlassian] added a comment - 08/Nov/06 06:30 PM

Patrick,

I believe that link was wrong, though it is a duplicate of JRA-9091, so it should still be closed as a duplicate.

Cheers,
Nick