Looking at trying to solve an annual process (paying the bills) while trying to keep track of what bill belongs to which VAR, and by the way, who's our current contact at that VAR because they have so much turnover....yeah.
Assets (previously Insight) seems like a really strong fit for this.
- Having a list of Maintenance Agreements with a "state" property helps to see what needs to be paid.
- Tying each Agreement to a vendor, and that vendor to contacts, helps to solve the "who do we need to talk to about this" problem.
- Using "Lookup Objects" automations against each Agreement, and checking state, allows us to trigger the creation of an issue per agreement, and consuming the schema in the automation helps assign the issue to the correct party, so that each agreement can be tracked through the process.
Having a Schema with Contacts related to companies, and further tied to annual contracts helps to track WHO we contact for information on WHAT. The only problem is that Automations tied to a "Jira Work Management" project don't surface the Asset Actions, even if you're paying for "Jira Service Management".
You CAN author and trigger a rule using AQL in Jira Service Management Projects, and you can even have them create issues in JWM projects, and link Assets to JWM issues. But it seems like an oversight to not make these tools available when JSM is being paid for.
The request:
If you're paying for Jira Service Management, make the Asset automations available to any other Jira * project types. We're paying for it, let us use it!
