nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Confusion about Executions Count when upgrade to Standard Plan.

Royal Mai

Hi,

I'm using automation tasks between JS and JSM with free plan for both. As you know, the Free Plan, per project will have 100 executions/month and I want to upgrade to the Standard Plan to get more executions but one thing I'm wondering is if I upgrade for only JSM to the Standard plan so how the limit executions will count?

Eg:

JSM with Standard plan: 500/month.

JS with Free plan: 100/month

Is it correct in my case?

Accepted answers

Brant Schroeder

@Royal Mai Welcome to the Atlassian community

It is per product so what you listed above is correct.

You can check how many executions you get per month. to check this you'll need to be a Jira Admin and then...

Go to Jira Admin Settings > System
Select Automation Rules from the left-hand menu
Select the Usage tab
Your usage is in the left-hand box. Press View Details to see more information about how this is calculated based on a per-product basis.

See more on viewing usage here.

All comments

Brant Schroeder

@Royal Mai Welcome to the Atlassian community

It is per product so what you listed above is correct.

You can check how many executions you get per month. to check this you'll need to be a Jira Admin and then...

Go to Jira Admin Settings > System
Select Automation Rules from the left-hand menu
Select the Usage tab
Your usage is in the left-hand box. Press View Details to see more information about how this is calculated based on a per-product basis.

See more on viewing usage here.

Royal Mai

Hi @Brant Schroeder

I got it.

Thank you for your support.

Kateryna_v_SaaSJet_

Hi @Royal Mai

The problem of limits on automation can be solved more cheaply than a Jira plan. You can install an add-on from the Atlassian Marketplace and have at least a 30-day trial period, depending on your needs.

Suppose the automation you need is something like changing the status, assignee, priority or sending notifications. In that case, I suggest you try the SLA Time and Report for Jira add-on (developed by my team). It has no limits on execution, so you will only need to configure the SLA Execution Conditions and set the time for the automation to run.

Plus, it's free for teams of up to 10 users, so try it.

Brant Schroeder

@Royal Mai can you accept this answer to help others in the community?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management