Naming convention pros :
- Searching is much easier
- Easier to find connections between various entities in Jira
- Easier to distinguish legacy customer configuration and new configuration elements
| Entity | Parameter | Naming | Examples |
|---|---|---|---|
| Issue types | Issue type schemes | Name+ Issue Type Scheme | ex. Dev Issue Type Scheme |
| Workflows | Workflow schemes | Name + Workflow Scheme | ex. Auditor Worflow Scheme |
| Workflows | Name + Workflow | ex. Dev Bug Workflow | |
| Screens | Screen Schemes | Name + Screen Scheme | ex. Dev Common Screen Scheme |
| Screens | Name + Issue type + Transition type + Screen | ex. Dev Bug Create Screen ex. Story Common Screen Major Incident Screen [CREATE] Major Incident Screen [EDIT] Major Incident Screen [VIEW] | |
| Notifications | Notification Schemes | Name + Feature + Notification Scheme | ex. Admin Common Notification Scheme ex. Customer Muted Notification Scheme |
| Permissions | Permission Schemes | Name + Feature+ Permission Scheme | ex. Sales Closed Permission Scheme |
| Automation Rules | Automation Rule Name | Project key + Issue Type + Event type | ex. IT: Incident: Set decision ALL: Incident: Transition Issue |
| JETI Email Templates | JETI Email Template Name | Project key/Process description + Issue Type + Initinal Status/Step - Final Status/Step + Transition Name | ex. ITSW: [System] Change: Approval - Extra approval (Approve) ex. RBSEC: Basic Process: Step Create - 01.01 (Create) |
1 Comment
Anonymous
examples chords of c
Add Comment