Templates are for creating issues rapidly, they should globally be sorted from most used to less used (ie from top to bottom: specific template then Update Notion Page and lastly SEV5 to 1). All templates should set the status 0 - Pending Workforce and have Template Footer in a synced block as footer.
Position: This template should always be the last one in the template drop down.
Fields:
Emoji: ❤️
Name: SEV1
Severity: SEV1
Assignee: @Eliott @Elrendio
Followers: @Pierre Vigand, @Camille Devaux, the team leader of the ticket table.
If tech related, include @Sylvain.
All SEV1 tickets (templated or not) must notify:
@Eliott @Elrendio @Pierre Vigand @Camille Devaux
If tech related, include @Sylvain.
Content:
Position: Just before SEV1
Fields:
Emoji: 🧡
Name: SEV2
Severity: SEV2
Assignee: Assign the leader of the team you're creating a ticket to.
Followers: @Eliott @Elrendio @Pierre Vigand @Camille Devaux
If tech related, include @Sylvain.
All SEV2 tickets (templated or not) must notify:
@Eliott @Elrendio @Pierre Vigand @Camille Devaux
If tech related, include @Sylvain.
Content:
Position: Just before SEV2
Fields:
Emoji: 💛
Name: SEV3
Severity: SEV3
Assignee: Please assign the leader of the team you're creating a ticket to. Notably
Content:
Position: Just before SEV3
Fields:
Emoji: 💙
Name: SEV4
Severity: SEV4
Assignee: Team Ticket Reviewer
Content:
Position: Just before SEV4
Fields:
Emoji: 💜
Name: SEV5
Severity: SEV5
Assignee: Team Ticket Reviewer
Content:
This should be the default of all views of all databases
Position: At the very bottom of the list of Templates
Fields:
Emoji: 📄
Name: Update Notion Page
Severity: SEV5
Assignee: Team can choose any default Assignee or leave it empty
Content:
A team may have specific templates for recurrent tasks, they must follow the following guidelines:
Templates must have an associated emoji. Ideally no emoji is repeated.
<aside> ⚠️ Don’t change emojis from SEV (1,2,3,4,5) templates
</aside>
For automated tickets, use 🤖
Templates name should be short enough be readable in template dropdowns (no ... at the end when selecting it)
Templates targeted to a specific team may have a [Team Name] prefix, for example [Ops] for templates built for the Operations team. When using prefix, please avoid using acronyms unless the team name is longer than 10 characters. Finally, when the template is built for the team managing the table tickets, please use [Self] rather than [My Team].
When using prefixes, please order the templates as such:
[Self] templates