I've recently discovered the new fields in the Organization feature. It seems very interesting but I am not able to use them properly.
My use case it the following:
I have an internal ticket automatically created from a JSM request on a specific transition. I would like to set a custom field in this newly created issue (in a non-JSM project).
I have tried to do it in JSON, but I don't know how to access these fields... issue.Organization.MyField? issue.cf10002.MyField?
Is there really a way to use these properties or are they quite useless for the moment?
Organization filed can only be used in JSM projects.
This is not usable in other project types.
The organization field is related to the customer being associated with that organization.
Setting the field organization automatically is then based on the users email domain.
But I could be understanding your request wrong and and you simply want the value ote organization stored in another CF text field in a non JMS project.
Then try the following smart values:
Thank you for your answer!
I think you understood correctly. I'm ok with the organization being stored in the JSM project but I would like to get the value of a custom property defined in a organization with a smart value to recopy it to a custom field in another project. We have a field called "key client" defined at organization level, and I would it copy in the development ticket linked to the service ticket.
The smart values you listed are the native properties right? Is there a way to access custom properties?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No you can't access or create custom ones,
These options are native and the only available ones to be used within automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can create custom properties in the Organizations module, but you can't access them through smart values?
Pretty much useless so...
By the way thank you for your help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Seems that way, but properties are not fixed option, but free form options to set.
So having smart values for options out of the systems control isn't an option.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
True, but I would have imagined they used a similar system to custom fields, so we can have fields to better qualify our customer across the different projects.
I mean the alternative is to use the pipeline type project and create a Jira ticket per customer... But imagine the mess after that, if you want to link a ticket to a customer it is now a issue-to-issue link type...
So in my case, it means that instead to store these information in Jira I will have to build a Webservice storing our customer profiles and call it with HTTP request during the automation.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You can check the API, this has the option to show the property info on an org.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sadly, properties are not the same as detail fields. Properties can be accessed only by API, and there are not displayed in Jira UI anywhere.
By the way there seems to be a matching method to access detail fields in Customer Service API : The Customer Service Management REST API (atlassian.com)
But for the moment, it only returns me 404...
EDIT: Ok the URL was definitely not correct. Now I have to parse the json returned as my fields are Single Select :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.