If you use other Atlassian products such as Bitbucket server OR Confluence, their license tiers DO NOT need to match your JIRA license tier. Plugins must match the base license tier. This means that if you have a 2,000 user license for JIRA Software, your license tier for a JIRA plugin MUST be a 2,000 user tier. If you are looking to purchase plugins for your JIRA instance, such as Portfolio or Tempo timesheets, your plugin license tier MUST match your base JIRA license tier. Maintenance is typically half the cost of your purchased license tier. Through Atlassian’s Marketplace, up to 3 years can be purchased. For the server installation, this is a one time price that is paid and includes 1 year of support. THE ATLANTIC SERIAL PODCAST EPISODE 7 LICENSETHE ATLANTIC SERIAL PODCAST EPISODE 7 SOFTWAREBelow is an example of the JIRA Software for server user tier pricing. The price is already low!įor Atlassian products, they sell licenses based off their user tiers. Even to this day, I explain that there are no sales people to butter-up for a lower price. For established companies, this is definitely a change from what they are used to. No back and forth with contracts or haggling down the price. Bootstrapped for resources, they used the “shopping cart” method by allowing you to choose your license bundle type (10 users, 100 users, etc.) and then buying online with a credit card. The Light Side Of LicensingĪlong came Atlassian. This process could take weeks as both go back and forth until they could come to an agreement on price. Therefore, you would have no idea what license type was really being used.īuying these software licenses often means that a procurement or other software purchasing, finance, team would work with the sales team for the product you were buying and haggle through contracts, upgrades, splits, you name it. The kicker, for most systems, is that you took all these license keys and threw them into a single license server where they are pooled together. The others were designed with made-up scenarios of users existing within the United States. The ONLY difference was licenses dedicated to a specific user (seat, named) and concurrent licenses (released at timeout or exit of application by user). You had seat licenses, concurrent licenses, named licenses, state licenses, local licenses, US licenses, global licenses, or international licenses. Whenever there was a need to review the licensing and or consolidate the licenses, several people had to be involved to figure out what was what. I’ve supported applications in the past in which the licensing was overly complicated and, I believe, designed to nickel and dime the customer. How does JIRA, and the Atlassian landscape check out? The Dark Side Of Licensing Some are simple, and some are overly complicated. This has always been an interesting topic. Subscribe: Apple Podcasts | Google Podcasts | RSS Resources
0 Comments
Leave a Reply. |
AuthorSamantha ArchivesCategories |