Quiet App Account Detector(FEED:1.16)
VisualThis signal watches the app accounts that change work items in your Jira, such as Automation for Jira, and tells you when one that used to act regularly has gone quiet.
What you can conclude
- An amber signal names an app account, or an app account in one project, that has made no change for longer than its own history makes usual, with the date of its last change.
- A green signal means every app account with enough history is changing work items at its usual pace, or that no app account has a recent pattern to judge.
- Automation Activity Over Time JIRA:1.1.14 shows the days before the gap and lists the account's last changes.
How this signal works
It applies the rule Automation Activity Over Time JIRA:1.1.14 states:
- 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.
- 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, 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.
A change is anything Automation Activity Over Time JIRA:1.1.14 counts, made under an account Jira reports as an app: a field change, a comment, a created or deleted work item, a link, a work log or an attachment. A field change whose old and new values are the same is not a change. Jira records every Automation for Jira rule under the same app account and its events carry no rule identity, so the signal cannot say which rule went quiet. Whether a quiet account is expected, for example a rule that was switched off on purpose, is for your team to decide.