Customizing Static Object to serve your business

By Grace Bradford at 12:43pm on January 24, 2018

Insightful reports based on your team’s performance

Monitoring your team’s performance is imperative to the success of your company, but it can be hard to find a “one size fits all” style of reporting that can accurately deem the performance of each programmer on your team.

Static Object provides visibility into the sometimes murky world of coding and identifies high-level trends and behavior from the countless commits that go into a project. Static Object simplifies the process of following a task across developers, repos, and organizations, all while minimizing time spent reviewing code.

Here are a few of our favorite tools for easy reporting and quick insights into your team’s performance.

Line Impact customization

We’ve talked about Line Impact (LI) before. LI is a relative measure of commit value. We take into consideration the typical performance of developers as individual contributors, as well as your dev team as a whole. However, not all code is created equal. Writing 500 lines of CSS takes significantly less time and is less complex than writing 500 lines of Javascript. This is why we allow teams to customize LI. With customization, you can set a multiplier based on your perceived value of the difference across code languages, allowing your front-end developers to be compared equally to those working on back-end projects. Customization is available to account admins and can be found in under “file types” in your repo's settings.

Don't want to do the customization yourself? Figuring out the right multiplier is tough. Our system uses data from your repositories to periodically recalculate the appropriate LI score. This way you can choose to take the manual approach, or sit back and let the data make decisions for you.

Issue mapping

Spending time searching through JIRA issues in an attempt to map them to your GitHub commits is inefficient.. Save time and boost your project management tool kit — use issue mapping. This feature allows you to automatically link your commit groups to their corresponding JIRA issues. Mapping these commit groups, you get real data on the scope of each issue. Not only does this help you plan scope for future issues, but it also gives insight into which issues were the most impactful.

Additionally, issue mapping makes it easy to see how much “extra” work your developers are doing. Developers often encounter easy-to-fix bugs or have smaller tasks to complete that don’t always show up in JIRA. Using issue mapping, you can get a better sense of how much of a developer’s time was not related to any projects or issues. For example, if 80% of a developer’s weekly LI is directly related to JIRA issues, you know that 20% is spent on extra work. Keeping track of this number week over week will give insight into where your team’s time is truly going. To find simple instructions on how to set up issue mapping, visit this help page.

Ignore masks

When importing your repositories, we analyze all the files and add a line impact score based on the work done. However, sometimes you might not want all files or directories to be scored. For example, documentation and configuration files are a few files that may provide less impact and can skew the values between developers. With ignore masks, you can exclude any branch, directory, filename, or file extension from scoring. By ignoring files you are reducing the noise while reviewing code, saving you valuable time. You can set up this feature in your repo’s settings.

Learn more about our other features, like commit groups and Line Impact, that will elevate your code review process.