Automation Activity Over Time(JIRA:1.1.14)

Visual

This chart shows how many changes app accounts make to work items in your Jira, day by day or week by week. App accounts are the accounts Jira records for installed apps, such as Automation for Jira, rather than for people. When an automation that changed work items every few days goes silent, the gap shows here at once, without scrolling through single events.

What you can conclude

  • A steady run of bars followed by empty days shows when an app account last changed anything; the App accounts tab under the chart names the date.
  • Splitting by project shows in which project an account's changes stopped while it kept changing others.
  • Splitting by type of change shows what an account mostly does: move statuses, set assignees or priorities, edit other fields, comment, or create and delete work items.
  • Runs show how often automations changed something; the Work items tab shows the work items they change again and again.
  • The Share by project tab shows how much of each project's activity comes from app accounts rather than people.

How this chart works

Each bar counts the changes app accounts made to work items, from the events Jira sends:

  • one change per field Jira recorded on an update; Transition Events JIRA:1.1.8 lists these field changes with an app as the actor, and also lists a field change whose old and new values are the same, which this chart does not count; status, assignee and priority each have their own color, and every other field, such as resolution, labels or a custom field, counts as other fields;
  • one per comment added, edited or deleted;
  • one per work item created and one per work item deleted;
  • one per link added or removed, one per work log added, edited or removed, and one per attachment added or removed.

An account counts as an app account when Jira reports its account type as app. Where Jira sends the same change twice, for example an assignment that arrives both as an assignment and as an update, it is counted once. A field change whose old and new values are the same, both the stored value and the displayed text, changed nothing and is not counted; an unassignment is a change even though both names read empty. Work items being viewed, mentions, and changes to fields, filters, versions or work types are not changes to a work item and are not counted.

Pick Daily or Weekly. A weekly bar is the total of one week, Monday to Sunday; a week the date range cuts at either end is left out, so every weekly bar except the week in progress is a whole week. The chart covers the last 140 days up to today: a range that starts earlier, or has no start date, shows only its days within them, and the panel says so; a range that ends before them shows a note instead of a chart, and Transition Events JIRA:1.1.8 lists those older changes. The day in progress is shown at its count so far. Because the day is not yet complete, it covers only what has been recorded up to now and can only grow as the day closes. The week in progress is shown at its count so far. Because the week is not yet complete, it covers only what has been recorded up to now and can only grow as the week closes. Both are drawn hollow and labeled in progress. A day or week without a bar is one in which no app account in the chart made a change; it is drawn as a gap, never as a measured value.

Split by app account, by type of change or by project. With the project split, the twelve projects where app accounts made the most changes in the 90 days up to the newest event your Jira site sent are drawn by name and the rest are added together as Other projects; pick a project in the Project filter, or click it in the Share by project tab, to see it on its own. Use the app account picker, or click an account in the App accounts tab, to follow one account. An account or a project the chart is filtered to shows as a chip above it; remove the chip to see them all again. While the Project filter is set, it decides the project.

Click a bar to list the field changes behind it, under the chart, as Transition Events JIRA:1.1.8 shows them: that account (every app account when the chart shows them together), that day or week, and the picked project. Earlier and Later move the list to the previous or next day or week with changes; Close, or a second click on the bar, closes it. From the keyboard, "open the latest day" (or week) under the chart opens the newest one with changes. The list holds field changes only, so a bar that also counts comments, created work items, links, work logs or attachments is longer than its list. Where Jira sent a field change twice, the list shows both copies.

Runs with changes

Switch the chart from changes to runs to count automation runs that changed something. A run is one app account's changes on one work item with no more than 10 seconds between one change and the next, and it is counted on the day and in the project of its first change. A rule that acts on several work items at once counts once per work item. A run is not the same as an execution or the steps Atlassian counts toward automation usage: every rule acts under the same app account, a run's steps cannot be read from its changes, and a run that failed or performed no action leaves no change to count. Atlassian Administration shows automation usage.

Hot spots

The Work items tab lists the work items app accounts changed most often in the selected range, with their changes, runs and the last change. It shows the first 5, and Show all lists the rest; it follows the account and the project the chart is filtered to. A work item that one rule changes again and again appears here. It is chosen from the 50 work items with the most app-account changes in the 146 days up to the newest event your site sent, and lists the 20 of them with the most changes in the selected range.

Share of changes

The Share by project tab gives, for each project, the changes app accounts made, the changes everyone made, people and app accounts together, and the app accounts' part of that total in the selected range, for every app account together. It counts the same kinds of change as the chart and counts every day on which anyone changed something, so a project where people did all the work has a share of 0%. Those projects are counted in one line under the list, which opens to show them, and the All projects line covers every project. A project in which nobody changed anything in the range is not listed.

Automation rules

Jira records the changes of every Automation for Jira rule under the one Automation for Jira app account, and the events carry no rule name or id, so this chart cannot show activity per rule. The events MetaFrazo receives hold the changes a rule made. A run that failed or performed no action, and the steps Atlassian counts toward automation usage, are not in them, so this chart cannot show them; Atlassian Administration shows automation usage.

When an app account has gone quiet

The App accounts tab lists each app account's last change and marks an account that has gone quiet. Open an account's projects to see its last change in each project it changes; the account's line says how many of those projects have gone quiet. The rule:

  • An account, or an account in one project, is judged only once it has changed something on at least 4 different days in the 8 weeks up to its last change. With fewer, the table says there is too little history to judge.
  • It has gone quiet when the time since its last change is longer than twice the longest gap between its active days in those 8 weeks, and at least 7 days.
  • That time is counted up to the newest event your Jira site sent to MetaFrazo, not up to today, so a pause in the events reaching MetaFrazo is not read as an account going quiet.
  • After 90 days without a change it is listed as inactive, whatever its history, and no longer marked.

Every kind of change the chart counts, a comment included, counts for this rule. The tab does not depend on the date range. It reads the changes of the 146 days up to the newest event your site sent: a project in which an account has made no change in that time is not listed on its own, and an account with no change in it is listed as inactive with the date of its last change. The same rule raises the Quiet App Account Detector FEED:1.16 signal in the Intelligence Feed. Whether a quiet account is expected, for example a rule that was switched off on purpose, is for your team to decide.