You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
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.
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.
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.