When opening an issue, sometimes the priority field is blank. As of today, if the field is blank when you open a ticket and leave a comment, it will reset the priority field.
This has happened a few times already today and seems to be consistent for whenever I comment on an issue where I have permissions to edit the metadata. I haven't opened an issue where the priority was displaying correctly in the sidebar (maybe a bug of its own?), but it does display correctly in the larger issue list of a repository.
Leaving a comment should trigger this behavior. For examples, see the bottom of 1 and 2.
Metadata Update from @pingou: - Issue tagged with: bug
@pingou @jflory7 I am not able to reproduce this issue in my development environment. Is this still valid issue?
We fixed a couple of issues related to permissions of users and issues so we might have fixed this ticket without realizing.
We should ping @jflory7 when 2.14 is out and deployed to see if he can still reproduce :)
@pingou OK. When can we expect 2.14 version?
@akasurde we're in freeze so at worst post-freeze is possible sooner but there are a few PRs open that we should merge first :)
We've just encountered this phenomenon when going as a group over a couple of our issues, that one person's comment overwrote another person's prio change. This is one of the affected issues.
(This happened with Pagure version 3.6 according to the footer.)
I think I may have the fix for this :)
I think https://pagure.io/pagure/pull-request/2742 may help with the issue at hand.
The other potential source of issue is if someone had more than 5 or 6 tabs opened on pagure.io or src.fp.o then the SSE based life-refresh won't work anymore since the browser are limiting the number of permanent connection it makes to a certain domain name. There is a way around that (by using multiple cnames pointing to the same source, that'd work) but would require some infra work.
Commit 138ab4df fixes this issue