Project

General

Profile

action #2216

action #2396: Refactor job_templates and friends

Best management of prio in job_templates

Added by ancorgs over 8 years ago. Updated over 6 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Feature requests
Target version:
-
Start date:
2014-04-03
Due date:
% Done:

0%

Estimated time:
30.00 h
Difficulty:

Description

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).

History

#1 Updated by ancorgs over 8 years ago

  • Parent task set to #2396

#2 Updated by ancorgs over 8 years ago

  • Target version set to Sprint 07

#3 Updated by ancorgs over 8 years ago

  • Target version deleted (Sprint 07)

#4 Updated by coolo almost 8 years ago

  • 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.

#5 Updated by coolo almost 8 years ago

  • Category set to 122

#6 Updated by coolo almost 8 years ago

e.g. https://progress.opensuse.org/issues/912 is something that might make things much more complicated - and we might be happy we didn't start with this task first :)

#7 Updated by coolo over 6 years ago

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

#8 Updated by RBrownSUSE over 6 years ago

I'm asking for a UI to change the prio

#9 Updated by coolo over 6 years ago

  • Status changed from New to Resolved

please make a specific issue then

Also available in: Atom PDF