Bug 773142 - RFE: Changeable sort order for second level topic tags
Summary: RFE: Changeable sort order for second level topic tags
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: Web-UI
Version: 1.x
Hardware: All
OS: All
unspecified
medium
Target Milestone: ---
: ---
Assignee: Matthew Casperson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-01-11 04:03 UTC by Misha H. Ali
Modified: 2014-08-04 22:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 01:54:40 UTC


Attachments (Terms of Use)

Description Misha H. Ali 2012-01-11 04:03:29 UTC
When expanding first level (Common Name) tags in skynet generated documentation, the second level tags (Concerns/Technologies) display in alphabetical order. This is a slight problem in EAP (where something that should be displayed more immediately, such as "Getting Started" is displayed in the middle of or further down the expanded tag list) but the strange sorting order becomes grating when the result is as follows:

Cache Loader (Common Name)
  Examples
  Frequently Asked Questions
  Getting Started

This RFE concerns a way to sort these tags differently. Perhaps an optional priority value could be attached, where if I wanted "Getting Started" to always appear as the first Concern/Technology within any Common Name, I could assign it a priority of 1 to ensure this would always apply. 

I'm not sure if these priority tags should be applied globally, another author may require a different sorted result, so perhaps we could have values within the generated book.zip files and each author could set them as required.</brainstorming>

Comment 1 Matthew Casperson 2012-02-02 07:22:18 UTC
Fixed in 20120202-1719

The order of the concerns will now follow the order of the tags in the category. I have reordered the concern category to follow a logical progression. This order can be changed at any time though.


Note You need to log in before you can comment on or make changes to this bug.