This may be related to https://pagure.io/pagure/issue/1788

Hi @wispfox,

Thanks for the report, it took me a little while to figure out what is going on
and in the process I had the opportunity to fix a few bugs, so thanks :)

Regarding your issue, I found out that it is not a bug, at least not one in pagure
and that you did change the priority of this ticket :)
Basically, looking at the fedmsg message: https://apps.fedoraproject.org/datagrepper/id?id=2017-f49b3ec4-ffcd-4e73-ae0f-db4365180a9d&is_raw=true&size=extra-large
which exposes the different priorities set for fedora-hubs you can see that there
are only three priorities, High, Low, Normal (you can also find them in the settings
page of the project). There are no empty priority.

So when you create a ticket, no priorities are set, but the drop-down where you can
pick the priorities is with as first value "High". Which means that when you update
the ticket (in this case by submitting a comment), this value is sent to the backend
which updates the database with it. Et voila, you just set the priority of this ticket
to "High".

The solution is simple, add a new priority to fedora-hubs and leave it blank in both its
weight and title.

The current settings are probably a left over from an old time as fedora-hubs was I think
one of the first project to start using priorities.

Hoping this helps :)

I am going to be closing this one as invalid for the reason I gave above.

We also had a few glitches in the messages sent while fields were in fact not really updated and these have been fixed now.

Feel free to re-open if this still happens once 2.12 is out :)

Thanks for reporting this! :)