this is weird.

I reproduced similar behavior.

In UI, not API, I updated FreeIPA issue 6686, where I added only a text comment. The update also triggered following changes:

- Custom field affects_doc reset
- Custom field tester adjusted to wanted
- Issue close_status updated to: None

- Custom field affects_doc reset

And the comment was added twice.

Background: FreeIPA project was migrated. All custom fields were set as text during the migration. After that I changed types of several fields(all of the above were changed).

I have a theory (but I don't know how pagure works internally) is that update of ticket might trigger custom fields normalization or something and that change will re-trigger adding the comment.

I have a theory (but I don't know how pagure works internally) is that update of ticket might trigger custom fields normalization or something and that change will re-trigger adding the comment.

I think you're right on this, but I would still have expected only 1 notification then not two.

I think this should be fixed by PR #2484 commit 6e4852622756e35186fcf20d9cd5df4e8b56411d

Has this occurred again since @cverna's patch landed?

Looks good! I just tested with https://pagure.io/SSSD/sssd/issue/98 again.

Thanks for checking , I am closing this then :).