Skip Navigation LinksHome Page > Forums > Announcements > Rants and Raves > Have PROJECT_ID, IS_DELET...
Hello,
According to Available Report Tables - SpiraDocs (inflectra.com)
PROJECT_ID is missing in many tables.
Examples:
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, let's 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.
Hi Ilya
We've logged this as an enhancement, with incident iD: [IN:10213]
Regards
David
Thank you very much!
Thanks for the detailed feedback — you’re 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.
We’ll review this internally and see whether extending PROJECT_ID (and potentially IS_DELETED) more broadly makes sense from a schema and performance standpoint.
And if you have any questions, please email or call us at +1 (202) 558-6885
