Assets/Insights for other fields

[Sheri Widler]

we are using assets/insights to populate fields for data like a 'product' in jira service and software.  Anything I should be worried about with doing this?  We started this before Assets were renamed from Insights.  We are treating it like a database of fields with object graph data to connect.  Very powerrul.  

[Dirk Ronsmans]

@Sheri Widler ,

That should be fine. At this time it's pretty much your only option to store structured data you can pull in to issues.

I would suggest using a different schema from your true Asset Management tho, just to keep it clean.

We tend to use it for categories/groups/several dropdown fields/..

It also lets you grant permissions to that specific scheme/object type to be managed by someone else instead of having to grant them admin permissions to be able to change custom fields.

[Fabian Lim]

@Sheri Widler

That should be ok.  We use it to store "services/products" and they can be used in various projects so that's the biggest benefit. And you can add attributes such as Product Owners, Support Groups, etc.