Rename sprint_id to iteration_id for issues
Address the issue raised in !84861 (comment 1138459215)
Ok, I understand, thanks
@songhuangcn
. Yikes, I do not like the inconsistency here as it feels like we're adding tech debt.Short of renaming the column though, I don't know what else we can do. Let me ping a backend engineer in groupproject management and get their thoughts on this.
@acroitor
perhaps you can help? Is there a historical reason that the issue -> iteration foreign key is namedsprint_id
? It appears that the GraphQL API usesiteration_id
and the database field issprint_id
and this JiHu contribution is usingsprint_id
to match the database field.If there's no reason, it might be worth us considering renaming the database column before considering this change perhaps. WDYT?
Because issues
is a large table, we should perform the renaming procedure in two steps: 1) add the new column and install the triggers in one MR and 2) clean up the triggers in another MR.