You spend the majority of your week coding or performing engineering-related tasks. Your organization wants to track where you’re spending your time.
Your Jira admin or team lead has added you to Capacity Insights. This product helps your organization understand where your time and effort are being spent. A majority of the data that is used to determine where you’re spending your effort is through Jira, so ensure you keep your tickets and ticket states up-to-date.
We also recommend that you install an IDE extension and keep your calendars up to date.
Depending on how your administrator sets up Capacity Insights, you might be prompted to provide optional feedback.
Best Practices
Depending on how your organization is set up, your calendar, IDE, or code repository can also send data, such as meeting duration and commit times. To help keep your work attributed correctly, use the following best practices.
Associate Activities to Jira Issues
Your administrator should have connected your account to your providers, such as calendars or GitHub.
We recommend that all commit messages, pull requests, and reviews have the associated Jira issue added to them, and that you use the Jira issue as the branch name. This helps associate time spent with the correct issue and reduces the need to log time manually.
Keep Your Calendar Up-to-Date
As Capacity Insights consumes information from your calendar, it's important to keep your calendar up-to-date with items like vacation or other time off. Be descriptive with your non-work time blocks to help attribute time correctly. See Recommended Calendar Event Titles for more information. You should primarily see meetings attributed to “1:1s,” “Agile Meetings,” and “Staff Meetings.”