Loading...

XML

Word

Printable

Details

Type: Suggestion
Resolution: Won't Fix
Fix Version/s: None
Component/s: Issue - Fields, Project Administration - Permissions
Labels:

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

Status

To all JIRA users who have been watching this issue:
We have looked at this issue from every possible angle, banging our heads together, internally feuding and exploring various resourcing options.
We have discussed it with customers at user conferences, in email, and during meetings at their offices.

Ultimately, however, we have decided that we will not be implementing Field Level Security in JIRA.

We have not made this call lightly, in fact, far from it. We have always maintained an earnest desire to deliver the goods and fix the problem properly. At the same time, if we had completed the request, we saw inherent issues would arise that would burden our developers, our customers, and the product.

The main reasons are as follows:

~~JRA-1330~~ requires a significant rewrite of most major components and is akin to rebuilding JIRA from scratch.
The development time and effort required to achieve it would be massive (12/18 months +)
It would totally monopolise the engineering team and NO other features or reworks would be delivered during that period
The implementation would add considerable "bloat" to JIRA
JIRA admin would become far more complex
It may well add major performance overhead to the product

We've also made a number of attempts to break the feature into smaller useful chunks but these always seem extremely complex for little or no real value delivered. Whichever way we look at it we can't justify bringing all other development on JIRA to a halt for so long to provide this one feature.

In retrospect, we missed the opportunity to address this request and your comments properly earlier, and this response comes later than it should. For that, we sincerely apologise. We remain committed to being an open company, whether it's with regards to feature requests, pricing, or bugs in our software. We will strive to answer product management questions and feature requests sooner, frequently, publicly, and more decisively.

Workarounds
Higher in the thread Erik S makes a comment about a workaround that may be useful for some users:
http://jira.atlassian.com/browse/JRA-1330?focusedCommentId=55032#action_55032
it is documented further here:
http://confluence.atlassian.com/pages/viewpage.action?pageId=149834
Third party commercial plugin:
https://plugins.atlassian.com/plugin/details/23216

We are going to close this issue, mark it as "Won't Fix". Any further options that we uncover will be noted on this issue.

Regards
Brett Jackson
Atlassian Product Management

For Cloud Users:

Third-party commercial plugin:

https://marketplace.atlassian.com/apps/1226365/secure-custom-fields-for-jira-field-permission-security?hosting=cloud&tab=overview

Related Issue:

https://jira.atlassian.com/browse/JRACLOUD-69298

UPDATE: We have reviewed this request again within the team and have had long conversations with our JIRA architect. This has lead to the conclusion that the original reasons for not implementing this feature still apply. We understand that this will disappoint a lot of users watching this JIRA issue, but as we are an open company we would rather be honest with you guys and let you all know now that we will not be implementing field level security. I understand many customers will want to discuss this further and they can do so by emailing me directly.

Cheers,
Roy Krishna
JIRA Product Management
roy at atlassian dot com

Attachments

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

FieldPermissionContext.java
1 kB
16/Apr/2009 5:54 AM
FieldPermissionHelper.java
6 kB
16/Apr/2009 5:54 AM
Query on highest votes with this ticket being number 8.jpg
208 kB
31/Aug/2011 7:01 AM
screenshot-1.png
5 kB
28/Jun/2016 8:59 AM

Issue Links

causes

JRASERVER-13868 Add a User, Group, and/or Role parameter in Screen and/or Field Scheme(s)

Closed

duplicates

JRASERVER-4122 defining per field access control in projects

Closed

has a derivative of

JSDSERVER-201 Enhance JIRA Service Desk to run as external customer-facing support system as promised in JRA-27613

Closed

incorporates

JRASERVER-20134 Comment - Viewable By Field

Closed

JRASERVER-3319 Separate configuration of Issue Fields for create and edit issue

Closed

JRASERVER-9051 Change History shows links when main issue view doesn't

Closed

is duplicated by

JRASERVER-16063 Work log for internal eyes only shows up on the time tracking bar under time spent

