May 2022 Release Notes - Issue Tracking & More

Share on facebook
Share on twitter
Share on linkedin
Share on reddit
How to Notice and Prevent Software Developer Burnout

How to Notice and Prevent Software Developer Burnout

How do you notice and prevent software developer burnout as a team lead or engineering manager? Burnout affects each person a bit differently. It often starts subtly and progresses incrementally. Developer burnout feeds into a vicious loop that can make your developers quit or even change career path. If not corrected, it can also lead to health consequences. The good news is that its onset can be identified, prevented, and rapidly alleviated. Let’s examine how.

Read More »
Effective Code Reviews

Best Practices for Effective Code Reviews

More than half (53%) of the software development teams do code reviews on a daily basis, according to SmartBear’s 2019 State of Code Review. They find, as one would expect, that more frequent code reviews have a direct correlation to higher-quality code. As their report goes on to say, “There is a compounding effect when you introduce all the benefits of code review into daily behavior. Communication improves, knowledge about the codebase is shared, and fewer bugs make it through development to QA.”

Read More »

By GITENTIAL TEAM

Hello Gitential Users,

Welcome to our May 2022 Release Notes! We continue to work on many changes and improvements you’ve requested along with those on our roadmap. Now, we can present the ones most recently implemented to you. We hope you will find them nice, useful, and insightful! Got feedback? We’d love to hear from you via in-app chat or email. 🙂 

Recent updates improve issue tracking already in the app, extended Project view, helpful Knowledge Center, and continuous improvement, adding:

  • Jira / Azure Boards in the new Overview tab
  • New tabs for Project 
  • Knowledge center
  • Fixes – invitations via email, support chat

Let’s get into more details!

1. Jira and Azure Boards Issue Tracking

We know some of you wanted to have a fuller view by combining git activities and issue tracking details, so here they are!

Our new Overview tab in Project details shows how your team is working on based on selected Jira or Azure Boards projects. You can set those up while creating and editing a project:

In the first step connect your issue tracking data sources:

And after connecting repositories (2nd step), select the projects that interest you in the 3rd step:

Then just click Create or Update project button, wait a sec for the analysis to go through your data, and enjoy the deeper insights you’ll receive on your project!

Let’s check more details of what you can expect.

The first part shows your Productivity Breakdown. For your selected time range you can see the number of issues grouped by status with a comparison to the previous period for context if work on the project is improving or declining in performance.

The Team Productivity table shows the split of issues by status between the developers working on the same project. You can quickly check what you need by sorting the columns.

The Issue Details table is a summary of issues split per status within the selected time range.

We hope this first release will help you with tracking your performance better with deeper insights in one tool by aligning git activities with logged tasks.

2. Extended Project View

We know you liked the Developer Scorecard view so we wanted to take one or two steps further to update our Project view as well. 

Besides adding the above-mentioned Overview tab, we also:

  1. updated and renamed the Trends tab (previously called Summary)
  2. grouped new analytics into new, categorized tabs:
  • Speed

  • Quality

  • Efficiency

We hope this will provide you with more focused insights and make it easier to navigate through Project’s details.

3. Knowledge Center

We introduced a full Gitential “encyclopedia” where you can check exactly how to use the tool, what possibilities specific features bring you, and collected a data dictionary with tips on what they tell. You have it all available with one click – don’t hesitate to use it!

 

4. Recent Fixes

In the meantime, we had a few small issues that we fixed relating to:

  • inviting collaborators via email 
  • our in-app support chat

Everything works perfectly now so we encourage you to take advantage of it 😉

We’re working intensely on the next features and improvements so stay tuned! If only our backlog and dev team could handle all our ideas… For now, let’s keep it going step by step.

 

About Gitential

Gitential is an Analytics and Engineering Intelligence service provider bringing visibility and optimization highlights on teams’ productivity. Our mission is to enable faster, data-driven decisions to continuously improve software delivery team cost performance and proactive risk management.

Ready to explore different ways to improve your software projects’ efficiency? Schedule a meeting and we will be happy to listen to and discuss your needs.

Have a project but are not quite ready to contact us? See if Gitential is a fit for you!

FREE TRIAL FOR LIFE
for up to 5 repos, 10 devs and 3 months of data
How to Notice and Prevent Software Developer Burnout

How to Notice and Prevent Software Developer Burnout

How do you notice and prevent software developer burnout as a team lead or engineering manager? Burnout affects each person a bit differently. It often starts subtly and progresses incrementally. Developer burnout feeds into a vicious loop that can make your developers quit or even change career path. If not corrected, it can also lead to health consequences. The good news is that its onset can be identified, prevented, and rapidly alleviated. Let’s examine how.

Read More »
Effective Code Reviews

Best Practices for Effective Code Reviews

More than half (53%) of the software development teams do code reviews on a daily basis, according to SmartBear’s 2019 State of Code Review. They find, as one would expect, that more frequent code reviews have a direct correlation to higher-quality code. As their report goes on to say, “There is a compounding effect when you introduce all the benefits of code review into daily behavior. Communication improves, knowledge about the codebase is shared, and fewer bugs make it through development to QA.”

Read More »
Code Churn: The Good, The Bad and the... Perfect

Code Churn: The Good, The Bad and the… Perfect

Code churn is regarded by many software engineers as the best indicator of a code’s quality and defect density. Most engineers will also agree that code churn is good or bad relative to when and why it is taking place. But it is worth understanding in detail because it is 100x less costly to catch a defect during the design phase than catching it during maintenance.

Read More »

Did you like our content?

Spread the word

Share on facebook
Share on twitter
Share on linkedin
Share on reddit

Subscribe to Our Newsletter

Don't miss our latest updates.
All About Software Engineering Best Practices, Productivity Measurement, Performance Analytics, Software Team Management and more.

Did you like our content?

Spread the word

Share on facebook
Share on twitter
Share on linkedin
Share on reddit

Subscribe to Our Newsletter

Don't miss our latest updates. All About Software Engineering Best Practices, Productivity Measurement, Performance Analytics, Software Team Management and more.