action #108004
closedConsider jobs important so long as they reference open bugs
Description
Motivation¶
From #105657:
- The number of retries seen in a job is pretty handy
- Log files tend to be gone after 3 days or so, which might be fine because bugs should be handled by then. Although uploading log files to bugs is recommended since otherwise the issue can't be investigated
- Idea, maybe jobs with open bugs should generally be archived?
openQA has the concept of important jobs and #108001 is about using them to keep around job results longer.
I'm thinking it would be a lot easier if openQA could rely on the comments that are added naturally as part of the review process. Less to know about, more time spent with the actual review than losing results.
Updated by livdywan about 2 years ago
- Copied from action #108001: [doc][ux][ui] Make it more obvious what "important jobs" are and how one can make jobs important (was: Important tags don't seem to have any effect) added
Updated by okurz about 2 years ago
- Category set to Support
- Status changed from New to Feedback
- Assignee set to okurz
- Target version set to Ready
cdywan wrote:
- Idea, maybe jobs with open bugs should generally be archived?
openQA has the concept of important jobs and #108001 is about using them to keep around job results longer.
I'm thinking it would be a lot easier if openQA could rely on the comments that are added naturally as part of the review process. Less to know about, more time spent with the actual review than losing results.
Well, that should be in place already considering
http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs
meaning that for any openQA job where an openQA job URL is referenced and someone clicks the openQA URL from that external reference, e.g. from the bugzilla bug report, then the job will be marked with "label:linked" which should mark the job as "important"
Updated by livdywan about 2 years ago
okurz wrote:
Well, that should be in place already considering
http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs
meaning that for any openQA job where an openQA job URL is referenced and someone clicks the openQA URL from that external reference, e.g. from the bugzilla bug report, then the job will be marked with "label:linked" which should mark the job as "important"
According to this, jobs can be marked as important How?
Alternatively a job accessed with a recognized referer is marked as important. It sounds like this would not trigger during review when the job is accessed first. And probably not at all if the browser doesn't send a referer?
Updated by okurz about 2 years ago
- Status changed from Feedback to Resolved
cdywan wrote:
okurz wrote:
Well, that should be in place already considering
http://open.qa/docs/#_referer_settings_to_auto_mark_important_jobs
meaning that for any openQA job where an openQA job URL is referenced and someone clicks the openQA URL from that external reference, e.g. from the bugzilla bug report, then the job will be marked with "label:linked" which should mark the job as "important"According to this, jobs can be marked as important How?
You can mark jobs as important by including any label or ticket reference in its comments.
I agree that this should be made more obvious in the documentation, see #108001 about that.
Alternatively a job accessed with a recognized referer is marked as important. It sounds like this would not trigger during review when the job is accessed first. And probably not at all if the browser doesn't send a referer?
After discussing with you we realized that we can make it more clear to users which jobs are important or not so we noted down the idea to add a message or icon to the job details in #65271
Agreed with cdywan that we can resolve this support ticket.