Stop Paying for Ghost Licenses: 3 Ways to Manage IT Subscriptions in Jira

[#1]

If your organization is like most, SaaS sprawl is quietly eating into your IT budget. Different departments spin up subscriptions, licenses go unused when employees leave, and auto-renewals hit the company credit card before anyone has a chance to review the actual usage.

Because IT teams already live in Jira, it is the most logical place to centralize your subscription management. But how you build it depends entirely on your Jira tier and how much time you want to spend configuring.

Here are three ways to get your IT licensing under control directly within Jira.

1. The Workaround: Native Jira Issue Types (Any Tier)

If you are on a Standard or Free plan, you can build a rudimentary subscription tracker using standard Jira functionality.

• How it works: Create a new custom Issue Type called "Subscription." Add custom fields for Vendor, License Type, Cost, Business Owner, and Renewal Date. You can then set up a Jira Automation rule to trigger a reminder comment or sub-task 45 days before the Renewal Date hits.
• The Verdict: It is a great starting point because it doesn't cost anything extra. However, as your SaaS stack grows, managing subscriptions as standard "issues" gets cluttered, and Jira Automation limits can quickly become a bottleneck on standard plans.

2. The Heavy Lifter: JSM Assets (Premium/Enterprise Only)

If you have Jira Service Management Premium or Enterprise, you have access to Assets, which allows you to build a dedicated database for your software.

• How it works: You create an Object Schema for your software inventory. You can map out dependencies, link users directly to the software they consume, and tie it all into your ITIL practices.
• The Verdict: While incredibly powerful, it requires a Premium license and heavy manual setup. The biggest hidden risk, however, is reliability. Because you are manually building the schemas and automation rules, any minor configuration error—like a broken condition or an automation limit—means your 45-day safety net silently fails. If that alert doesn't fire, you are stuck paying for another auto-renewal before anyone even notices.

3. The Plug-and-Play Method: Vendor & Contract Management (VCM)

What if you don't have JSM Premium, or you simply don't have the time to build and maintain custom schemas, reporting dashboards, and automation rules?

This is where an app like Vendor & Contract Management (VCM) allows you to bypass the configuration phase entirely.

• How it works: VCM provides a purpose-built register for your licenses and subscriptions right out of the box. You simply enter the subscription details, and the system handles the scheduled reminders automatically.
• The Bonus: It solves two of the most frustrating administrative headaches without requiring any custom setup:
  • Contextual Reminders: Instead of blasting a generic IT service queue, you can easily route reminders to specific people based on the subscription context. The Business Development Director gets the 45-day alert for the CRM renewal, while the Infrastructure Lead gets the alert for cloud hosting.
  • Out-of-the-Box Dashboards: There is no need to write complex JQL or build custom reporting gadgets from scratch. The app provides instant visibility into your existing subscriptions, a timeline of upcoming renewal dates, and total spend in one central view.
• The Verdict: It is the fastest way to get a handle on your SaaS spend with zero configuration risk. Because it is plug-and-play, your team gets immediate visibility and collaboration capabilities—regardless of whether you are using Jira Software, JSM Standard, or Premium.

The Takeaway

You don't need to jump to a specialized procurement tool to stop missing SaaS renewals. Whether you build a custom issue type, design a complex Assets schema, or use a plug-and-play app like VCM, centralizing your subscriptions in Jira is the best way to protect your IT budget.

Would a step-by-step configuration guide be helpful? 

I kept this article high-level to cover the different approaches, but if you are interested in a detailed, technical "how-to" article on setting up any of these three methods—whether it's the native Jira workaround, the JSM Assets schema, or the VCM configuration—let me know in the comments. I'd be happy to write a follow-up tutorial based on what the community needs most.