Best Practices

1. For Meetings: 

   1. Block calendar for meetings with descriptive content & issue key (if available)

   2. If not specified, users get meetings attributed to “1:1s”, “Agile Meetings”, “Staff Meetings”, “OOO”

   3. Set up the key Internal Issues with the Description text from the Setup guide

2. For Coding:

   1. Use Jira key in the branch name or in the commit message when pushing to repo

   2. Add a build script/workflow action to validate if issue key exists on a PR

   3. Use GitHub with SSO for easily enabling org. level integration

   4. If users are not connecting IDEs, workday could be filled below typical working hours

For key reports

1. Set up Tempo Teams to mirror product or project teams that you want reporting on

2. Ensure a person belongs to one team

3. Set up Tempo Accounts to add a new dimension to reporting, and track effort for Capex reporting

4. Associate Tasks/Stories to Epics

   1. Create Maintenance epics to track effort on bugs, unplanned enhancements

   2. Set up epics to track effort under Meetings and Time off

5. Utilize Jira Premium to roll up Epics to Initiatives