15
edits
TestEngineering/Performance/Sheriffing/Workflow: Difference between revisions
Jump to navigation
Jump to search
TestEngineering/Performance/Sheriffing/Workflow (view source)
Revision as of 12:32, 29 November 2023
, 29 November 2023A note about how to correct a comment that is invalid.
Alexandrui (talk | contribs) |
Bacasandrei (talk | contribs) (A note about how to correct a comment that is invalid.) |
||
| Line 270: | Line 270: | ||
You also need to add the 'perf-alert' keyword, to indicate there is a performance alert associated with this bug. | You also need to add the 'perf-alert' keyword, to indicate there is a performance alert associated with this bug. | ||
Note: If by mistake you left a comment that is actually invalid, just add to the comment the tag '''obsolete'''. | |||
'''Attention!''' The summary could contain alerts reassigned from other alerts. You have to tick the box next to '''each untriaged alert''' and change its status to ''Acknowledge''. <br /> | '''Attention!''' The summary could contain alerts reassigned from other alerts. You have to tick the box next to '''each untriaged alert''' and change its status to ''Acknowledge''. <br /> | ||