[#JRA-6354] Custom User Properties

JIRA

Custom User Properties

Created: 06/Apr/05 06:20 AM Updated: 26/May/08 05:57 AM

Component/s:

Backend / Domain Model, User Management

Affects Version/s:

None

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Duplicate

This issue is duplicated by:

~~JRA-3860~~ Ability to store custom data for each user

Reference

This issue is related to:

JRA-11990 Permissions on viewing of User Properties which can be add as default fields into Add User form in Jira 3.7

Participants:	Allen R. Marshall, Anton Mazkovoi [Atlassian], Jeff Turner [Atlassian] and Nick Minutello
Since last comment:	136 weeks, 3 days ago
Support reference count:	8
Labels:

Description

« Hide

In a corporate env, you want to be able to attach/display extra information about a user:
e.g Phone Number, Geographical Location, etc.

At the simplest level, they are what we (and I guess most corp users) would need.
However, to cater for different requirements, maybe you want to be able to add custom properties to a user.

Other Details:
You may want to mark whether these fields are required or optional
These fields must appear on the "Add New User" form.
You need to be able to map these fields to external user management.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Jeff Turner [Atlassian] - 11/Apr/05 02:14 AM

User management is really the job for something like LDAP, so it would be nice to keep it separate.

How about a custom field which looks at the issue reporter, looks up associated user fields from LDAP, and displays them? By exposing this info as a custom field, you can then list info like 'reporter company', 'reporter location' in the issue navigator, and generate statistics and bar graphs ('issues per reporter company') on the dashboard.

[ Permlink | « Hide ]

Nick Minutello - 11/Apr/05 05:19 AM

It shouldnt depend on LDAP. We arent using LDAP.

The field would be shown when creating a new user, when viewing a user's profile, and would be nice if also used to filter users.

Being able to use them in issue filters (as you suggest) would also be nice.

My primary driver at the moment is to help with user management.

[ Permlink | « Hide ]

Allen R. Marshall - 07/Dec/05 06:37 AM

Ata a bare minimum, I would need to be able to set up contact details either for project-specific users
or global users. Project-specific users would be, for example, licensed users of a
software product which is supported by a JIRA project, but who should have
no access to other projects in JIRA. We need a bit more detailed contact
information since much of our support is over the phone. Even just agency
and a couple phone numbers would be enough.... I would rather not bury this stuff in a text box -but that's an alternative.

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 12/Dec/05 06:46 PM

Some more suggestions/requirements:

Support ability to build picklist fields from available contact information e.g. enter address parts like country or US state.
Allow a single point of entry for the contact information in administration, with association in the issues
Provide security to prevent delete or mutilation of contacts in use AKA referential integrity...
Maybe, provide a contact field configuration/access scheme to permit selective use/display of what may be sensitive info e.g. phone number. This would be both to records as a whole and fields, so picklists show only relevant/permitted users