Issue #931: Priority form not set to null - pagure - Pagure.io

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

pagure

#931 Priority form not set to null

Closed: Fixed Opened Apr 29, 2016 by ryanlerch.

If you edit the metadata for an issue, and the priority is not set for that issue, the form defaults to an actaul priority (i think the first in the list).

The form should default to the current set value, in this case '' otherwise the user will inadvertantly set the priority to something they don't want.

pingou commented Apr 29, 2016

:thumbsup: it's been annoying me as well

pingou commented May 5, 2016

Fixed in https://pagure.io/pagure/pull-request/949

pingou commented May 5, 2016

Fixed in https://pagure.io/pagure/pull-request/949

Metadata

Assignee

Tags

Blocking

None

Depending on

None

Priority

None

Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.