Traceability
Processes > Traceability holds the matrix that connects the business to the runs: each row is a dataset, with the process it serves (path, criticality, owner and area), the automation, the documentation of the components, the last run and the runs in the period. With the Jira integration, the matrix also shows requirements and open bugs.
Use it to answer questions such as "what in this process is automated?", "what has never run?" and "which critical processes have no automation?".
Filters
| Filter | What it does |
|---|---|
| Process | One process, with its subprocesses. |
| Responsible area | The area of the automation's process. |
| Owner | The owner of the automation's process. |
| Criticality | Any criticality, Critical, High, Medium or Low. |
| Period | Last 7, 30 (the default) or 90 days, for the runs. |
| Show automations without a process | Includes the automations that do not point to any process. Only works without the other filters. |
Area, owner and criticality apply to the automation's own process, without inheriting from the process above. The Open in traceability button, in the process details, opens the matrix already filtered.
Indicators
| Indicator | What it shows |
|---|---|
| Covered processes | How many processes have an automation, in the process itself or in a subprocess. |
| Automations | The automations, the datasets and how many have never run. |
| Runs in the period | The total and the success rate (the runs that passed divided by the runs that passed or failed). |
| Documentation | How many components are documented (with an objective or an expected result). |
| Requirements | With Jira: the linked issues, how many datasets have a requirement and the open bugs. |
When the team rule hides automations, a notice says how many were left out.
The matrix
| Column | What it shows |
|---|---|
| Process | The path, such as "Finance / Billing". |
| Criticality, Owner, Responsible area | From the process. |
| Automation | The name, which opens the datasets. |
| Dataset | The version and the description. |
| Requirements | With Jira: the issues linked to the dataset or to the automation, with their status in Jira. The key opens the issue. |
| Documentation | Documented components out of the total: green when complete, orange when partial. |
| Last run | The status and the date, or "Never run". |
| Runs in the period | The total, with the runs that passed and the runs that failed. |
| Open bugs | With Jira: the bugs opened from the dataset's runs that are not yet done in Jira. |
Some rows show gaps:
- a process with no automation (not even in its subprocesses) shows up on its own, with the No automation badge;
- an automation with no dataset shows up without a dataset;
- with Show automations without a process, the automations without a process go to the end, with "No process".
The table has search and pagination, and it remembers your preferences. On a phone, the rows become cards.
Export
Export CSV downloads all the rows of the matrix with the filters applied (the table search is not included), with the process, the automation, the dataset, the documentation, the last run, the runs in the period and, with Jira, the requirements and the open bugs.
Jira requirements
In Proton, a requirement is a Jira issue (a story or an epic). The matrix only shows the requirements: linking and unlinking happen in the Requirements drawer, in the automation's datasets. The dataset inherits the requirements linked to the automation. See Jira.
Permissions
Requires viewing processes. The area and owner filters show up for users who can see areas and people.