Project
Git integration for Jira App
Helping managers
to know software project's state
Git integration for Jira is a Jira app which allows users to see Git + Jira team activity at the project, epic, or sprint level. Managers and developers based on this information can make better decisions, identify risks, and uncover trends. I designed this app 0 to 1 and worked a lot with stakeholders, product managers and other teammates.
Long-term project
Released in 2012 and since then reached ~10k org installs. In 2021 was bought by GitKraken and is actively developed.
My role
I created all Git Integration for Jira interface working closely with developers PMs and stakeholders.
Process
Supported development team with design assets and modifications and also overall design guidance.
Outputs
Provided a style guide and a library of updated design assets based on Atlassian design principles.
Helping managers to know how software project is going
Git integration for Jira is a Jira app which allows users to see Git + Jira team activity at the project, epic, or sprint level. Managers and developers based on this information can make better decisions, identify risks, and uncover trends. I designed this app 0 to 1 and worked a lot with stakeholders, product managers and other teammates.
Evolution of Manage User Interface
The “aha” moment for app admins is connecting integrations (without this step users won’t get value). The first challenge when I joined the company was that there were a lot of requests from clients to make it possible to connect 1000’s of repositories from large organisations. Working closely with PMs we created a flow which allows to do that easily.
This problem exists and transforms through years and each time together with the team we create new approach which solves new problems. This evolution resulted in much less requests to the support and was one of the most delightful changes.
The “aha” moment for app admins is connecting integrations (without this step users won’t get value). The first challenge when I joined the company was that there were a lot of requests from clients to make it possible to connect 1000’s of repositories from large organisations. Working closely with PMs we created a flow which allows to do that easily.
This problem exists and transforms through years and each time together with the team we create new approach which solves new problems. This evolution resulted in much less requests to the support and was one of the most delightful changes.
Evolution of Manage User Interface
Pages and features
After researching the problem and talking to managers (as this view is mostly designed for manager persona) it turned out that each manager has it’s own flow and preferences on how to use Jira. Because of that and because this app was supposed to be a proof of concept, we added all kind of flexible instruments - filtering, grouping, search to then identify the best options.
Pages and features
After researching the problem and talking to managers (as this view is mostly designed for manager persona) it turned out that each manager has it’s own flow and preferences on how to use Jira. Because of that and because this app was supposed to be a proof of concept, we added all kind of flexible instruments - filtering, grouping, search to then identify the best options.
Signals for Jira
In Jira it’s problematic to see the whole picture of your project, you need to check different views (backlog, issues etc). The hypothesis is that if we will collect all these things (issue status, git information etc.) in one place it would help visibility and make easier to understand the project and what’s going on with it. The leadership already have in mind the rough concept for solving this problem - my task was to expand it and develop possible use cases and tackle other UI/UX problems.
Signals for Jira
In Jira it’s problematic to see the whole picture of your project, you need to check different views (backlog, issues etc). The hypothesis is that if we will collect all these things (issue status, git information etc.) in one place it would help visibility and make easier to understand the project and what’s going on with it. The leadership already have in mind the rough concept for solving this problem - my task was to expand it and develop possible use cases and tackle other UI/UX problems.
Feature
Sprint diff
During the product research I suggested a feature which allowed to show which issues were added in sprint or deleted from the sprint after sprint was started. It is called “Sprint diff” inspired by code diff. It was successfully implemented and loved by users (but it’s a bit hidden).
Feature Sprint Diff
During the product research I suggested a feature which allowed to show which issues were added in sprint or deleted from the sprint after sprint was started. It is called “Sprint diff” inspired by code diff. It was successfully implemented and loved by users (but it’s a bit hidden).
Merging
two products
and more
Q1 of 2025 we were solving multiple tasks simultaneously: Firstly Atlassian provided new selling options (for high-demand customers). And secondly Atlassian rolled-up new navigation This forced us to rethink our own navigation and user paths (before it was not very good designed as it was a bunch of links). Now we have a strong start to provide more value for our users and create these new paths.
Merging 2 products
Q1 of 2025 we were solving multiple tasks simultaneously: Firstly Atlassian provided new selling options (for high-demand customers). And secondly Atlassian rolled-up new navigation This forced us to rethink our own navigation and user paths (before it was not very good designed as it was a bunch of links). Now we have a strong start to provide more value for our users and create these new paths.
© 2025 - ALL RIGHTS RESERVED