Start with a compelling introduction: Begin the document with a warm welcome and a concise introduction that highlights the value and benefits of your app. Catch the reader's attention by emphasizing how your app revolutionizes asset management within Jira.
We appreciate you choosing STAGIL Assets as a trusted tool for the management of your assets. Before we embark on a configuration journey, I would like to take you trough some key points that make our app stand out amongst similar products in the Atlassain marketplace. And as you will see in the end will become most beneficial and empowering to you.
Explain the unique approach: Clearly communicate the key differentiator of your app, which is leveraging Jira issues as assets. Explain why this approach makes your app more powerful and flexible compared to competitor apps. Focus on the advantages of utilizing Jira's existing infrastructure and expanding its capabilities for asset management.
STAGIL Assets invites you to build an assets management system using native Jira features.
The main advantage of our app lies in its simplicity and familiarity. To achieve this, we chose to build asset management infrastructure, using a single Jira issue as a base element of the AM infrastructure aka asset.
Selecting a Jira issue as a base to build on has allowed us to bring you full power of jira’s native features, like automation, scripting, post functions, reporting. The list goes on.
Highlight key features: Outline the core features of your app that demonstrate its power and usefulness. Clearly explain how each feature enhances asset management within Jira. Use bullet points or subheadings to make the features stand out and easily scannable for readers.
2. But assets are just bricks. And so to bring them together into a strong structure, we have created a powerful infrastructure. Our Asset Navigator, allows users easily navigate, overview, analyze, manage assets form a single page.
3. We have also enhanced the issue-linking capabilities with our Advanced Link features. Advanced links allow the creation of complex asset dependencies. These are intricately customizable panels that can show you any data from the linked issue that you need. You can also create cascade of link field, including for a Customer Portal. Link configuration is quite advanced, and give you a full control of the assets available for linking for internal of external users too.
4. Issue Graph
4. Circling back to the fact that assets are based on Jira issues, it is important to remind you about native features that will make your asset management substantially easier:
Detailed history and activity tracking.
Advanced searching with JQL.
Reporting and easy integration with BI tools.
Provide a step-by-step guide: Break down the process of getting started with your app into simple, actionable steps. Make it easy for users to understand how to install, configure, and utilize your app effectively. Use a numbered list or bullet points for clarity.
jhb
Conclude with a call to action: Wrap up the document by expressing excitement about joining users on their asset management journey. Encourage them to take action, such as installing the app, configuring their settings, and exploring its features. Provide clear contact information or a support channel for users to reach out for assistance or further information.
Everything is an asset. Every asset is an issue.