action #2396: Refactor job_templates and friends
Best management of prio in job_templates
Right now, the priority of the generated jobs is defined in the test_suite. The job_template looks like a better place, but that will make the UI way more complex. We need to decide what the best solution is (which probably requires playing some days with the current implementation) and implement the required changes (if any).
- Target version set to Sprint 07
- Target version deleted (
- Priority changed from Urgent to Normal
I'm not even sure the prios as is are good to have in the long run or we shouldn't define something new.
the prio is in the job template now - we have no UI to change it at the moment, but noone is asking for it either. So let's close this for now - adding the UI is actually quite easy in the current interface
I'm asking for a UI to change the prio
- Status changed from New to Resolved
please make a specific issue then
Also available in: Atom