closed date editor not sorted by date

Bug #1746766 reported by Dawn Dale
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Evergreen
Won't Fix
Undecided
Unassigned

Bug Description

The closed date editor is not sorting by date. When looking at the list of closed dates they are in no significant order.

Tags: sorting
Revision history for this message
Dawn Dale (ddale) wrote :
Dan Wells (dbw2)
summary: - closed date editor
+ closed date editor not sorted by date
Revision history for this message
Jennifer Pringle (jpringle-u) wrote :

Confirming that this is still an issue in 3.1 and that I can't see any significance to the order either.

Revision history for this message
Jane Sandberg (sandbergja) wrote :

Just a note that I think this is fixed by the new emergency closing feature? https://bugs.launchpad.net/evergreen/+bug/1766716

Perhaps somebody more familiar with that project can confirm.

tags: added: sorting
Revision history for this message
Remington Steed (rjs7) wrote :

Jane, I think you're right. The Emergency Closing branch includes a new AngularJS app for managing Closed Dates, which seems to sort by closed date. I'm just reading the code, so I haven't tested anything.

Revision history for this message
Andrea Neiman (aneiman) wrote :

I can confirm that the rewrite of Closed Dates Editor (as part of Emergency Closing Handler) now shows closings in date order. That code is currently targeted for the 3.2 release.

Revision history for this message
Lynn Floyd (lfloyd) wrote :

Marked as duplicate, as it is fixed in the Rewrite.

Changed in evergreen:
status: New → Confirmed
Revision history for this message
Jason Stephenson (jstephenson) wrote :

After Jeff Godin asked about this bug in IRC today (), I decided to remove its duplicate status with bug bug 1766716. While that other bug does rectify this behavior, it does so only in Evergreen 3.2 and later releases. This issue is still open in Evergreen 3.1.

I believe that this bug should still stand on its own so it can be found via bug search, etc.

There is also the chance that someone may fix this bug in 3.1.

Changed in evergreen:
status: Confirmed → Fix Released
status: Fix Released → Confirmed
no longer affects: evergreen/3.1
Revision history for this message
Terran McCanna (tmccanna) wrote :

Marking this as Won't Fix since it has been resolved.

Changed in evergreen:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.