Issue Bot Guide
Send your email to:
incoming+jublia-operation-issues-10584635-issue-@incoming.gitlab.com
Email Subject: <Event Name> [Event ID]- <Issue outline>
Example: ACD 2021 [1316] - Unable to access Video meeting page
Body text:
Module: Web / Engage / Dataflow / Native / Maps / Video (select one)
Label: Basic support / Enterprise support / Infrastructure / Escalate (select one)
<Your content of Email>
Example:
Module: Web
Label: Basic support
Most of the attendees could not access the video meeting.
Internal note:
Make sure to add a line break after Module information
Make sure there is no typo for Module and Label information
When creating an issue in Gitlab, it is important to give the appropriate label as it affects how the tech team will prioritize the issue. The current classifications are:
Basic Support (72 hours)
Ent Support (24 hours)
Infrastructure (4 hours)
The question is, how do we classify the issue at hand?
What passes as Infrastructure (4 hours)?
If products are inaccessible → Infrastructure
Accessible but not working → Module Issue
This notifies the Tech team that the issue is critical and needs to be fixed immediately.
Any issue with this label will be treated as the highest priority.
If the issue affects the event and the client has opted for Enterprise Support, please label the issue as Ent Support (24 hours).
If the issue affects the event non-significantly and the client has NOT opted for Enterprise Support, please label the issue as Basic Support (72 hours).