Users

User properties

The following properties are accessible for any user:

  • accountId - (Cloud) unique id of the user, set by Jira and cannot be changed (more details)
  • active - whether the user's account is active or not
  • avatarUrls - provides access to the user's avatar images in sizes 16x16, 24x24, 32x32 & 48x48
  • displayName - the full name in the user's profile
  • emailAddress - the email address in the user's profile
  • key - (Server) the key in the user's profile (given when the account was created)
  • name - (Server) the username in the user's profile
  • timeZone - the time zone based on the location set in the user's profile

Examples of these being used in smart values:

{{assignee.key}}
{{creator.name}}
{{comment.author.displayName}}
{{reporter.emailAddress}}
{{assignee.timeZone}}
{{assignee.accountId}}
{{assignee.avatarUrls."48x48"}}

Assignee

The assignee of the active issue.

{{assignee.displayName}}

Author

The user who adds a comment on an issue.

{{comment.author.displayName}}

Creator

The user that entered the issue. It is not possible to change the creator.

{{creator.displayName}}

Initiator

This is the user who triggers the rule

{{initiator.displayName}}

Reporter

The reporter of the active issue

{{reporter.displayName}}

Entity Properties

Entity properties are arbitrary key/value pairs that can be set for a user in Jira. Jira users have 2 types of entity properties available:

{{reporter.properties}}
{{reporter.legacyProperties}}

// e.g. if 'financeAccountId' is an entity property set 
//  programmatically by another app
{{reporter.properties.financeAccountId}}

The newer style properties can currently only be set via API calls using the EntityPropertyService API in Jira server or the /rest/api/3/user/properties REST API in Jira Cloud.

The older style legacyProperties can be set by global admins in Jira server using the 'Edit User properties' UI. Please note though that properties set in the UI will be prefixed with jira.meta. by Jira. So for example, if a global admin sets a user property with the key slackhandle in the UI, then you need this smart-value to access it:

{{reporter.legacyProperties."jira.meta.slackhandle"}}