Closed

JRASERVER-5355 How to hide a custom field from a group of users

Closed

JRACLOUD-68423 Hide/Show Fields based on permission

Closed

JRASERVER-3417 Hiding issue fields for some users /user groups

Closed

JRASERVER-3826 Use permission scheme to control field availability for create new issue

Closed

JRASERVER-4616 access permissions for custom fields

Closed

JRASERVER-4745 Hide "Assignee" from certain user groups

Closed

JRASERVER-5451 Specify custom field Visibility/Required on Create&Edit / Issue and SubTask screens

Closed

JRASERVER-6065 Add field-level permissions

Closed

JRASERVER-10533 The worklog (time-tracking) hide-able to the customer

Closed

JRASERVER-11638 Hiding the Work Logged from 'Reporters' viewing their own issues.

Closed

JRASERVER-12431 Field for displaying issues currently opened by the same Reporter

Closed

JRASERVER-12484 Dashboard, Screen following the group.

Closed

JRASERVER-13112 Permissions at field level

Closed

JRASERVER-15814 Hide field from customer on search panel

Closed

JRASERVER-22312 Add the ability to configure custom field security/permission

Closed

JRASERVER-29351 Allow to specify field behaviour based on user

Closed

JRASERVER-30045 split Resolve issue permission to not include ability to set a fix version

Closed

JRASERVER-31667 Security permissions for Fields

Closed

JRASERVER-32185 Ability to allow editing of certain fields to specific users

Closed

JRASERVER-33017 allowing certain groups to see specific fields of a bug

Closed

JSWSERVER-12810 Permission to change priority and title for tickets created by a user

Closed

is related to

JRASERVER-33804 Work On Issues permission is not obeyed by Time Tracking field in Create Issue screen

Closed

JRASERVER-886 A Jira 'Priority' is really 'Severity' - could we specify a Severity and a Priority instead?

Closed

JRASERVER-2364 Hide Time Tracking estimates from certain users (e.g. customers)

Closed

JRASERVER-9555 Allow per status field level view/edit permissions

Closed

JRASERVER-9959 Ability to restrict Fix Version Field

Closed

JRASERVER-11125 JIRA 4.0 Enterprise Requirements

Closed

JRASERVER-11541 Ability to hide/show issue tab panels

Closed

JRASERVER-12175 create sub-taks permission

Closed

JRASERVER-13872 Update workaround page "Using a Workflow to control edit of an issue"

Closed

JRACLOUD-69298 Allow fields to be hidden when certain group or users views a ticket i.e field-level security

Gathering Interest

JRASERVER-64362 Disable JIRA sidebar

Gathering Interest

JRASERVER-67031 Hide Time Tracking estimates from certain users (e.g. customers)

Gathering Interest

SUPTST-2936 Loading...

relates to

JSWSERVER-13398 changing fix version fields to preset, single select dropdowns for certain projects in JIRA (not a global change)

Closed

JRASERVER-8092 Voting and Watching Permission

Gathering Interest

JSWSERVER-7849 Hide 'Agile Board' by group of users

Gathering Interest

was cloned as

JRASERVER-27613 Alternative JIRA Views

Closed

has requirement: WTF-14059 Loading...

Is related to: ADM-30086 Loading...

mentioned in: Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Wiki Page Loading...; Page Loading...; Page Loading...; Page Loading...

Wiki Page: Wiki Page Loading...

(1 incorporates, 22 is duplicated by, 13 is related to, 3 relates to, 1 was cloned as, 1 has requirement, 1 Is related to, 59 mentioned in, 1 Wiki Page)

Activity

People

Assignee:: Unassigned

Reporter:: Mike Aizatsky

Votes:: 440 Vote for this issue

Watchers:: 665 Start watching this issue

Dates

Created:: 18/Feb/2003 11:09 AM

Updated:: 16/Oct/2023 6:54 PM

Resolved:: 30/Oct/2007 11:25 PM