|
(→Ticket Priorities Explained)
|
(→Consideration before filing a ticket)
|
| Line 36: | |||
| *Provide the configuration for the step/uDeploy object | *Provide the configuration for the step/uDeploy object | ||
| *Provide server logs | *Provide server logs | ||
| - | *Provide a start time for the deployment | + | *Provide a start time for the deployment/time-frame you saw the error |
| *List steps taken to reproduce the error | *List steps taken to reproduce the error | ||
| *Strive to use the same terminology uDeploy uses | *Strive to use the same terminology uDeploy uses | ||
| Line 46: | |||
| *Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting. Please, no "oh by the way"s) | *Use the same ticket for a different problem unless it stems from the original issue (we use tickets for future troubleshooting. Please, no "oh by the way"s) | ||
| *Use the same priority for all tickets (If it's very time sensitive and/or detrimental to production, make it High. If not, it's probably medium or low. Check your SLAs. This helps us manage our work queue) | *Use the same priority for all tickets (If it's very time sensitive and/or detrimental to production, make it High. If not, it's probably medium or low. Check your SLAs. This helps us manage our work queue) | ||
| == Webexes == | == Webexes == | ||
