Mumi: sorting the list of issues by date

  • Done
  • quality assurance status badge
Details
4 participants
  • Felix Lechner
  • Ricardo Wurmus
  • Chris Riddoch
  • zimoun
Owner
unassigned
Submitted by
Chris Riddoch
Severity
normal

Debbugs page

Chris Riddoch wrote 4 years ago
(address . bug-guix@gnu.org)
CAOUQaeqx0rfqstYf7ToZQ-n2-_1cC6YdnSGrFohKfGqLE4WHJw@mail.gmail.com
Hi,

When using the issue tracker at issues.guix.gnu.org, clicking on the
column titled "Date submitted" in an effort to find the most recently
submitted issues results in an arrangement of rows that makes no
sense, because the javascript in the sort-table.js file is expecting
to do a string-based sort rather than a date-based sort. I've
attached a screenshot to illustrate.

However, because bug ids appear to be sequential, sorting the rows by
'id' appears to give the same result that sorting by date submitted
should. Still, sorting by date should be fixed.

Thanks!
Attachment: guix-issues-issues.png
zimoun wrote 4 years ago
(name . Chris Riddoch)(address . riddochc@gmail.com)
867dj2j71b.fsf@gmail.com
Hi,

On Mon, 12 Apr 2021 at 17:21, Chris Riddoch <riddochc@gmail.com> wrote:

Toggle quote (7 lines)
> When using the issue tracker at issues.guix.gnu.org, clicking on the
> column titled "Date submitted" in an effort to find the most recently
> submitted issues results in an arrangement of rows that makes no
> sense, because the javascript in the sort-table.js file is expecting
> to do a string-based sort rather than a date-based sort. I've
> attached a screenshot to illustrate.

Indeed. Thanks for reporting. Patch is welcome. ;-)

Cheers,
simon
Ricardo Wurmus wrote 2 years ago
Mumi: sorting the list of issues by date
(address . 47739-done@debbugs.gnu.org)
87k02gcxea.fsf@elephly.net
This is now fixed in mumi commit
4361d69de393a55ad27574d10d7c6ad62477a13e.

--
Ricardo
Closed
Felix Lechner wrote 1 years ago
(no subject)
(address . control@debbugs.gnu.org)
875xyf1fhb.fsf@lease-up.com
unarchive 68680
reassign 68680 mumi
archive 68680

unarchive 63802
reassign 63802 mumi
archive 63802

unarchive 63215
reassign 63215 mumi
archive 63215

unarchive 61645
reassign 61645 mumi
archive 61645

unarchive 60410
reassign 60410 mumi
archive 60410

unarchive 60292
reassign 60292 mumi
archive 60292

unarchive 60292
reassign 60292 mumi
archive 60292

unarchive 58573
reassign 58573 mumi
archive 58573

unarchive 54024
reassign 54024 mumi
archive 54024

unarchive 49115
reassign 49115 mumi
archive 49115

unarchive 48160
reassign 48160 mumi
archive 48160

unarchive 47739
reassign 47739 mumi
archive 47739

unarchive 47520
reassign 47520 mumi
archive 47520

unarchive 47121
reassign 47121 mumi
archive 47121

unarchive 45015
reassign 45015 mumi
archive 45015

unarchive 43661
reassign 43661 mumi
archive 43661

unarchiv 43166
reassign 43166 mumi
archive 43166

unarchive 41906
reassign 41906 mumi
archive 41906

unarchive 41098
reassign 41098 mumi
archive 41098

unarchive 39924
reassign 39924 mumi
archive 39924

unarchive 39924
reassign 39924 mumi
archive 39924

unarchive 39924
reassign 39924 mumi
archive 39924

thanks
?
Your comment

This issue is archived.

To comment on this conversation send an email to 47739@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 47739
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help