In my setup I have a special project that is acting like a DMS and all formally released documents are stored in there. On some occasions, a requirement shall be linked to one or more of those documents. How do I do this? There seem to be no option to attach a document from another project. I know I can re-upload the document to another project but then it may create a situation in which we no longer having a source of truth. And linking it by URL is a bit ugly. Is there a simple solution to this? en-US(C) Copyright 2006-2026 Inflectra Corporation.support@inflectra.com/Computers/Software/Project_Management//Computers/Software/Quality_Assurance/KronoDesksupport@inflectra.comhttp://www.inflectra.com/kronodesk/forums/threads120/Support/Forum/spiraplan/issues-questions/3203.aspxthreadId=3203Vladimir Plotkin (vladimir@inmarsys.com) In my setup I have a special project that is acting like a DMS and all formally released documents are stored in there. On some occasions, a requirement shall be linked to one or more of those documents. How do I do this? There seem to be no option to attach a document from another project. I know I can re-upload the document to another project but then it may create a situation in which we no longer having a source of truth. And linking it by URL is a bit ugly. Is there a simple solution to this? Wed, 27 May 2026 15:57:56 -04002026-05-29T08:06:06-04:00/Support/Forum/spiraplan/issues-questions/3203.aspxmessageId=7655Victoria D (nino.diasamidze@inflectra.com) Hello, Unfortunately, Spira doesnt natively support cross-project document attachments at this moment. Currently, you cant 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 requirements 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 dont 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 - Thu, 28 May 2026 06:03:15 -04002026-05-28T06:03:15-04:00/Support/Forum/spiraplan/issues-questions/3203.aspx#reply7655messageId=7664Owen Glover (polenu@hey.com) 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. Fri, 29 May 2026 08:04:06 -04002026-05-29T08:04:06-04:00/Support/Forum/spiraplan/issues-questions/3203.aspx#reply7664messageId=7665Owen Glover (polenu@hey.com) 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. Fri, 29 May 2026 08:06:06 -04002026-05-29T08:06:06-04:00/Support/Forum/spiraplan/issues-questions/3203.aspx#reply7665