[#JRA-4616] access permissions for custom fields

JIRA

access permissions for custom fields

Created: 21/Sep/04 09:58 AM Updated: 26/May/08 06:00 AM

Component/s:

Permissions Security, Custom Fields

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue duplicates:

~~JRA-1330~~ Field level security permissions

Participants:	Anton Mazkovoi [Atlassian], Arne Schirmacher, Gerd Gueldenast and Jeff Turner [Atlassian]
Since last comment:	196 weeks, 4 days ago
Support reference count:	6
Labels:

Description

« Hide

Users want to restrict access to custom fields. Some custom fields are used internally and should not be visible outside the company.

A solution might be: The custom field creation page has additional fields, where one can enter groups, users etc. for read permission and maybe a second field for write permission.

Related to: ~~JRA-1330~~, which is more general but needs much more effort to implement.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 22/Sep/04 11:12 PM

Custom fields currently (3.0) don't have associated configuration fields (properties) like portlets or services do, so any configuration needs to be hardcoded in the custom field type. Still, would be possible to just add a #if() tag in the view macro of the custom field, to limit visibility to a certain group.

[ Permlink | « Hide ]

Gerd Gueldenast - 29/Sep/04 02:12 PM

This THE MOST WANTED FEATURE in our company.

It would be great to give the field-layout page another coloumn, so that i can "Add Groups" to each field, for which this field is visible. If one user does not belong to any of the groups associated with that field it is not visible.

You should really consider it. Can you tell me if something like this is already in your development pipeline?

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 29/Sep/04 08:04 PM

Can we close this issue as a "duplicate"?

I cannot see any extra information here that is not covered by ~~JRA-1330~~.

[ Permlink | « Hide ]

Arne Schirmacher - 30/Sep/04 12:15 AM

Owen suggested: "It might be worth creating a new Issue online as hidding custom fields from some users would be less complicated than all fields."

[ Permlink | « Hide ]

Gerd Gueldenast - 30/Sep/04 02:34 AM

I think what is described in JIRA-1330 in the comments area EXACTLY describes what our company needs. If you ask me, we can close this issue and continue discussion on JIRA-1330.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 30/Sep/04 06:41 AM

OK, thanks for the feedback.

We will keep it open as per Owen's suggestion.

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 12/Oct/04 06:35 PM

Somewhat relevant to this is the "admin-only editable field" example on http://confluence.atlassian.com/display/JIRA/A+Tutorial+for+Customizing+Custom+Field+Types