Bug 1275999 - [RFE] port groups grid to Backbone
[RFE] port groups grid to Backbone
Status: CLOSED CURRENTRELEASE
Product: Beaker
Classification: Community
Component: web UI (Show other bugs)
21
Unspecified Unspecified
unspecified Severity unspecified (vote)
: 22.0
: ---
Assigned To: Dan Callaghan
tools-bugs
: FutureFeature, NeedsTestCase, Patch
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-10-28 06:52 EDT by Dan Callaghan
Modified: 2016-01-14 00:34 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-01-14 00:34:05 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Dan Callaghan 2015-10-28 06:52:11 EDT
We should port the groups grid (/groups/) to Backgrid, similar to what we have done for some existing grids such as the activity grid.

This is something I have been toying with on and off for a while. Now seems like a good time to get it merged, considering that the group page has just been ported to Backbone for the next major release.

The main motivator here is to be able to link to search results showing all groups which a particular user is member/owner of, which the current groups grid can't do. That functionality will be useful for some other user page enhancements I have in mind.
Comment 1 Dan Callaghan 2015-10-28 06:54:09 EDT
http://gerrit.beaker-project.org/4461 Delete button on group page
http://gerrit.beaker-project.org/4462 ported groups page to Backgrid
http://gerrit.beaker-project.org/4463 expanded lucene_to_sqlalchemy to handle .any() for one-to-many relationships
http://gerrit.beaker-project.org/4464 groups grid: allow searching by member and owner
http://gerrit.beaker-project.org/4465 replace /groups/mine with a search by member on the groups grid
Comment 4 Dan Callaghan 2016-01-14 00:34:05 EST
Beaker 22.0 has been released.

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