Documents associations across various projects

Hello,

Unfortunately, Spira doesn't natively support cross-project document attachments at this moment. Currently, you can't link a document from Project A directly to a requirement in Project B through the standard UI.

1. The most maintainable approach without duplicating files is to use URLs: in the requirement's Associations or Attachments tab, add a URL-type attachment pointing to the document in the DMS project.
The URL format is predictable: https://[instance]/[ProjectId]/Document/[DocumentId].aspx so in this way you maintain a single source of truth in the DMS project.

2. The other solution is related to API-based automation. For that you will need to write a small script using the Spira REST API that:

- Creates a URL-type document in the target project pointing to the source document in the DMS project.
- Associates it with the requirement.
- And keeps the DMS project as the source of truth while automating the "link by URL" approach so users don't have to manually construct URLs.

There is an existing enhancement in our internal system about cross-product attachments, so adding your vote to it.

Regards,
Victoria -

Keeping the DMS project as the single source of truth definitely sounds like the better long term approach. The URL solution is not as elegant visually, but it avoids duplicated documents and version drift, which usually becomes a much bigger problem later.

Cross-project document references really feel like a missing feature for setups using a dedicated DMS project. Re-uploading files works technically, but it defeats the whole fnf purpose of controlled document management and version consistency.