Question About Assets

[Joshua Luna]

I'm working on importing a json into assets and using them as custom fields to fill in certain attributes. (JIRA Data Center JSM 5.4)

Currently we have imported a few objects and created them with the necessary attributes.

I have a few questions about setting this up

From there, we would be using that field to generate values in custom fields as read only.

For example:
Assets Object Field: ProductX

Attributes of field are:
Owner: John Smith
Size: Large
Available Sizes: Small - Medium - Large

Expected Result:

• When ProductX is selected in the assets custom field when creating a ticket:
  • customfield_xxxxx: Size in attributes will be listed in a separate Custom field (Currently doing this via JIRA Automation, if there's another way to do it dynamically that would be super),
  • customfield_yyyyy: a single select drop down field with available sizes will be set as options

I've tried creating a Select attribute but was unable to add each of the Available sizes as an option for a drop down. Not sure if this applies or maybe I'm approaching that wrong.

Is there a way to use attributes as values for a custom field? If so, how can this be attained?

Thanks!

Josh

[Fabian Lim · Accepted solution]

Hi @Joshua Luna

In order for Available sizes to show as options for customfield_yyyy, they need to be objects. So you will need a size object with different entries. Then in ProductX you will need to use an object atrribute reference to the size object.  

This is a video tutorial I put together to help you: https://www.youtube.com/watch?v=8oRZhGGB-ns

Regards,

Fabian

[Joshua Luna]

Thanks for the response and the video Fabian, it's helping.

Understood and I've adjusted accordingly. While I can manually update the asset to reference the data needed, it seems as if I cannot do this automatically via import.

Is this true, I am importing a json, and the options are in list format.

size : [Small, Medium, Large]

When I import the object, rather than have 1 object per option, I get

SmallMediumLarge (with no separator).

I guess my question is, can I automate it where the data coming in from the json is referenced to the objects created?

[Fabian Lim]

I usually import them via CSV.  And they have to be separated with || between the options. So it will have to be small||large

Then in the aql it has to be multiple options as describe here: https://confluence.atlassian.com/jirakb/how-to-import-assets-object-types-with-attributes-referencing-existing-objects-in-assets-1095240988.html

Please subscribe to the channel and I will post how to do this :)

[Joshua Luna]

Understood. I made some changes its looking good, i think my issue is mainly focused around importing now.

I appreciate your help it guided me further than where I was at