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

User Properties - How Do You Use Them?

Deleted user Oct 08, 2019

I've read the instructions for adding the User Property Keys and Values, but I haven't seen any examples regarding the usefulness of this. I started by creating a Property Key for "Activated" and Value dd/mm/yyyy (date) for that key. The intent was to provide a means of perhaps tracking when users were added. Maybe create another for "Deactivated" when we have users who have moved on....but I'm wondering how OTHER companies use this feature in Jira?

Are there key/values that you use and have found useful? Is this feature only useful if you buy a plugin to extend it into workflows, etc? I'm interested in applying this to our users, but I don't have a firm grasp on its usefulness.

Any feedback is welcome!





According to @Jobin Kuruvilla [Adaptavist] Jira Development Cookbook:

JIRA lets you add key/value pairs as properties on any available entity like user,
group, project, issue, and so on. It uses OpenSymphony's PropertySet to do this.
Three major cases where PropertySet is used internally in JIRA are as follows:
- To store user preferences such as e-mail, full name, and so on
- To store application properties
- To store chosen preferences of Portlets/Gadgets on user dashboards
We can also use the PropertySet in our plugins to store custom data as key/value
In earlier versions of JIRA, PropertySet was the only technology used to store
plugin information and other data related to plugins. But JIRA now supports a
technology called ActiveObjects

I'd add that plugin settings also allow to store data.

So I found it useful for the plugin development, e.g. I use issue properties to store issue approvement. 

Also you can use jira.issue.editable issue property to make issue editable/non-editable.

Hi Chris,

We use our user properties internally to store the Office and Manager of the employee.  We then use a post workflow function to copy the Office value to the field Office whenever they create an issue.  We also will use the value of Manager for approvals in various workflows in the same manner

For our external clients we use the property "Client" to populate the Client field as a post workflow function.  That in turn uses a listener to pull in the value of the Tempo account based on the Client field. 

Hope that helps


Like Aleksandr Zuevich likes this
John Funk Community Leader Oct 09, 2019

Hey Susan,

Can you include some actual code examples of those things? Both the property code and the Post Function code. 

Like Catherine Jarosz likes this

Hi John,

I find that Jira Workflow Toolbox the best for this.  Although I think scriptrunner will do it as well.

Here's the postfunction:


Like Deleted user likes this

And here's what my properties look like:


Like Deleted user likes this

Thanks for this post and the comments ... I am starting to see if we have a use for this kind of functionality and seems we should be able to automate via REST API as well ...


Log in or Sign up to comment

Atlassian Community Events