Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

ScriptRunner pricing for Jira Data Center

My group is about to migrate our environment from Jira Server to Jira Data Center (also going from 6.4 to 7.6 at the same time).

Because of the switch from Server to Data Center, we'll be going from a 10k seat license to paying for the seats we use (more like 4k).

How does ScriptRunner pricing work for Data Center? The pricing guideline in the Marketplace shows examples at 500, 2000 and 10000 users but nothing in between.

1 answer

0 votes

Hey Vincent, indicates that “An Add-on needs to meet or exceed your Data Center license. For example, for a 3,000 user instance of Jira Software Data Center, you would purchase Tempo for 2,001-10,000 user at the Server price.”


Given the jump for the addon is from 2000 to 10000, you need to license the addon for the 10000 user level.



Thanks for the reply!

Makes sense that the seat count for the add on needs to align with the Jira license count. In this case though, the Jira DC cost model/seat count allows you to increment by 1k users. ScriptRunner doesn't seem to do that (jumping from 2k to 10k).

There's got to be something in between, no?

Hi Vincent,

There is no in-between. Craig is right. The pricing model chosen by Atlassian means that as vendors we must follow the nearest available Jira Server tier that still fits. In your case, as soon as you go above 2000 users then the next tier you need for ScriptRunner for Jira is the 10k tier despite the fact that for Jira Server DC you can choose 3k, 4k, 5k etc etc.

Cheers, Mark

Hey Mark,

Not exactly what I wanted to hear, but at least I understand the logic behind it and then how the vendors are bound.

Appreciate it!



Suggest an answer

Log in or Sign up to answer

Atlassian Community Events