incubator-jspwiki-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Florian Holeczek (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JSPWIKI-329) wrong version history grouping on page info tab
Date Tue, 12 Aug 2008 09:22:44 GMT

    [ https://issues.apache.org/jira/browse/JSPWIKI-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12621742#action_12621742
] 

Florian Holeczek commented on JSPWIKI-329:
------------------------------------------

The real errors have gone now, however:

{quote}
On first clicking the info tab, I only get 1 version displayed (41), we could argue if this
is correct or not, I can live with it
{quote}

I can live with it, too, of course :-) But I think from the usability point of view, it would
be better to group from the latest version to the first version:
Typically, the user wants to access/compare/... any of the latest versions. This is why he
should be displayed the last 20 versions on the first click on the info tab, no matter how
many versions are existing right now. Let me give an example:

Status quo:
page 1: 1 to 20
page 2: 21 to 40
page 3: 41 to 60
page 4: 61 (= displayed page)

Proposal:
page 1: 61 to 42 (=displayed page)
page 2: 41 to 22
page 3: 21 to 2
page 4: 1


> wrong version history grouping on page info tab
> -----------------------------------------------
>
>                 Key: JSPWIKI-329
>                 URL: https://issues.apache.org/jira/browse/JSPWIKI-329
>             Project: JSPWiki
>          Issue Type: Bug
>          Components: Default template
>    Affects Versions: 2.6.3, 2.7.x
>            Reporter: Florian Holeczek
>            Priority: Minor
>             Fix For: 2.8
>
>         Attachments: JSPWIKI-329.png
>
>
> The version history is grouped by 20 entries per page. However, the grouping should follow
the sorting order. At the moment, it starts at version-1, which results e.g. in only displayed
version on page 1 if there are 20 versions available (see attached screenshot).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message