[KULRICE-7998] Rewrite how Dirty Fields Work Created: 27/Aug/12  Updated: 12/Aug/13  Resolved: 19/Jun/13

Status: Closed
Project: Kuali Rice Development
Component/s: Development
Affects Version/s: 2.2.0-m3
Fix Version/s: 2.3
Security Level: Public (Public: Anyone can view)

Type: Task Priority: Major
Reporter: Jerry Neal (Inactive) Assignee: Brian Smith (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: Not Specified Time Spent: Not Specified
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Issue Links:
fixes KULRICE-7851 Dirty field indicator not working on ... Closed
relates to KSENROLL-8089 Dirty Field Warning and Page Refreshe... Closed
is related to KULRICE-7308 Option to override the default dirty ... Closed
KULRICE-7999 Dirty fields not being updated when u... Sub Task Open  
KULRICE-8000 Collections are lost when refresh is ... Sub Task Closed  
KULRICE-8001 Checks not correctly cleared for dirt... Sub Task Open  
Similar issues:
KULRICE-8001Checks not correctly cleared for dirty fields
KULRICE-7851Dirty field indicator not working on Collections
KULRICE-13958Checkbox dirty validation not working
KULRICE-6515Dirty fields check does not work for all pages of a view
KULRICE-7999Dirty fields not being updated when using a date picker
KULRICE-796Document how inheritance works with the Document Type hierarchy
KULRICE-9816New collection rows are not set to dirty
KULRICE-7625Dirty fields warning appears when returning from a lightbox
KULRICE-234Work with UI team to look at how best to generalize the action list so that it can show document type specific fields
KULRICE-1649Rewrite EDL to use the KNS
Rice Module:
KRAD Feature Area:
Persistence Framework
Application Requirement:
KAI Review Status: Not Required
KTI Review Status: Not Required
Include in Release Notes?:


parent JIRA for work needed to rewrite how dirty fields work

See https://wiki.kuali.org/display/KULRICE/Dirty+Fields

Comment by Jessica Coltrin (Inactive) [ 16/Oct/12 ]

moving non-blocker and non-critical m4 Jiras to 2.2-backlog

Comment by Brian Smith (Inactive) [ 19/Jun/13 ]

Whoops forgot to hit resolve on this one

Generated at Thu Apr 09 18:48:10 CDT 2020 using JIRA 6.1.5#6160-sha1:a61a0fc278117a0da0ec9b89167b8f29b6afdab2.