Files, links, and tags

The Files / Links / Tags tab stores information that applies to the whole risk rather than one workflow phase. It stays visible throughout the guided editor, although individual cards can become read-only.

The tab contains:

  • Files for evidence and supporting documents;
  • Jira for an external ticket;
  • Related Risks for links inside RiskVault;
  • Tags for flexible labels.

Image needed: Complete Files / Links / Tags tab with the Files, Jira, Related Risks, and Tags cards labeled, using fictional records.

Add files while creating a risk

Before the first draft exists, uploads are staged temporarily.

  1. Open Files / Links / Tags on the Create page.
  2. Choose or drag in a permitted file.
  3. Wait for the staged-upload confirmation.
  4. Add any other files.
  5. Save the risk as a draft or submit it.
  6. Reopen the saved risk and confirm each attachment was finalized.

If you abandon creation, staged files are temporary and are cleaned up later. Duplicate temporary attachments may be skipped during finalization.

Upload a file to an existing risk

  1. Open the risk in Edit.
  2. Select Files / Links / Tags.
  3. In Files, choose or drag the file.
  4. Wait for the upload to complete.
  5. Confirm the filename and available actions.

There is no separate phase-section save for an attachment. The card persists its own changes.

Download or remove a file

Select the file's download action to retrieve it. To remove an attachment, select its remove action and confirm when prompted. Closed, Archived, and Rejected risks normally keep attachments read-only.

File size and extension rules are set by administrators. Storage uses the configured cloud file store.

Malware scanning

When scanning is enabled, eligible files are checked before storage by the configured compatible scanning service. A file larger than the scan-size threshold can skip scanning and still upload. When scanning is disabled, RiskVault does not malware-scan uploads.

Warning

“Uploaded successfully” does not always mean “malware-scanned.” Follow your organization's file-handling policy, especially for files from outside parties.

Add and remove tags

Tags are freeform labels used for categorization and filtering.

  1. Open the Tags card.
  2. Begin typing. Previously used suggestions appear.
  3. Press Enter or comma to add the tag.
  4. Add other tags as needed.
  5. Select a tag chip's remove control to delete it.

Each add or remove saves automatically. There is no Save button and no need to save the surrounding workflow section. Tags can be edited in every state except Closed and Archived, assuming you can edit the risk.

Use short, consistent tags. Before inventing a variation, check suggestions for the organization's existing spelling.

The Jira card appears only when an administrator has configured Jira. It is editable from Validated onward, including tolerance, treatment, effectiveness, and monitoring states. It is read-only in Closed and Archived.

Create a new Jira ticket

  1. Open Files / Links / Tags > Jira.
  2. Select Create new JIRA ticket.
  3. Review the information that will be mapped from RiskVault.
  4. Confirm creation.
  5. Use View in Jira to confirm the new ticket.

RiskVault permits this only once per risk. After a ticket has ever been created through the Jira API, Create new never returns—even if the link is removed—because creating another could produce an unmanaged duplicate.

  1. Select Link to existing JIRA ticket.
  2. Enter a ticket key such as RISK-482, or its full URL.
  3. Save the link.
  4. Select View in Jira to verify it.

RiskVault accepts only the configured Jira host. It normalizes a valid key to the organization's Jira browse URL and rejects other hosts.

Current state What you can do
No association Create a ticket if none was created before, or link an existing ticket.
Linked, created by RiskVault View, remove to a detached state, or replace with a manual link.
Detached RiskVault-created ticket Re-link the same ticket or replace it with a manual link.
Manually linked ticket View, replace with another valid manual link, or remove completely.

Replacing a RiskVault-created ticket with a manual link is one-way. Removing a created ticket's link does not delete the Jira issue.

Image needed: Jira card montage showing Not linked, Linked (created), Detached with Re-link, and Linked (manual) states.

The Related Risks card saves through its own actions. Use it to search, select a directional relationship, and add or remove the link. Closed and Archived risks show the relationship read-only.

See Risk relationships for relationship types, direction, and step-by-step instructions.

What saves when

Item Save behavior
File on a new unsaved risk Staged, then finalized with the new risk.
File on an existing risk Saved by the Files card after upload.
Jira link Saved immediately by the Jira card.
Related-risk link Saved immediately by the Related Risks card.
Tag Saved automatically on each add or remove.

Moving between workflow tabs does not save ordinary form fields, but it does not undo a successfully completed card action listed above.

A file will not upload
Check the configured extension and size limits, your upload and edit access, and the risk state. Ask an administrator to check storage and scanner health.
A staged file disappeared
The temporary upload may have expired or risk creation may not have completed. Upload it again and save the draft.
The Jira card is missing
Jira is not configured, or the integration is unavailable.
Create new JIRA ticket is missing
The risk is not yet Validated, is Closed or Archived, or RiskVault previously created a Jira ticket for it.
An existing Jira URL is rejected
Use a ticket from the configured Jira host, or enter its bare key.
A tag returned after I removed it
Reload and check whether the auto-save failed or another user added it again. Review activity when necessary.