id summary reporter owner description type status priority milestone component version resolution keywords cc estimatedhours hours billable totalhours internal 26 stop_timestamp is not correct when only one job run. alexis.michon@… bastiaans "When a job run alone on the cluster, stop_timestamp save in the database isn't correct. Same job on the same cluster has a correct stop_timestamp when there is at least one other job running at the same time." defect closed normal 0.3 jobarchived 0.2 fixed