action #122407
closed
slo-gin commented about broken slo period for immediate ticket too early
Added by jbaier_cz over 1 year ago.
Updated over 1 year ago.
Description
As can be seen on #122356#note-6, slo-gin commented about not updating an immediate ticket within the period. For immediate ticket the period should be 24 hours, yet the ticket was commented after 15 hours. Apparently, the job does only look on the date disregarding hours (the comment was made the next day in the morning).
- Subject changed from slo-gin commented to early to slo-gin commented about broken slo period for immediate ticket too early
- Status changed from New to Feedback
- Assignee set to okurz
jbaier_cz wrote:
As can be seen on #122356#note-6, slo-gin commented about not updating an immediate ticket within the period. For immediate ticket the period should be 24 hours, yet the ticket was commented after 15 hours. Apparently, the job does only look on the date disregarding hours (the comment was made the next day in the morning).
Because IIRC we only look at the results of the query https://progress.opensuse.org/issues?query_id=542 which uses "more than days ago" with value 1. We could be more gracious and change the value to 2 but I would rather keep everything as is and remind people that a ticket shouldn't stay on "immediate" over night. In the case of #122356 after you addressed the urgency by immediately pausing the pipeline and then even fix the problem within a short time then just for monitoring you could have reduced prio to "Urgent". What that approach be ok for you?
okurz wrote:
jbaier_cz wrote:
As can be seen on #122356#note-6, slo-gin commented about not updating an immediate ticket within the period. For immediate ticket the period should be 24 hours, yet the ticket was commented after 15 hours. Apparently, the job does only look on the date disregarding hours (the comment was made the next day in the morning).
Because IIRC we only look at the results of the query https://progress.opensuse.org/issues?query_id=542 which uses "more than days ago" with value 1. We could be more gracious and change the value to 2 but I would rather keep everything as is and remind people that a ticket shouldn't stay on "immediate" over night. In the case of #122356 after you addressed the urgency by immediately pausing the pipeline and then even fix the problem within a short time then just for monitoring you could have reduced prio to "Urgent". What that approach be ok for you?
That makes sense, I could decrease the priority while putting the ticket into feedback. This state basically mean, that the ticket will be commented on a daily basis, but I am fine with that (after all it is the immediate priority). With this, feel free to reject this ticket.
- Status changed from Feedback to Resolved
jbaier_cz wrote:
With this, feel free to reject this ticket.
ok, good that we clarified.
Also available in: Atom
PDF