When reversing a queue for the sake of admin interface convenience, i.e. adding items from the top rather than bottom, the position field added to a view shows position unaffected by the reversal. This is confusing and inconvenient to those using the "reversed" queue to add new nodes to it, but seeing completely different position in the actual view output of the queue.

Comments

merlinofchaos’s picture

merlinofchaos commented

The 'reverse in admin view' does just that, it reverses it in the administrative view. The position in the database is unchanged. If you want your views similarly reversed, you'll need to change the sort order.

rawbytes’s picture

rawbytes commented

that's true and can be fixed with a sort order, but the field still shows an unrelated position, I guess is is more of an interface expectation. From my perspective listing one position in the admin queue and having another one in the queue view as a field is confusing and makes this specific field unusable for my use case.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support
Status: Active » Closed (works as designed)

Looks like this one is by-design.