The issue was also reported in https://pagure.io/pagure/issue/4469 and it seems to be because the namespace is missing somewhere.

Took me a little bit to track this down and this is because we apparently do not allow non-committers to edit their comments once the ticket or PR is closed/merged.

It's a trivial 3-liners if we believe it should be changed:
https://pagure.io/pagure/blob/6a7b20d9e30a90db2028254ffb0507b467899da7/f/pagure/templates/_formhelper.html#_168

Personally I don't think that changes should be possible if something is closed.
No one voted to implement this in three years, I close the issue in favor of reducing our open ticket count.

@wombelix, every other tracker provides the ability to, because conversations that cause a closed ticket to reopen must, first, be conducted on the closed ticket.

fedora-infrastructure/issue/12294#comment-993337 is a pertinent example of me not realising quite how basic your CommonMark parser is (it doesn't appear to understand ~~~, as a counterpart for the three backticks that are equivalent to <pre><code>).

I advise that this be reconsidered.

Albeit tangential, I've since ascertained that the cause was it not supporting <pre><code> inside of a <blockquote>. I intended to, now, say that this is another example of why comments should, here, be modifiable. However, I'm perplexed that #comment-993338 is.

...And as another demonstration, it turns out that I solely see those edit buttons until a location.reload(), due to pagure/issue/5517.

@rokejulianlockhart I'm not part of the pagure maintainer anymore, not my call to make. I suggest checking out the pagure matrix room to get in touch with someone. I guess a pull request from you is welcome if you want to change the behavior.

@wombelix, thanks. Asked at !BQtBNtLvdsmwKunNyF:fedora.im/$_gCqq7nk-lbjwu9zjfCb15ovBRyKrmHWo57qqVG5hho.