Bug 716782

Summary: RFE: Ability to group projects in a Zanata instance
Product: [Retired] Zanata Reporter: Jared MORGAN <jmorgan>
Component: UsabilityAssignee: Runa Bhattacharjee <runab>
Status: CLOSED DUPLICATE QA Contact: Ding-Yi Chen <dchen>
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: ankit, mmurray, sflaniga, zanata-bugs
Target Milestone: ---Keywords: Improvement
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-04-17 06:33:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 742111    
Bug Blocks:    

Description Jared MORGAN 2011-06-27 04:36:13 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686) AppleWebKit/534.30 (KHTML, like Gecko) Chrome/12.0.742.100 Safari/534.30

There does not seem to be a way of sorting the names of the projects in Zanata currently. It would make sorting much easier if there was.

I'm also wondering if there might be a way of grouping projects under a product group.

For example, JBoss EAP is currently growing on translate.jboss.org. It would be good to sort all related projects under one main heading (similar to how docs-stage currently groups projects). This would also remove the need to prefix all books with JBoss EAP in the project title.



Reproducible: Always

Comment 1 Alex Eng 2011-10-14 03:43:10 UTC
Project sorting resolved in https://bugzilla.redhat.com/show_bug.cgi?id=742111

Comment 2 Ding-Yi Chen 2011-12-02 04:28:28 UTC
Jared,
As Bug 746859  describe, Zanata-1.4.1 and early is actually sort by id, not by project name. This is fixed in 1.4.2.

Yet, the project grouping is not yet implemented.

Comment 3 Sean Flanigan 2012-04-17 06:33:47 UTC
Project grouping will now be tracked in bug 800869.

*** This bug has been marked as a duplicate of bug 800869 ***