Details
-
Type:
Story
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.10.0-b1
-
Component/s: None
-
Labels:None
-
Epic Link:
Description
Each widget on the client profile should be updated to support filters. This applies to both the client and admin interface.
- Each widget controller method should handle filtering form submission
- Each widget controller should handle creating an InputFields object with the appropriate filtering fields (perhaps these should be handled by the model? Or helper classes? Core classes?)
- Each widget should use the ajax submission option (AbstractMethod::setAjaxFiltering())
- Make sure each filtering form is hidden on initial load, but shown after submission
- Models may need to be updated to support this level of filtering
- Pagination and sorting should still function properly (submitting filters can reset pagination and filters)
Activity
| Field | Original Value | New Value |
|---|---|---|
| Epic Link | CORE-3540 [ 14785 ] |
| Rank | Ranked higher |
| Rank | Ranked higher |
| Story Points | 13 |
| Sprint | 4.10.0 Sprint 2 [ 106 ] |
| Rank | Ranked lower |
| Rank | Ranked higher |
| Story Points | 13 | 8 |
| Description |
Each widget on the client profile should be updated to support filters. This applies to both the client and admin interface.
* Each widget controller method should handle filtering form submission * Each widget controller should handle creating an InputFields object with the appropriate filtering fields (perhaps these should be handled by the model? Or helper classes? Core classes?) * Each widget should use the ajax submission option (AbstractMethod::setAjaxFiltering()) * Make sure each filtering form is hidden on initial load, but shown after submission * Models may need to be updated to support this level of filtering |
Each widget on the client profile should be updated to support filters. This applies to both the client and admin interface.
* Each widget controller method should handle filtering form submission * Each widget controller should handle creating an InputFields object with the appropriate filtering fields (perhaps these should be handled by the model? Or helper classes? Core classes?) * Each widget should use the ajax submission option (AbstractMethod::setAjaxFiltering()) * Make sure each filtering form is hidden on initial load, but shown after submission * Models may need to be updated to support this level of filtering * Pagination and sorting should still function properly (submitting filters can reset pagination and filters) |
| Assignee | Jonathan Reissmueller [ jonathan ] |
| Assignee | Abdy Franco [ abdy ] |
Automated transition triggered when Abdy Franco created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 5 hours, 36 minutes [ 20160 ] | |
| Worklog Id | 13524 [ 13524 ] |
Automated transition triggered when Abdy Franco created pull request #842 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
| Time Spent | 5 hours, 36 minutes [ 20160 ] | 6 hours, 30 minutes [ 23400 ] |
| Worklog Id | 13528 [ 13528 ] |
| Time Spent | 6 hours, 30 minutes [ 23400 ] | 7 hours, 31 minutes [ 27060 ] |
| Worklog Id | 13531 [ 13531 ] |
| Time Spent | 7 hours, 31 minutes [ 27060 ] | 7 hours, 45 minutes [ 27900 ] |
| Worklog Id | 13533 [ 13533 ] |
Automated transition triggered when Jonathan Reissmueller merged pull request #842 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |