Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Answered
Fix Version/s: None
Component/s: Project Administration - Permissions
Labels:

Support reference count:
10
Feedback Policy:

We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

Description

NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

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

Attachments

Issue Links

duplicates

JRASERVER-9107 Create post-function to set security level

Gathering Interest

is incorporated by

JRASERVER-9108 Create post-function to set security level

Closed

is related to

JRASERVER-11125 JIRA 4.0 Enterprise Requirements

Closed

JRASERVER-3619 Validate email addresses of users who sign up

Gathering Interest

JRASERVER-9014 Add "Reporter Group" Permission

Gathering Interest

relates to

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

Closed

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

Closed

JRASERVER-3838 Allow default issue security level at component level

Gathering Interest

mentioned in: Page Loading...

(3 relates to, 1 mentioned in)

Activity

People

Assignee:: Unassigned

Reporter:: Andrew Michalec

Votes:: 95 Vote for this issue

Watchers:: 74 Start watching this issue

Dates

Created:: 18/Nov/2004 11:22 PM

Updated:: 19/Sep/2019 6:07 AM

Resolved:: 27/Jun/2014 4:45 AM