GitLab

Processing New Request

graph TD;
A(Issue already exists?) -- Yes --> E(Update issue)
A -- No --> B(Contact exists?)
B -- Yes --> D(Create issue)
click D "#creating-a-new-issue"
B -- No --> C(Create contact)
C --> D(Create issue)
E --> F(Urgent?)
D --> F(Urgent?)
F -- Yes --> J(Communicate with the team)
F -- No --> G(Does work need to be scheduled in?)
G -- Yes --> H(Notify the team)
G -- No --> I(Move issue to the backlog)
J --> K(Assign issue)
K --> L(Send confirmation email)
H --> L(Send confirmation email)
I --> L(Send confirmation email)
L --> M(Set workflows)

Creating a New Issue

Issues are used to manage the team’s workload and track time for billing. It is important to raise issues for both external and internal work.

Issues relating to a specific project (for example, an application or an interface) should be logged under that project.

GitBot

GitBot is our custom automation tool triggered by GitLab webhooks. GitBot will notify the first available:

• Assignee.
• Department.
• Author.

GitBot can interact with issues in the following ways:

• Unpend issues when the due date or workflow label changes.
• Notify users when an issue:
  • Is near or exceeds the time estimate.
  • Has missing contact or workflow labels.
  • Is missing an assignee when in working.