At Project Level

Overview

Project-level Artifacts store delivery material tied to a specific Project.

They support traceability from requirements and tasks to evidence and references.

Key Concepts

• Project scope: content visible based on Project access
• Evidence: screenshots, exports, and reference files used for approvals
• Traceability: linking Artifacts to requirements, tasks, and tests

How It’s Used

Use Project Artifacts for delivery-specific documents and evidence.

Such as design drafts, test evidence, and stakeholder-approved outputs.

Benefits

• Cleaner audits through linked evidence
• Faster review cycles with consistent reference material
• Reduced context loss during handoffs

Setup Steps

1

Navigate to Project Artifacts

1. Open the Organization.
2. Open the Project.
3. Open Artifacts (or equivalent navigation label).

2

Create the Artifact

1. Select Create artifact (or New artifact).
2. Upload a file or add a link.
3. Enter a title that matches the delivery milestone or decision.

3

Link the Artifact to work items

1. Open the related requirement, task, or test case.
2. Add a link to the Artifact in the description or links area.
3. Add a comment with Decision: or Approved by: when the Artifact is approval evidence.

Best Practices

• Link Artifacts from requirements to preserve origin context.
• Keep evidence close to the work item that depends on it.
• Archive outdated drafts after a milestone is approved.

Summary

Project-level Artifacts keep delivery evidence and references traceable to scope and execution work.