Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 361217

Summary: Need a way to record why/what/who triggered execution of a job
Product: z_Archived Reporter: Mike Tschierschke <mike.tschierschke>
Component: gyrexAssignee: Mike Tschierschke <mike.tschierschke>
Status: RESOLVED FIXED QA Contact:
Severity: enhancement    
Priority: P3 CC: gunnar
Version: unspecified   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:

Description Mike Tschierschke CLA 2011-10-18 04:26:43 EDT 
During the work with the provisional jobs api we noticed, that we need to improve the traceability of actions made on jobs. So we have extend the IJobManager queueJob and cancelJob methods with a mandatory field 'trigger', that simply extends the job history data. The job history also has to provide IStatus objects instead of a pair of severity and result.
We also decided, that a single schedule entry must have the ability to be disabled regardless the enclosing schedule is running.
Comment 1 Gunnar Wagenknecht CLA 2011-10-18 08:32:17 EDT 
+1
Comment 2 Gunnar Wagenknecht CLA 2011-11-01 12:49:38 EDT 
Marking fixed.