A user ran the JOBS_FOR_APPLICATION report, and for a job that was resubmitted "x" times in the same application generation, he noticed that only the last execution of the job is listed.
This happens because, with the present design of the product, it does not retain the previous execution of a resubmitted Job for the same Application generation. Each time a Job get resubmitted the data in the Database specific to the resubmitted job gets overridden by its latest submission detail.
Even if user performs a "Reset Definition" on a submitted job, the product will override the same record with the Updated detail done through reset definition action.
If the Job "A" has been submitted twice within the same application generation, then the product will retain only the 2nd submission detail.
The product will only create a new record entry, if the Job has gone into FAILED state and the user perform "RESET DEFINITION". This is the way the product has been designed to work as present.