|
Bugzilla – Full Text Bug Listing |
| Summary: | extending History | ||
|---|---|---|---|
| Product: | [SUSE Tools] SWAMP | Reporter: | Thomas Schmidt <tschmidt> |
| Component: | Core | Assignee: | Thomas Schmidt <tschmidt> |
| Status: | RESOLVED FIXED | QA Contact: | Klaas Freitag <klaas.freitag> |
| Severity: | Major | ||
| Priority: | P2 - High | ||
| Version: | all | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Thomas Schmidt
2004-07-19 23:05:45 UTC
Yes, storing the diffs should enable us to go back to every state the databit ever was in. I'm cleaning up my bug list - Thomas, I have no idea if this is still relevant. Yes, I think it is. History needs to be much more extended. - We need every relevant Information in the History to be able to reconstruct the Workflow state at a given point in time. - History must provide an API to be queryable for certain entries. This API can be made available in the Workflow over a Dababit-Notation to be usable in Notification-Templates, Conditions, Texts... - History must provide User-relevant Information to be shown in GUI - Maybe we can provide generic Notifications for people subscribed to special History entries. the changes of Databit content must _not_ be saved in the Workflow history, because the Data is independant from a Workflow. done in svn. |