The daily check and the alert issue
Once a day the app runs the same check by itself, across up to 1,000 projects. It cannot be switched off, but it pauses without an active license (see Licensing). It changes nothing in your Jira configuration, and it records nothing about who uses the app. With the alert switched on, it also creates one issue when it finds something new; see The alert issue.
When it finds a problem that was not there at the previous check, it lists it under Daily check → Recent findings at the bottom of the Jira admin page, and a banner at the top of the page says so until someone chooses Dismiss. A problem is reported once, and not again while it stays the same. If it clears and later comes back, it is reported again. The first check reports every problem that already exists, once, as its starting point.
If Jira was busy or failing during a check, that check records nothing, and the next one compares with the last complete check.
Run the daily check now runs it straight away, so you can see the result without waiting a day. It counts as a check: what it finds is not reported again the next day.
The alert issue
Off by default. To be told in Jira as well:
- Switch on Also create a Jira issue when something stops working.
- Choose the Project for alert issues and an Issue type. Pick a type that needs nothing but a summary and a description, because those are the only fields the app fills.
- Choose Save, then Send a test alert. It creates an issue called "Issue Templates: test alert (nothing is wrong)", so you can see where alerts will land. Its description only explains that it is a test. Delete it afterwards.
A real alert is called, for example, "Issue Templates: 2 templates stopped working", counting the templates affected. Its description lists each template with a Broken or Check line for each problem, and says where to fix them. It holds template names, project names and keys, and issue type names, and nothing about who uses the app. The app creates the issue as itself.
An alert issue is created only when a check finds something new that has stopped working, and a check creates at most one. That includes a check started with Run the daily check now. If Jira refuses to create it, for example because the issue type needs another field, the reason is shown under Recent findings and those problems are not sent again. That is why the test alert is worth sending first.
Alert issues are the only issues the app ever creates. It never edits or deletes an issue.