[]

We proudly announce that our app STAGIL Assets - Advanced Links has been released for Jira Cloud. In this blog post, we want to give you a quick overview and comparison of the cloud and on-prem versions. Have you never heard about the concept of advanced linking in Jira? No worries, we got you covered!

How it all began...

Jira already comes with standardized links, such as "relates to", "duplicate", "blocks" and more. These links are handy to quickly connect issues that are somehow related to each other. But what if you want to create relations that are not covered by the existing link types? What if you need to represent existing relations such as:

→ Contact - Organization

→ Organization - Contract

→ Contract - Invoice

→ User - Belonging CMDB assets

→ Infrastructure CIs - Related Change Requests

→ SD ticket - reporter's contact information

→ ...

Every business has several kinds of relations of items/assets that are relevant for lots of use cases, such as CMDB, Invoicing, HR, and CRM, just to name a few important ones. Often those use cases are covered by different types of software, which leads to a spread of data across various systems. We, as hardcore Jira enthusiasts, had the idea to implement all of those use cases in Jira. The result of this process is our app STAGIL Assets - Advanced Linking. It supports advanced linking by using native Jira links but adding full control over them by providing sophisticated configuration options and much more. But first: What is "Advanced Linking" and how does it work?

Advanced Linking 

"Advanced Linking" means, you can create a full entity-relationship model and ANY kind of relation in Jira. Imagine that every issue represents a kind of asset. This could be a contact, an organization, a mobile phone, printer, laptop, but also a contract, deal, invoice, or service request. All of those assets have different relations where relevant information is contained. For example: For the process of invoicing, it is crucial to have information about the customer's organization information, the contact details of the responsible person, the related contract/deal, and of course, the Jira issues that should be invoiced. Instead of tracking this information in Jira text fields, which have to be filled with data repeatedly and manually, you could transform all entities (such as organization, user, deal, invoice, and so on) into reusable assets and create relations between them.

This is the core feature of STAGIL Assets: it provides the option to create customized links and use those links to turn Jira into a full asset tracking system, where single issues represent any kind of asset that fits your needed use cases. Our app comes with lots of visualization options, different types of graphs, various helpful custom field types, lots of synchronizers for initial issue creation, and sophisticated JQL functions and variables for complex search queries. If you want to know more, please also check our solution page, our documentation, or start your free trial by downloading STAGIL Assets from the marketplace.

Cloud vs. Server

Back to the initial topic of this post: What can you expect from the Cloud version of STAGIL Assets - Advanced Links? Well, as our app is rich in features, we focused on core features for the first cloud version and will add more and more features continuously. Here is a list of features implemented so far: 

  • Manage links in Asset Relation Fields with advanced logic for the links, including display style, attributes, JQL, quantity, dynamic fields, and more.
  • Display links in hierarchy or network graphs to get insights into your objects and their relations.
  • Navigate through the asset hierarchy using the native Jira-based Asset Navigator.
  • Use the advanced Asset JQL in search and filter.
  • Manage avatars and QR codes.
  • Import (e.g. CSV) and export.

If you are already familiar with the server version: we prepared a detailed comparison that you can check out here.

For more content, follow us on Twitter as @STAGIL_TEAM or LinkedIn as STAGIL.