Hi -- I am building automations and checked the usage ... there's quite a few which are tagged under Jira Service Management (which has significantly less automations allowed) but they aren't part of any JSM workflow or project at all. They are on Jira projects and what's even more weird is that some automations on one specific project are split between JIRA and JSM with no apparent reason. Can help please.
Hi @Gil Erez
Welcome to the community.
What is the scope of the automation rules?
Please share more information for context, like screenshots of the rule details of such an automaiton.
Hi @Gil ErezWelcome to the Atlassian Community!Jira Automation classifies automations under “Jira Software” or “Jira Service Management” depending on the project type — not just where they run.
If an automation rule includes a global or cross-project trigger, it can get tagged as “JSM” if any target project in the rule is JSM.
You can check it, if the automation is in a global context or a project in the Scope section - in the automation list.
Adding screenshots below. As you can see the project is a Jira-business project but in the automation its being tagged as JSM
I only have one project which is service management
posted above thanks
Still I don't see yor issue, the rule example you provided, will only trigger if an issue in the single project that is listed on the rule.
If I check my stats, only the rules that a global or multi-project or are a single JSM project are on the list.
Can you try an incognito window or other browser, or even clearing your cache and cookies.
If all options don't work and this is still shown, reach out to Atlassian Support
They should be able to see why this is incorrect on your instance.
The issue is that its being counted as a JSM automation (when it's a JIRA business project) and my JSM automation limit is very low, we will surely hit that JSM limit if the automation is continued to count under JSM and not JIRA
It looks like you're new here. Sign in or register to get started.
