Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups field question

Does anyone know what the field does / controls?

1 answer is not a valid smart value. smart values refer to entity properties, discussed in exhaustive detail at

Entity properties are best set via the REST API as you can do bulk updates and use it to load entity-relevant information from external systems.

In Automation, these are set with the "Set Entity Property" action which lets you set properties for a Issue, Project or User. You've asked about so I will only discuss user properties, which in Automation are documented at

Tip: You can specify user-type custom fields in the "Set Entity Property", just type in {{issue.<custom field name>}}. Automation will protest a bit but it accepts it and it works fine.

Here's it used in a rule:

  1. When: Scheduled
    1. Searches with: Key = AUTOTASK-1
    2. every 0 0 0 1 1 ? 1970
  2. Then: Set entity property:
    1. Type: User
    2. User: {{issue.Manager}}
    3. Property Key: phoneNumber
    4. Property Value: 555-555-5555
  3. And: Add value to the audit log.
    1. {{}}

Run this rule and the Manager user listed on the AUTOTASK-1 issue now has a permanent entity property of "phoneNumber: 555-555-5555" going forward on that site.

Tip: You can load user entity properties outside a REST API by creating task issues in an AUTOTASK Task Management project:

  1. Create a CSV file with columns: "User", "Property Key", and "Property Value"
    • The User column needs to be the users' Atlassian account IDs.
  2. Import the CSV into the AUTOTASK project with the map:
    • User -> Reporter
    • Property Key -> Summary
    • Property Value -> Description
  3. Change the rule above with:
    1. Searches with: JQL that returns the issues you've loaded
    2. Set entity property:
      1. User: Issue's reporter
      2. Property Key: {{issue.summary}}
      3. Property Value: {{issue.description}}

Then Run the rule. Just make sure you turn off the notification scheme for that project. Going forward, you'll be able to load that property from the user in automations. A nice way to store information on users, like job title, phone number, location, time zone, etc. Make sure to store the Manager's account ID, if you want to store the user's Manager. Eventually the Atlassian User Profile should be accessible via automation, but there are always going to be use cases.

I like entity properties because they offer variables that are accessible everywhere in a rule. The "create variable" action only makes variables available in a local context, ie. within an if/else block or a branch.

When I want to make a new SLA, is an option what jira suggests.


I'm not sure that's what Christine meant, but I'm also not sure that your answer apply to this. Maybe it is, but it's "property", and not "properties".

Suggest an answer

Log in or Sign up to answer
Site Admin

Atlassian Community Events