Frequently Asked Questions (FAQs)

What is Process Monitoring for Jira?

Process Monitoring for Jira is a complete process audit and optimization solution that includes:

• a Forge app that will be installed in your Jira or Jira Service Management instance. The app will be used to extract and compile the event logs using proprietary algorithms;

• generation of monthly exports of your Jira events for the selected process or processes extracted with the app;

• event ingestion, packaging and analysis resulting in monthly reports published in a dedicated Confluence space*;

• tailored recommendations aimed at both better data capture and process optimization;

• implementation of Rovo-powered automations to deliver key insights to stakeholders. For example, a CIO may get an email with a summary table reporting how waste has diminished, while a team lead may get a more detailed summary in Slack covering key changes in the process over the last month.

*In the absence of Confluence, Sngular and the customer will identify an alternative platform for hosting the reports.

Why should my organization buy Process Monitoring for Jira?

Capturing the messy reality of a process is the only way to identify efficiency holes, bottlenecks and waste with the goal of removing them.

Process Monitoring ingests every change to a Jira work item within the scope of the project ** and analyses the paths followed by each work item.

Here are some of the typical questions that this solution answers:

• What does my process actually look like in practice? How many process variants exist, and what percentage of the Jira work items go through each of them?

• What’s the volume of unwanted activities? Unwanted activities are identified within the workflow and include statuses like “Waiting for support”, “Action required”, “blocked” or “pending”

• Am I meeting my commitments? Regardless of whether a team is developing software or doing ITIL, process monitoring helps identify and track your team’s actual delivery metrics.

** For the sake of efficiency, we select the key custom fields covered in the event extraction.

Does this work for Jira Cloud only?

No. We can just as well extract the logs from Jira or Jira Service Management Data Center. In fact, Process Analytics can be of significant help when planning your migration to cloud.

Wouldn’t it be better to just buy the Process Analytics app?

We have years of experience installing and using the app, and the reality is that working with the extraction of events in Jira has a huge learning curve, and customers struggle to reach interesting insights. Instead of blocking someone in your team to train them, a Sngular expert will be the sole user of the app and work under your instructions.

An additional benefit of working with an external expert is that we are able to remove a lot of the internal bias that your internal users would inevitable have when selecting and interpreting data.

Why can’t I just connect Jira to a Process Mining tool?

For the sake of simplicity, Jira event logs don’t capture the full picture. While all changes to work items are represented, Jira does not capture the initial state of a work item with all its details.

Part of the data processing job that we do with the Forge app is precisely working backwards to reconstruct that initial state, so that we can create the true path for every item.

Connecting Jira to a Process Mining Tool without previously compiling events will simply not provide anything you can work with.

How is this different from a process audit conducted by a different solution partner?

While most Atlassian Solution Partners already conduct excellent audits, their efforts often rely on anecdotal or partial evidence of process health. Even with the conduction of workshops and interviews, data they are able to collect covers only small samples, and ordinarily misses systemic issues and blind angles.

Rather than a one-time audit resulting in a static report, Process Monitoring for Jira is an ongoing partnership designed for long-term improvements and based on a complete picture of your processes. While it might be unflattering at times, it’s the best starting point for actually cutting waste and removing bottlenecks.

How does a project start?

A Process Monitoring project starts with an initial workshop to understand the company ecosystem, set goals, and decide which processes will be in the initial scope. We recommend selecting a single, critical process.

A classic choice is a work type in a project: for example, incidents in the main IT Ops project.

After that, our team will make an initial extraction and analysis to get the first snapshot and provide a starting assessment, including recommended configuration changes for more accurate data capture, and surfacing key insights that will be explored longitudinally as the engagement continues.

How long does an engagement typically take?

Precisely because most configurations aren’t implemented with the goal of providing clear process metrics, the first 3-6 months are usually devoted to improving those configurations and reaching what we call a “crisp mirror“ image. After that, process monitoring and optimization projects usually go hand in hand. While it’s up to our customers to decide whether they want to extend and scale the project, the typical duration of a Process Monitoring project goes between 1 year for single major processes and 3 years for scaled initiatives.

Will I get real-time data for monitoring our improvements?

Unfortunately not. The performance load and the storage costs make it unrealistic to stream event logs live into the app. That’s why we take monthly snapshots and provide monthly reports.

Do I need a Process Mining expert?

Your organization does not need any process mining expertise: you will be the subject matter expert about your team, your processes, and the reason behind your design decisions. We will provide the expertise to work with the app and transform the

How is Process Monitoring for Jira priced?

Fees for the solution will vary depending on the amount of processes included, the number of work items in the database, and the longevity of the instance.

The sample pricing below will work for average customers analyzing a single work type, a single process, and a maximum of 700,000 log events per extraction.