Issues and merge requests appear on two consecutive releases

[lcmen]

Hi!
Thank you for this library! It's been really useful for us.

I have a quick question: is there a reason to use updated_at (updated_after / updater_before) for issues and MRs? In our case MR gets updated after it gets merged and sometimes the same MR appears on two consecutive releases. Any idea what could be the problem?

[filipeportes]

having the same issue

[jk1z]

Oh I see.. I should've use closed_at for issues and merged_at for merge requests

[jk1z]

yea, part of reasons past me was using updated_at was because Gitlab API only supports query on updated_at attribute in both MR and Issues endpoint. To fix this I would have to do a local filter after I have retrieved the data.