Book a Demo

Author Topic: Sorting issue in maintenance  (Read 5029 times)

MWensOrdina

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Sorting issue in maintenance
« on: October 13, 2016, 09:06:48 pm »
One of our users has reported an issue with the sorting of our changes. Sometimes a newly added change is not added to the bottom of the list in the Maintenance / Changes screen, but gets on top of the list or is inserted mid way. The 'Sort' function helps only in this screen, re-establishing the correct sorting, but when generating a document the faulty old sorting shows in the document, and when opening the Maintenance / Changes the next time the list is in the faulty sort order yet again.

I've searched the forum and found one earlier post dating back to version 7.5 in 2009: http://sparxsystems.com/forums/smf/index.php?topic=8512.0. It remained unanswered at the time.

Is there any way to get the sorting right again without having to manually adjust the list in the resulting document?

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Re: Sorting issue in maintenance
« Reply #1 on: October 14, 2016, 08:50:12 am »
The problem is that the maintenance types don't have a position property that allows sorting. Yes, the UI allows changing the way they are sorted, and filtering the items. But this isn't something that is applied to the model and therefore also not in reports.

The best workaround I can offer is to prepend a number to the name.

MWensOrdina

  • EA Novice
  • *
  • Posts: 7
  • Karma: +0/-0
    • View Profile
Re: Sorting issue in maintenance
« Reply #2 on: October 17, 2016, 11:06:51 pm »
The best workaround I can offer is to prepend a number to the name.
That's the first thing I tried. We've had this problem in the past (I have been working with EA since 2006 despite my 'novice' status) and prefixing a number to the name worked just fine in the past. It also has the added bonus that in the Changes entry screen you can immediately see if the changes are ordered correctly, as only the name and priority are shown in the list. I would expect that numbering 0.1, 0.2, 0.3 etc for each version of the document would work, as it always did, but we suddenly get cases where version numbers above 1.0 give problems and do not order correctly