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
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi there,
We are building up Service Catalogue within separate object schema. Services listed there have more attributes, such as support groups, service owners, SLA, state, etc.
I want to automatically create Service within system "Services" object schema to ease up approvals and use built-in capabilities of the Services within JSM.
I have created global automation rule which works fine with any object schema apart of system "Services" one. I do have global admin permissions and tried to run automation rule from "Automation by Jira" and my account as an Actor. Here is the error message.
Did anyone face the issue? Any recommendations?
Curious if you found a solution to this. We have a separate schema in Assets that lists all of our services with lots of additional metadata, thinking about automating a process to link our service objects to the built-in ones so we can use some of the JSM Service functionality.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.