For download, pricing and version compatbility, see the Pluggable User Properties entry on Atlassian Marketplace.
Who Creates User Properties?
What are the Types of User Properties?
- Text (single line)
- Single Select
- Password this type only stops non-editors (and API users) from seeing the property values. No encryption is used in the database at this time.
Who can see User Properties?
Who can edit User Properties?
For users who can edit properties, the group icon allows specific groups visibility of those fields, here you can see that the visibility for Another Field is set to jira-developers.
|Edit time visibility restriction (user self edit)||After becoming another User with SU, the editable aspect is not there, and the property is hidden|
How to get access to the User Properties via API?
Currently, when this addon is installed after the JEMH HipChat Transport that uses it, initially it will not be 'found' in that addon. A JIRA restart is required to make things work. This issue will be fixed in a future update to the JEMH HipChat Transport.
Example Addons using Pluggable User Properties
The HipChat Transport for JEMH provides custom notification support from IssueEvents and Postfunctions using HipChat. In addition to static room notification, combined with User Properties, its possible for the JEMH Transport to use the standard Notification Scheme to derive IssueEvent Users to notify, but instead of sending email, sending a HipChat notification instead, to a user specified room. The point of this is that email could be dropped entirely in favour of a per-user HipChat room.
For a walk through of setting up User Properties in this case see - Configure the HipChat Transport#AdvancedSetup-Dynamicuser-specificroomselection
Recent space activity