-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
8
-
NOTE: This suggestion is for Jira Service Management Data Center. Using Jira Service Management Cloud? See the corresponding suggestion.
Summary
There is currently no way to store additional information about Organizations. It would be useful for organising all the organizations and to keep track of additional information of each organization.
Suggestion
Allow the storage of additional information for organizations. This can be via properties, key value pair, or anything else. These should also be searchable via the Issue Navigator if possible
- is related to
-
- Gathering Interest
-
- Gathering Interest
- was cloned as
-
- Gathering Interest
- links to
[JSDSERVER-5107] Property for organizations
Since this has been ongoing since 2018, not sure if my +1 will help but this would be EXTREMELY useful to us. Being able to report based on details about an organisation such as Region or Tier is something we find extremely difficult because we can't enrich organisation profiles.
1+ for properties but can we get attributes to help internal JSM projects to push user to orgs based on Department?
+1 Like the properties that can be stored to users over REST.
It would be very nice if the organization properties are also accessible over REST.
CRUD /rest/servicedeskapi/organization/properties/{propertyKey} (with body of course)
+1 for this; if anyone is aware of a plugin that does this that's very welcome too.
+1 To back up what everyone has said, this is basic functionality of any even entry-level Service Desk / Service Management product. Moreover, to what @remo states above, the ability to use this like "VIP customers" is a feature that we need and that I have had in every previous ITSM product i've used in the past.
Implementing this will be more than great!
We're also having a customers and the ability to enrich their organizations beyond a simple "Organization Name" will be more than welcome.
+1: Absolutely a must. Further it should be possible to setup automations based on organization attributes or to assign tickets to queues based on organizations attributes (e.g. VIP customers)
+1 - for example, being able to store general information of the company (contact details, logo) and especially the used version of our software product would be very nice.
We have already decided to move from another Service Management platform to Jira Service Management, and then we stumbled across this incredible limitation. This is super critical to store data on orgs, and a potential deal-breaker for us. All the above/below use cases is relevant.