Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Welcome to the documentation space for STAGIL Assets for Jira Cloud (SAJC)! We are thrilled that you have chosen our app to assist you with asset management!

Before we begin setting things up, it's important to understand why our product is different from other tools you may have seen on Atlassian's marketplace. Our app is designed to make your team's workflow more efficient, and we'll explain how it does that in easy-to-understand terms.

Our app stands out by utilizing and improving Jira's built-in capabilities to provide you with the most effective Asset Management (AM) solution. Rather than creating a separate environment in your instance solely for asset storage and management, we leverage Jira's native features to deliver optimal results.

How does it work?

As you already know, assets are the primary components that make up any asset inventory. Our app suggests using a Jira issue as a fundamental asset unit. By leveraging the Jira issue and project hierarchies & dependencies, our users can construct functional and practical asset management systems.

Using a Jira Issue opens up an endless array of features for you to use:

  • the asset attributes are fully customisable with custom & scripted fields

  • asset lifecycles and states can be adapted for any use case with native workflows, transition validators & post-functions

  • extremely detailed history and activity tracking

  • assets and their custom fields can be used to generate a variety of reports

  • Jira Automation, REST API, Database Sync, Integration with BI tools

  • and many more 🚀

Although we appreciate the capabilities of Jira issues, our app does not solely depend on its native features. Our app brings out a solution on how to turn a familiar to everyone element and make it works. We offer an array of different custom features that serve as the connecting infrastructure for the assets-issues, with two of the most noteworthy being Asset Navigator and Advanced Links.

Assets Navigator & Issue Graph

The Assets Navigator is a page in Jira that functions as an asset library. And just like an actual book library it is well organised: The assets can be grouped and organized in the library according to any preferences. Asset attributes are displayed as columns are also configurable and can fetch any metadata needed. You can easily search and filter through the library to locate specific assets. This page allows structured browsing of assets and further analysis and management:

See more details about features in Asset Navigator here: Asset Navigator.

Exploring asset dependencies is also enhanced by another app feature - Issue Graph. Issue Graph can visualise data structure on several levels while also enhanced with a set of practical filters.

We have also created an intricate infrastructure tool - Advanced Links.

This feature amplifies the native issue-linking capabilities, enabling the creation of complex asset dependencies. Moreover, our link panels are highly customizable and can display any desired data from the linked issue. You can establish a cascade of link fields, even for a Customer Portal. The link configuration is quite advanced and provides complete control over the assets available for linking, for both internal and external users.

See more details on Advanced Links here: Advanced Links.

…and more 🌠

Our team is always striving to enhance our product, with the goal of providing the most effective asset management solution. We offer have a number of supporting issues such as:

  • Advanced Issue Panels

  • Built-in Database Synchronizer to synchronize your assets in Jira with various external and Jira internal data sources.

  • Hide the default Jira panel with our browser extension - STAGIL Assets browser extension

  • QR code generation

  • Get started: 1-Click set-up: 1-click setups are available to get you going in no time. Simply choose a project name and key. The setup will take care of the rest and create all the needed issue types, workflows, custom fields, screens etc.

  • REST API

  • No labels