Keeping history of service attribute changes

Registered by John Hurst on 2010-05-05

When a attribute to a service is changed (for example a MAC address of a device) is changed the old mac address is lost. It would be very useful if it kept a history of what each attribute was with time stamps of when the attribute was changed and the user that changed it.

After going into a service to make a change to any of the attributes and clicking on 'save changes' citrus makes a copy of everything on that particular service and puts it into another table that has the same field (hist_options_dsl). This history table would have two more fields that have a time stamp of when it was changed, and who changed it.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
New
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Tthat would be a lot of history, not sure I would want to look through it, but it may be necessary for CPNI compliance some day. Especially if the FCC implements section 222 across the whole internet industry. (not just phone service providers)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.