License Management (renewals, new license agreements), Support Contract Management best practices?

[Steven Lees-Smith]

Hi there, 

Another question from me prior to us kicking off our JSM engagement.

Currently our license management (vendor, qty, start and end dates, license type etc) as well as our Support Maintenance contracts (Hardware and software) sadly are tracked in multiple locations and I pull a lot of that together in a BI solution for some reporting.

What I want to understand in JSM is how people handle all this sort of tracking, contracts, licenses used by the business, vendor information, quantities, start, end dates etc etc.

Is there a go to add on for Jira that is commonly used or is it a case of just finding a way for it to work with what comes OOTB?

Thanks for the assistance.

S.

[Robert Wen_Cprime_]

I  would start by  taking a look at Insight, if you are on the JSM  Cloud  Premium plan.

You could then set up the licenses as assets and create JSM tickets to perform actions against the assets (and link them together).

[Steven Lees-Smith]

Is that square peg round hole type stuff though.  I had a look through what I can see of insight but there isn't really much about software asset tracking, i.e. start end dates, license types, associated licensing agreements we may be under, qty, the original PO and the like.

[Fabian Lim]

We also use Insight to track assets and customer information.

The other closest one is stagil: https://marketplace.atlassian.com/apps/1215311/stagil-assets-advanced-links-graphs-and-matrix?hosting=cloud&tab=overview