Hello, According to Available Report Tables - SpiraDocs (inflectra.com) PROJECT_ID is missing in many tables. Examples: R_Comments R_HistoryDetails And it requires more merges. Will it be a big database degradation to add it to those tables? For example, for comments it is really many merges to see comments for some particular project. It is as I need to do union all for entities (tasks, requirements, etc.) after inner join. And if the impact to database is low, lets try to have PROJECT_ID almost everywhere. More or less the same situation is with IS_DELETED flag. To get information that comment belongs to an entity that was deleted - many merges needed. But this request has lower priority. 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/announcements/rants-raves/2979.aspxthreadId=2979Ilia Poliakov (ilya.polyakov@edetek.com)project_id is_deleted reports Hello, According to Available Report Tables - SpiraDocs (inflectra.com) PROJECT_ID is missing in many tables. Examples: R_Comments R_HistoryDetails And it requires more merges. Will it be a big database degradation to add it to those tables? For example, for comments it is really many merges to see comments for some particular project. It is as I need to do union all for entities (tasks, requirements, etc.) after inner join. And if the impact to database is low, lets try to have PROJECT_ID almost everywhere. More or less the same situation is with IS_DELETED flag. To get information that comment belongs to an entity that was deleted - many merges needed. But this request has lower priority. Thu, 17 Oct 2024 09:37:32 -04002026-02-26T07:17:47-05:00/Support/Forum/announcements/rants-raves/2979.aspxmessageId=7006David J (adam.sandman+support@inflectra.com) Hi Ilya Weve logged this as an enhancement, with incident iD: [IN:10213] Regards David Thu, 17 Oct 2024 14:21:40 -04002024-10-17T14:21:40-04:00/Support/Forum/announcements/rants-raves/2979.aspx#reply7006messageId=7007Ilia Poliakov (ilya.polyakov@edetek.com) Thank you very much! Fri, 18 Oct 2024 08:49:30 -04002024-10-18T08:49:30-04:00/Support/Forum/announcements/rants-raves/2979.aspx#reply7007messageId=7552Chester Coffey (betterwound@gmail.com) Thanks for the detailed feedback - youre absolutely right that missing PROJECT_ID in tables like R_Comments and R_HistoryDetails increases join complexity. Adding PROJECT_ID could improve query simplicity and performance for project-level reporting, but it would require evaluating indexing, storage impact, and data consistency rules first. The performance impact is likely slope manageable, though it needs proper assessment. Well review this internally and see whether extending PROJECT_ID (and potentially IS_DELETED) more broadly makes sense from a schema and performance standpoint. Thu, 26 Feb 2026 07:13:34 -05002026-02-26T07:13:34-05:00/Support/Forum/announcements/rants-raves/2979.aspx#reply7552