Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Fixed
Component/s: Project Administration - Workflows and statuses
Labels:

UIS:
10
Support reference count:
24
Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

Description

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

Atlassian Update - 19 March 2015

Hi everyone,

This is a routine update of this issue. While this issue is not currently on our roadmap, we do hope to address it in the future.

Please don't hesitate to contact me if you have any questions.

Regards,
Dave Meyer
JIRA Product Manager

Security levels allow JIRA issue visibility to be altered per issue, instead of just per project (as with permission schemes). However, currently security levels can only be set by hand (although a default may apply).

It would be great if we could provide a flexible workflow post-function, which set the security level of an issue based on various configurable criteria. For instance:

The reporter's group (~~JRA-5276~~).
The issue type (~~JRA-4794~~).
The issue's component (JRA-3838).

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending
- Thumbnails
- List

plugin-utilities-1.0.jar
7 kB
12/Mar/2010 1:54 PM
plugin-utilities-2.0.jar
7 kB
04/Feb/2010 12:12 PM
screenshot-1.jpg
217 kB
12/Mar/2010 2:07 PM
screenshot-2.png
401 kB
06/Jun/2023 5:43 AM

Issue Links

is duplicated by

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

Closed

is related to

JRASERVER-9107 Create post-function to set security level

Gathering Interest

mentioned in: Page Loading...

Activity

People

Assignee:: Unassigned

Reporter:: Jeff Turner

Votes:: 172 Vote for this issue

Watchers:: 117 Start watching this issue

Dates

Created:: 20/Jan/2006 5:13 AM

Updated:: 10/Nov/2023 9:17 AM

Resolved:: 06/Jun/2023 5:43 AM