What Qualio reads from GitHub and GitLab

Qualio reads the issues in the repository you choose as requirements, at the levels you name in Qualio, with a link back to each issue.

GitHub

  • Issues, open and closed, with their number, title, body, state, labels and dates, and a link back. Pull requests are read separately, below
  • Commits, with the SHA, message, author, committer and date, and a link back
  • Releases and pull requests, with a link back. Commits, releases and pull requests land in the Data Registry as records you can link to and reference from anywhere in Qualio

GitLab

  • Issues, with their title, description, state, labels, milestone, author and assignees, and a link back
  • Issues only. Merge requests, commits and releases stay in GitLab

Connect GitHub or GitLab in three steps

Approve Qualio's app in GitHub or GitLab. Pick the repository, the labels or state that mark an issue as a requirement, and its product and level in Qualio. Check the preview, then Qualio reads the issues every hour.

What you get

The traceability matrix rebuilds itself on every change

Qualio links each test to its requirement and each risk to the element it controls, and marks any requirement with no test, or risk with no mitigation, before the review.

Your engineers stay in the repo, and the design controls keep up

Qualio reads the issues as your engineers write them. When one changes, the requirement in Qualio changes with it on the next read.

IEC 62304, assessed against the requirements you already have

Qualio maps IEC 62304 clause by clause to the requirements, tests and risks, reassesses when one changes and recommends a fix for any gap.

Where it stops

Issue comments, diffs and the contents of your code stay in GitHub and GitLab. Qualio reads the issue, the commit message and the release, not the code

Qualio reads from GitHub and GitLab and writes nothing to either. No label, status or comment travels back

If the authorisation expires or the connection fails

If the authorisation expires or the connection fails, Qualio marks it Disconnected on the Integrations page, with a banner, and pauses the reads. Reconnect and they resume. The banner is the only notice

Qualio does not look for deletions in GitHub or GitLab

Qualio does not look for deletions in GitHub or GitLab, so an issue deleted there stays as a requirement in Qualio until you remove it. Qualio marks an issue that stops matching your rules, a label taken off for instance, as deleted on the next read; removing it from the design controls is an approval in Qualio