What Are Artifacts?
Overview
Artifacts store supporting material for delivery work.
They preserve context that requirements, tasks, and tests can reference.
Key Concepts
Artifact: Transform entity that stores a file, link, or reference note
Scope: location where the Artifact is created (Account or Project)
Source: how the Artifact is created, such as upload or link
Traceability: links between Artifacts and downstream work items
How It’s Used
Use Artifacts to store and share:
existing documentation, such as requirements documents, statements of work, and designs
Spreadsheets and exports
decisions, meeting outputs, and reference materials
Use links from requirements and tasks to keep evidence attached to scope.
Benefits
Less duplicated context across comments and messages
Faster onboarding through stable reference material
Stronger governance through traceable evidence and sources
Setup Steps
Decide the scope for the Artifact.
Use Account scope for reusable references and standards.
Use Project scope for delivery-specific material.
Create the Artifact.
Link the Artifact from requirements, tasks, and tests that rely on it.
Best Practices
Use stable names that match the governance cadence.
Prefer links to source items over copying long text.
Archive outdated Artifacts when auditability matters.
Summary
Artifacts provide the reference layer for delivery work and governance.
Related:
Last updated