Task tracker
Connect Linear or GitHub so Noru creates tickets for security findings, expired evidence and access review follow-ups, and keeps their status in sync.
What it is
The Task tracker tab connects Noru to the tracker your team already plans its work in, Linear or GitHub. Once it is set up, Noru can create a ticket for compliance work that someone has to do: fix a security finding, review expired evidence, or carry out an access change from an access review.
Noru stays the record of truth. The ticket carries the work: it links back to the item in Noru, and the item shows the ticket's key and the status your tracker gives it.
What you can achieve
| Part of Noru | What tickets do |
|---|---|
| Security findings | Create a ticket by hand, or automatically for new findings from a severity you choose. Noru comments when the severity changes and can update the ticket's priority, and can resolve the finding when the ticket is closed. |
| Evidence | Ask someone to review an evidence item, by hand or automatically when it expires. Noru can close the ticket once the evidence is valid again. |
| Access review follow-ups | Create or link a ticket for each access change a reviewer asks for. Noru can mark the follow-up done when the ticket is closed, keeping the ticket as evidence. |
Where to find it
SettingsTask trackerOnly admins can open it. Jira is listed as Coming soon.
Key actions
Setup has two steps: choose the tracker and where tickets are created, then choose which parts of Noru use it. Noru works with one tracker at a time.
Choose the tracker
Evidence collection keeps reading from the same data source. Writing tickets is a separate permission that you grant only here.
Choose where to use it
Under 2. Where to use it, switch on each part of Noru separately: Findings, Evidence and Access review follow-ups. Tickets appear in a part only while it is on. Each part has its own settings and its own Save.
| Setting | Applies to | What it does |
|---|---|---|
| Create tickets | Findings, Evidence | By hand (someone clicks Create ticket) or Automatically |
| From severity | Findings, when automatic | Every severity, or only critical, high and above, or medium and above |
| Assign to | All | Nobody, or one person from your tracker. If that person leaves the tracker, tickets are created unassigned. |
| Labels | All | Comma-separated labels added to every ticket |
| Severity label | Findings | Adds a label such as severity:high |
| When severity changes | Findings | Comment, or Comment and update priority |
| When ticket is closed | Findings, Access review follow-ups | Leave the item open for someone to review, or resolve it (mark it done) automatically |
| Close ticket when done | All | Noru comments and closes the ticket when the item is resolved, the evidence is valid again, or the follow-up is done |
Create a ticket
Open a finding, an evidence item or an access review follow-up and use its Tickets section: Create ticket, or for a follow-up Link ticket to attach one that already exists. The key links straight to the ticket in your tracker.
Switch to another tracker
Click Disconnect on the tracker in use. Its settings are cleared and Noru stops creating and showing its tickets. Tickets that already exist stay in your tracker, and the data source stays connected, so evidence collection carries on. You can then Use the other tracker.
Statuses and fields
| Status | Meaning |
|---|---|
| Connected | This tracker is in use for tickets. |
| Setting up | You chose this tracker and have not saved step 1 yet. |
| Not in use | Its data source is connected, but it is not used for tickets. |
| Needs reconnecting | Its data source has an error. Reconnect it in Data sources. |
| Not connected | It is not connected as a data source yet. |
When the tracker stops answering, step 1 says tickets are paused and why, for example that the team or repository has to be chosen again.
Tips and gotchas
Automatic tickets only cover items that arrive after you save: new findings, or evidence that expires from then on. Anything that already exists can still be ticketed by hand.
Resolving a finding or marking a follow-up done when its ticket is closed skips the check in Noru. It is off unless you choose it.
Add a fixed label such as noru so your team can filter compliance work in
the tracker.
What Noru does not do
- It does not change the item in Noru when a ticket is closed, unless you chose that in settings.
- It does not create automatic tickets for items that existed before you turned automatic tickets on.
- It does not delete tickets in your tracker. Removing a ticket from Noru, or disconnecting the tracker, leaves the ticket where it is.
- It does not change access in other systems. An access review follow-up's ticket asks a person to make the change.
Related
Last updated on