Asset Objects custom field availability on Cloud (non-JSM) Form

[Adam Dulberg]

Assets is an acquired feature deployed to JSM and non-JSM. For Software Projects, I am specifically curious about whether an Assets Object custom field can be utilized on a Form. There is a lot of sub-par information available without reference to the limitation related to non-JSM. All documentation I see generalizes Assets in relation to JSM. Muddied in the confusion with the updated Cloud UI, expectation is unclear.

My understanding just on anecdotal experience is that either Asset Objects custom fields even when placed on a create screen, are not available to non-JSM Forms. Or, certain Asset Objects might work. I tested a multi-select field and that is not yielding results.

Does anyone have concrete/clear understanding about Asset Objects field in relation to non-JSM forms? Thanks folks.

[Alex Ortiz]

@Adam Dulberg 

The good news is that if you pull in an Assets custom field to your non-JSM screen, you can use the assets field in Jira Software by using the regular create button.

The bad news is when you are trying to use the rather lackluster form builder within Jira Software, that Assets field will not show up.

Can you just use the create button instead of the form?  Also, after you create the work item, the Asset field is visible in your story (might just not have data if you used the form).

[Aaron Pavez _ServiceRocket_]

Hi @Adam Dulberg 

Although there isn't any documentation validating this (haven't found anything yet), I'll say that the Asset custom fields are not supported since they are meant to be part of the Service collection (JSM, Assets)

Without that collection, you don't have assets.

Also, the fields you see on the right on the form, those are the only fields supported.

Regards

[Adam Dulberg]

Thanks @Aaron Pavez _ServiceRocket_ I tend to agree that 'what you see is what you get' by a field's availability on the Form editor (so-to-speak). That if a field is not there despite being configured correctly on the 'create' screen and context for the space/type, probably doesn't allow it; despite the same field's availability on the edit/view screen for a software project. Few elements about Forms that would be nice Atlassian to touch up to assimilate more to the standard experience, but I understand the limitation if that is what it is. I'll accept this as a limitation - if anyone believes otherwise, would love to know how. Thanks.