Author Name: Bob Gobeille
Original Redmine Issue: 447, http://www.fossology.org/issues/447
Original Date: 2012/01/13
Original Assignee: Mary Laser
Scheduler Administration has some usability issues. These are a combination of UI issues and data not coming from the scheduler.
For example, rather than pause job 687, I should be able to pause "mytar.tar nomos (job 687)"
Also, you should only be able to pause a job, change priority, shutdown the scheduler, etc., if you have the right permission level.
There is no way to kill a job.
Job status could be formatted much better
JOB_COMPLETE, JOB_CHECKEDOUT, etc., are not explained
Some operation result in empty secondary pulldowns. For example, if you unpause a job and there are no jobs to unpause. The user can then hit submit on this. The user should just be told that there are no jobs to unpause.
Author Name: Bob Gobeille Original Redmine Issue: 447, http://www.fossology.org/issues/447 Original Date: 2012/01/13 Original Assignee: Mary Laser
Scheduler Administration has some usability issues. These are a combination of UI issues and data not coming from the scheduler.
For example, rather than pause job 687, I should be able to pause "mytar.tar nomos (job 687)"
Also, you should only be able to pause a job, change priority, shutdown the scheduler, etc., if you have the right permission level.
There is no way to kill a job.
Job status could be formatted much better
JOB_COMPLETE, JOB_CHECKEDOUT, etc., are not explained
Some operation result in empty secondary pulldowns. For example, if you unpause a job and there are no jobs to unpause. The user can then hit submit on this. The user should just be told that there are no jobs to unpause.
Display fossology.conf should be an option.