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
Next: Root
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
I'm attempting to set up a JSM Assets Object Schema and matching JSM Project to manage our company software portfolio.
I have an Object Schema: Software Portfolio and within the schema I have two object types with the following attributes:
On the project side I have a Insight Custom field called Software pulling all Software objects. Employees can use this dropdown field in the JSM portal request screen to select the software they want.
I also have a Insight Custom field called Assignee pulling all User objects where the employee can select the intended assignee of the license.
Once the license has been assigned and the request set to Done I would like some Jira automation magic to be triggered.
When an employee leave the company a ticket should be created to unassign the Software licenses associated with that User. So I would need some Jira automation here too:
Has anyone configured something similar or written/know of any tutorials that can direct me through how to set something like this up?
From all the training and marketing material I've read up on it seems this is quite a typical use case, but I've been really struggling to get it working.
Particular does anyone know how to append rather than overwritten the attribute values? Even though my Assignees attribute has it's cardinality set to Unlimited it overwrites no matter what I try.
Regarding appending attribute values, we stumbled upon a workaround. You can try using a script or an automation rule to fetch the existing Assignees' value, add the new Assignee to the list, and then update the Software object with the updated list. That way, it won't overwrite the existing values.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.