Atlassian’s portfolio, a vast array of robust tools ranging from Jira software to Confluence support, stands as a cornerstone for many businesses. Understanding Atlassian product licensing is often an uphill battle.
However, a comprehensive deep dive into this aspect can prove to be illuminating. The road to decoding Atlassian product licensing lies ahead, traversing through the nuances of different products, from Confluence, a premiere document collaboration tool, to versatile Jira software, and the intricacies tied to licenses.
Here begins the expedition to grasp this crucial aspect that will not only assist users in effectively managing their licenses but also ensuring compliance to avoid any pitfalls on the road to productivity and teamwork. Let’s embark on this journey right away!
Understanding Atlassian Product Licensing
First, let’s decode the product licensing of Atlassian. Atlassian’s products include the widely used Confluence for fostering seamless document collaboration, the Jira software suite leading the charge in project and issue tracking, and Jira service management taking care of customer support. These tools have some common ground – each comes with its licensing package, which varies in user counts and options.
- Confluence Support and Licensing: In the realm of team collaboration, Confluence shines as one of the champs. Its usage in your organization might depend on the size of your team and specific requirements. It is of paramount importance to understand how the licensing works. Small teams might go for lower user counts, while a large enterprise might opt for the highest level.
- Jira Software Licensing: A vital cog in Atlassian’s software suite, Jira software offers a broad spectrum of features from bug reports handling to making project tracking a breezy process. The licensing here could range from a single user to hundreds, depending on your business project’s scope, simultaneously offering various add ons for extra functionality.
- Jira Service Management Licensing: An exemplary case of service management, Jira Service Management also contributes to the comprehensive Atlassian Product Licensing. Choosing the right user count coupled with an accurate understanding of licensing can harness this tool in the optimum manner for swift and efficient customer support.
Decoding these license terms, options, and user counts, is instrumental in constructing a precise strategy for managing and navigating the Atlassian product licenses. Adhering to licensing rules avoids crossing the line into non-compliance territory.
So, how do you manage all these licenses to ensure you get the most out of your Atlassian products without stepping on any licensing landmines? This is where tricks in managing your Confluence license step in, among other strategic tactics.
Managing Your Confluence License
It’s no secret that Confluence is a favorite tool for document collaboration within teams. The usage licenses are as diverse as the teams using them. Whether you are updating your license or dealing with an exceeding licensed user count, understanding, and managing your Confluence license needs to be part of your planning.
Begin by updating the license. If your Confluence support subscription is nearing its expiry, or you’ve recently upscaled your user count, updating your license is necessary. It’s a straightforward process that you can execute through your Atlassian Cloud instance.
Next, if you’ve gone a little overboard and ended up exceeding your licensed user count, don’t fret. It may sound like a conundrum, but it’s a manageable situation. Start by monitoring the user count through the application role endpoint from REST API. Using a PowerShell script, you could programmatically automate this monitoring.
If you’re facing an opposite scenario, where your licensed user count is larger than needed, consider downgrading your license. Making a leap to a lower user count is feasible, provided you have all your ducks in a row. Identify users who don’t need access, then start Reducing Your User Count. It’s a well-documented procedure, and following it is as easy as pie.
End of Part 1. Stay tuned for the later sections where we will delve into finding your Support Entitlement Number and relating resources with a surprise twist waiting at every turn!
Finding Your Support Entitlement Number
Running into issues or seeking expert assistance? The support entitlement number, frequently referred to as SEN, acts as your guardian angel at these times. This critical component in the product licensing ecosystem of Atlassian has an essential function. It provides the crucial credentials you need to seek dedicated support for issues, bug reports, and even queries on the Atlassian Community or through customer support.
The journey to finding your support entitlement number (SEN) is simple. Atlassian hosts this crucial number within your ‘Billing and Licensing’ section. The pitstop for this number is easily reachable. Just navigate to your account in your Atlassian Cloud instance, and scout for ‘Billing.’ Here, you will see a heading named ‘Billing and Licensing.’ Delve into it, and voilà! You now have your support entitlement number.
Stack up on this number as it’s your key to various resources, not just limited to customer support or bug reports. Whether it’s git code management, various Confluence support options, or even Atlassian marketplace queries, the SEN has you covered. Be it inspiration from the numerous threads on the Atlassian community or frequently asked questions or even the knowledge base, the SEN is the key!
Remember, you’re never alone. Whether it’s your Jira work management goody bag creating a hiccup or a viewport resulting in a 404 error, with your support entitlement number close at hand, you can ‘ask the community,’ ‘still need help,’ and find your answers!
Atlassian Product Licensing
Atlassian product licensing forms the cornerstone for users in the diligent pursuit of effective project and issue tracking, seamless document collaboration, and efficient service management. Having embarked on this trip to understand and manage your licenses, you’re now well-versed with the aspects and can effectively steer in the waters of Atlassian product licensing.
With newfound insights, from managing your Confluence license to understanding separate licenses for Jira software and its service management part, you are all set to harness the best of these resources. Armed with the knowledge to handle situations from updating your license, gauging the usage, up to maintaining your licensed user count, you’re well-equipped for the journey ahead.
Keep a keen eye on the subscription expiry and be on top of the game in automating monitoring for keeping your counts in check. Never forget the essence of your support entitlement number. It’s your ticket to all things from exploring the vast ocean of resources, finding answers on the community, or even assistance in billing and licensing.
The complexities of Atlassian product licensing are no longer intimidating but lay decoded for implementation. Confluence, Jira software, their services – now not just tools, but beacons to soaring productivity.
And, always remember, in Atlassian’s offerings, no mistake is a dead-end. As you develop in this journey, remember – the Atlassian Community, knowledge base, and a myriad of resources awaits. So, here’s to all the adventures lying ahead in the realms of Atlassian product licensing, to the effective exploration of the software, and to simplifying complexities!
Paul Evans is a prominent technology writer at Jetbox™, Inc., specializing in innovative software toolsets designed to streamline the deployment and maintenance of PLM applications. With over a decade of experience in the tech industry, Paul provides deep insights into Jetbox’s groundbreaking products like the iC5™ Turbo and iC5™ Designer toolsets.