[KULRICE-13283] Grouping classes and ids bad for row grouping in collection Created: 16/Sep/14  Updated: 16/Jan/15

Status: Open
Project: Kuali Rice Development
Component/s: Development, User Experience (UX)
Affects Version/s: 2.5
Fix Version/s: 2.6
Security Level: Public (Public: Anyone can view)

Type: Improvement Priority: Major
Reporter: Brian Smith (Inactive) Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Old
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Similar issues:
KULRICE-9475Unable to set class for a row of a collection group
KULRICE-5479Rice Dev: KRAD Adding a row in Collection Group 1 does not save the sub acocunt or Travel Fiscal Officer ID
KULRICE-5541Collection Group header classes need changing
KULRICE-12201Collection Group With Refresh has way too many rows
KULRICE-5480Rice Dev: KRAD deleting a row with error in Collection Group 1 removes error messages from other rows as well
KULRICE-12443KRAD Collection Groups don't display the correct number of rows.
KULRICE-8099collections items need to be separated from the subcollection group
KULRICE-8217Document Collections Grouping and Totaling Functionality
KULRICE-9707Validation messages for collections should allow matching on property name in addition to section/group id
KULRICE-9463Kim authorization configuration not working for groups inside stacked collection
Rice Team: Framework
Rice Module:
KRAD
Application Requirement:
Rice
KAI Review Status: Not Required
KTI Review Status: Not Required
Code Review Status: Not Required
Include in Release Notes?:
Yes

 Description   

When using a grouping title the id and classes applied become too complex/lengthy, remove the class (if not needed), the data attribute, and simplify the id. Make sure this does not affect grouping totals or grouping functionality.


Generated at Thu Apr 02 07:24:42 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.