This issue is assigned to support@openoffice.org.  It is my
understanding that this is not the purpose of the support mailing
list.  Can we reassign to a person to stop the unneccessary mails to
my inbox?
Just lookin out for myself! ;)
Michelle

I tried to reassign it to 'louis@openoffice.org' but I am not "the 
owner or submitter of the issue, or a sufficiently empowered user." I 
would add 'extremely annoying' and 'makes the mailing list archives 
unusable' to Kevin's description of the problem. Maybe you could add 
another option 'Summarise by Date - last first'.

Kevin - maybe you could reassign it to Louis yourself?

Martin

As Martin Suggested, I am trying to reassign this to 
louis@openoffice.org.

Hope this works!

Louis, if that isn't right, please let me know and I will try
something else.

;-)

okay, I went to the man who knows, EdK, and he told me that there are people with skill working on this problem. I asked: how long until it is resolved? and he said "it's in progress." Translation: don't hold your breath, but it will happen, because enough people are annoyed and expressing that annoyance. 
Because there is not much I can do now with this, am resolving this to "wontfix."
louis

Louis, tell edk he has got to be kidding ...

It's a servlet! All is needed to be done is reverse the sort criteria.

Note that people are not asking for both features; they only want it
the way it used to be.

Jason, can you dig a little into that BrowseList servlet? I am sure it
won't take more than 10 minutes...

Thanks,

Max

Ah, Max, 
i should hope he was kidding. Yes, it's a simple fix. I'll raise the hue and cry here at 
HQ.
louis

In EdK's defense, the paging mechanism (so you can view X many messages 
at a time, stepping forward and backward) makes it a non-trivial change.  Without 
paging you could just reorder the query.  With paging, you have to change the 
servlet, the db query logic, the templates, and perhaps other things.  It's 
complicated enough that you'd have to do some thinking and testing.  It's not a 
nasty change, but not a one-liner either.

BTW, the archive software used now is entirely different than before, so it's not 
really a "set the tool's feature set like it was before" but rather "make the new tool 
behave like the old tool".  :-)

I agree the change needs to happen.

-jh-

believe it, Max. It is a "feature request." Meaning the next build, meaning wait until 
next favorite time period (or the apocalypse, whichever comes soonest). 
Suggestion: that Sun request this specifically....
louis

I would like to track this as resolved later.

In the interim,  perhaps simply a link to take you to the end of 
every list would be helpful.

I do this now myself by looking at the URL of the page in the 
mailing list archive and the
first=1&&count=YYY and manually editing the url to make first = 
YYY-20 (or whatever the page max is).

Upon hitting enter, that brings me to the latest posts at the end of 
that mailing list.

If we had a link that did just that (moved you to count-pagesize) 
then I would be happy to examine the list by paging "backwards" 
through the messages from the most recent at the end.

This link should not require any sorting changes would it?

It is not perfect, but should be easy to implement with no 
underlying changes and should help make everyone happier until you 
get around to rewriting things for this "feature" request.

What do people think?

  

Is Kevin's idea sounds promising to me.

this idea sounds good; but not sure what exactly would need to be done for this to 
work (ie, is it a manual placement of a link or a generated one).
louis

For what it is worth, I have been informed that this issue has been resolved, just not for us. I have tried to arrange for Max Lanfranconi to work with collabnet to implement the fix in OOo, but don't know what the status of that collaboration is.
louis

I do not know when this enhancement (last date first) will be 
implemented. But, as a stop-gap solution, do this:
1. when in the archive, go to the url in the browser
2. switch the end with the start. 
3. press return (enter, go, whatever).
thus, ...1 to 500,
becomes 500 to 1
works for me.
louis

Being tracked by issue pcn5999 internally.

Please evaluate whether the fix can be backported from 1.3 to 1.1.

To clarify:

For the upgrade this coming Monday this fix will not be implemented. 
Backporting a fix from 1.3 to an earlier version of Scast was 
discussed at the Issue meeting previous to the OOO upgrade meeting. 
This will be researched by Cecilia and Gabby as to viability and 
details added to this issue.

Please let the party in charge of a resolving activity be owner of the
issue.

Kat,

Can you please track this issue and add the internal issue updates as 
they become available?

thanks

A fix has been backported to SourceCast1.1.3 and will be available at
the next upgrade to this version.

Adding the version this is addressed in to the Status Whiteboard
field.

Kat

Reassigning all of kat's open issues to support so that I can go through them.

Admin note: Internal issue number: PCN5999; Target Milestone: 1.1.2;
Status: Resolved.

We've brought this live on the site.  Please verify.

verified.
louis

verified and closed