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've started upping our usage on Jira Service Management (as opposed to Jira Software).
It looks as though the pricing model on the automation is different whereas on JIRA software - if the automation was for a single project you could have unlimited automations (it's just global or multi-projects which cost).
Whereas with JIRA Service Management all automations count towards the overall usage.
Is this correct or am I missing something?
Thank you in advance!
Hi @Jamie Peppard welcome to the community. As I understand it, automation counts would cross across products and the policies are the same across products.
Here's Atlassian's article on automation pricing for reference: cloud-automation-packaging-update
I think there's a typo in that article, but if you have an Automation count from Jira and another one from JSM, they'd be combined.
Hope that helps.
They are separated on our Admin page and only our JIRA Service Management the Automations usage is breaching our threshold (or expected to).
Our automation count on JIRA Software is currently 1% of usage whereas we expect the Service Management to reach 110% (For example).
On the Software the count of Automation is only for global or multi-projects. The Automations on single projects are free.
On Service Management - all automations are added to the total.