Pricing Adjustments for TeamCity Integration for Jira

June 30, 2022
#News
4 min

We would like to inform our community and the customers of the TeamCity for Jira Integration app of the upcoming price changes that will affect all hostings (Cloud, Server, and Data Center).

Since the first release of the app, we have extensively invested in the development of new features, provision of timely and effective support, and, of course, collaboration with you on improvements and adjustments within the app. 

Our operational costs have greatly increased since that time, and at the moment we are heavily developing the Data Center infrastructure to ensure the reliability and high performance of our app under any circumstances.

Over the years, we were working to improve services for you and provide the best quality for your satisfaction. Thus, we’ve decided to normalize the existing prices and, in particular, make the Cloud version of the app more cost-effective.

For all hostings, the price change will go into effect on August 1, 2022. Below are the new pricing models.

Cloud Pricing

Data Center Pricing

Server Pricing

Buy at today’s price

You can buy TeamCity for Jira Integration at the current price till August 1, 2022. To save up even more, go with 2 or 3-year licenses — the price will remain the same for the whole maintenance period.

But even after August 1, 2022, existing customers with commercial licenses get a 60-day grandfathering period (till September 30, 2022), so you’ll have 60 days more to renew your license for the old price.

Have questions?

Please, feel free to contact us if you have any questions or need our assistance.

Case Study: How Doutor Finanças Revamped Evaluation of Developer Performance in Jira Cloud

July 20, 2021
#How To#Jira#Case Study
9 min

This case study outlines how Doutor Finanças streamlined performance evaluation of their development teams with our Employee Performance Ratings app.

Employee performance ratings review

About the customer

Doutor Finanças helps Portuguese families balance their finances and save money on regular or one-time payments. The company aims at promotion of financial lifehacks and extensive development of financial literacy of Portuguese people.

They facilitate financial education by posting training articles, financial simulators, and various courses on budget instruments. Our customer aims at letting the Portuguese become more independent and make more informed decisions about their family budgets and financial planning. In addition to education, our customer evaluates and reviews finances of their customers, analyzes their pains and goals, and elaborates solutions for income and expense optimization.

At the moment, Doutor Finanças has more than 100 financial advisors (doctors) that work on home loans, life and property insurance, automobile loans, and consolidated credits. Since the company foundation, they have helped about 50,000 families balance and optimize their finances, reduce expenses, and find financial solutions for their needs.

Case background

Doutor Finanças runs a platform for tracking incoming requests, collecting documents, and collaborating with their customers. The dedicated development team implements new features and works on reliability and optimization of this platform.

As the company is developing its financial advisory platform as a digital product, they greatly value the quality and user-friendliness that’s why the company heavily invests in making it simple and easy-to-use.

In addition, our customer contributes to the training and professional growth of the development team, as well as facilitates and refines approaches to writing high-quality program code. That’s so they needed a tool to evaluate how development processes are evolving over time and how development teams and their processes are improving.

Looking for potential solutions

Evaluation of developers’ performance is not an easy task as it may seem at once. A lot of factors affect the way it is assessed and the metrics that are used. When you are using a SMART or OKR approach for performance evaluation, it may be not so objective as the focus is on the final results and delivery time, while quality is out of focus. In addition, six-month performance reviews performed by HR teams cannot fully reveal all the potential problems that may exist in your development processes.

Our customer wanted to integrate performance evaluation into the existing development pipeline and make it an integral part of developers’ activities. They have reviewed a lot of articles and evaluated multiple approaches of how to assess performance of development teams and what metrics to use for this.

Having tried multiple methods and frameworks, our customer was quite dissatisfied with them. They did not help them reach the defined objectives. The resulting metrics were quite useless in revealing the actual problems and issues of their development teams.

After several attempts to find the solution for their needs, they came to the Atlassian Marketplace where found our Employee Performance Ratings app. Actually, it was not the solution they actually needed, but it was the closest one to their requirements.

Reshaping the solution and adjusting it to actual needs

The Employee Performance Ratings app is an extension for Jira Cloud that lets you assess completed issues against particular metrics, like speed, quality, or skills. Our customer was one of the early adopters of the app after its release in the Atlassian Marketplace.

Collaboration with them helped us identify the key scenarios for assessment of developers and existing gaps and flaws in the current user experience. In addition, our customer requested a better way to manage metrics and let several people evaluate developer’s performance on the same task.

Besides the available dashboard with metrics and their trendline, Doutor Finanças needed export of CSV data with ratings for their further evaluation per sprint in MS Excel.

Refined approaches to developer performance assessment

After integration of the Employee Performance Ratings app into the development pipeline, our customer is using a comprehensive approach to evaluate performance of developers in Jira Cloud.

evaluate performance of developers in Jira Cloud

At the moment, they assess every development task against the three metrics (criteria):

  1. first approval: this metric indicates whether the task was approved during the first review. If not, this will decrease the resulting score. It is used as an indicator of how well the requested functionality was implemented and how many corrections were required before it fulfilled all the acceptance criteria.
  2. story points: this metric indicates whether the developer is taking more complex tasks that take more story points or deals with small and simple tasks or bugs. It defines the developer’s contribution to the project development and the introduction of new features.
  3. code quality: this metric indicates the quality of the program code written by the developer and its correspondence to guidelines and code conventions.

assessment of development tasks in Jira Cloud

Every development task is assessed against these three metrics. The developer’s progress is measured based on the sprint-to-sprint approach, so the project managers can see whether the developer improves over time or not and what activities can facilitate these improvements. So that they can elaborate on the adequate approaches to handle such situations. Progress by sprint is calculated in MS Excel on the basis of raw CSV data exported from the app.

jira task with employee performance ratings

Our customer does not leave the text feedback in the app itself, as they comment specific code snippets inline in Bitbucket, so they have no need to duplicate this information in our app.

Main benefits of developer performance assessment

The introduction of the Employee Performance Ratings app for assessment of completed tasks has improved the development processes and made the evaluation process simple and transparent to all. Project managers and team leads can now focus their attention on actual problems of their teams and address them pointwise, and developers receive continuous feedback on their work.

The app’s assessments are used for performance review and promotion of developers on a regular basis. For every evaluation period, the developer has a development plan which includes improvement of a specific metric from one value to another. So now developers are more eager to grow technically and look for more feedback on how they can progress.

Since the moment of integration of the Employee Performance Ratings app into the development pipeline, Doutor Finanças has noticed significant improvements in its development processes, increasing speed and quality of code delivery, and transformation of the performance review into a clear and transparent process for all parties.

Top 5 Reports from Jira and Bitbucket to Get the Most of Your Sprint Retrospective

August 25, 2020
#How To#Confluence Tutorial#Confluence#Reporting#Jira#Bitbucket
10 min

In the previous post How Project Managers and Scrum Masters Use Confluence for Project Monitoring, we showed how management professionals use Confluence to build a dashboard based on data from Jira and Bitbucket for project monitoring. In the present article, we move on to the second part of the dashboard. It contains reports showing what went well during the sprint and what needs to be worked on. The dashboard provides you with the visualized data for analysis during the sprint retrospective when the team can inspect itself and plan the improvements to be enacted in the following sprints. 

Analyze what’s been done: Pull Request Activities charts

The Pull Request Activities chart shows the number of pull requests by state and comes in two variants: pull requests grouped by a repository or by a user. 

By looking at these charts, you can identify if there were any problems in teams working in the same repos, see how much each person managed to do, and use these insights in future sprint planning. For example, if you see there were a lot of declined pull requests during the sprint, there could be some problems in the teams’ arrangements, so this is a perfect occasion to discuss and resolve them.

The Pull Request Activities chart shows the number of open, merged, and declined pull requests in a particular repository.
Grouped like this, the Pull Request Activities chart shows the number of pull requests made by a particular user around the whole project.

One more point to consider is the number of open pull requests at the end of the sprint — you need to count them in if you want to predict whether you’ll be able to complete work on time in the next sprint.

Follow the instructions to build these charts.

Learn, plan and improve: Pull Requests Gantt chart

The following chart can give your team an understanding of how long the pull requests take to resolve. It can help you predict using historical Git data if your team can finish the tasks by the end of the sprint.

The Pull Requests Gantt chart helps you see the tendencies in pull request resolution time for each user. 

To make realistic predictions, you need to look at the average age of PRs created by the author. If a developer is junior or new to a particular repository or project, they tend to make more mistakes, or they are subjected to more thorough reviews and testing, which potentially delays their PRs, which you need to consider in your planning. Your ideal models will be the users with sets of “colorful bricks” of almost the same size, as they will probably tend to follow the accepted practice.

One more thing that you can pay attention to is the case when a pull request or a few are closed by the very end of the sprint. It could be a sign that the author was hurrying to meet the deadline, which might be the result of review delays or just carelessness, so keep that in mind.

Check out the guide to learn how to build this chart.

Find out who did what: Activity graph

Activity Graph is made to help you know what everybody was doing during the sprint in terms of commits, pull requests, Jira issues, and meetings.

The Activity graph helps you visually compare the distribution of the workload.

The idea behind it is that predictions based on engineering metrics are great, but even a few calls or meetings can slow down the processes. In research by Harvard Business Review, 65% of senior managers said that meetings keep their teams from completing their work. That’s why you need to look at who does what, identify bottlenecks, and manage the processes so that there are no obstacles nor reasons for delays. You can determine who is spreading themselves too thin and find those who are not actively involved. It’s evident that if you expect active development from your engineers and they are stuck in a series of meetings, it won’t work. 

Using these metrics, you can understand why the team is moving with such speed and how the changes in the processes affect the team dynamics.

Learn how to build Radar (Spider) chart type.

Count it up: Velocity graph

And the last, but not the least thing when we look back on the finished iteration, is calculating velocity. 

The Velocity graph shows the ratio of story points committed vs. story points completed during the sprint.

When we plan a new sprint, we should consider the information about story points performance in the previous sprints. This way, we can observe the trends, make some conclusions, and change the planning approach if needed. For example, we can calculate the average number of story points completed within one sprint (velocity) and stick to this value in the following sprints. And after that, as more data about finished sprints is accumulated, you can plan much more accurately.

See a full guide on how to work with this graph.

Put it all together

The graphs and charts illustrated in this and the previous article make up the multifunctional dashboard for project management, aimed to give you reporting insights based on data from Jira and Bitbucket, which we presented in the Project Management Dashboards in Confluence webinar.

If you would like to build similar charts and graphs on your own, try the Table Filter and Charts for Confluence and Awesome Graphs for Bitbucket apps for free.

How to Assess Performance of Support Teams in Jira Cloud

August 18, 2020
#Jira
6 min

Every company does its best to deliver high-quality and robust support services to its customers. This lets every company establish reliable long-term relationships with customers and increase brand loyalty.

Jira Service Desk from Atlassian allows companies to set up an effective support portal and handle all sorts of support requests coming from customers.

For every business its vital to understand the quality of provided support services and continuously work on their improvement. For doing this, there are several ways how you can get insights on support effectiveness and collect feedback on what to improve from customers.

Satisfaction feedback

Jira Service Desk provides the native satisfaction feedback module which sends emails to customers once their tickets are closed. This module can be enabled within the project settings.

Every customer is prompted to leave feedback once the ticket is closed and add a comment about the support agent and provided services.

Then you can view the customer satisfaction report with all feedback and ratings which customers leave.

Using the default feedback module you can receive valuable information about your support agents and view the average rating over the recent periods. The only problem with it is that your customers may ignore it and leave no feedback at all.

Employee Performance Ratings

Unlike the standard Customer satisfaction module, the Employee Performance Ratings app provides a quick way to collect assessment ratings against the three metrics.

Once the ticket is closed, the customer can assess support quality, response speed, and efficiency of the support agent. The form appears inline in the ticket, so it increases the assessment rate if comparing to the customer satisfaction module.

Within the project, you can view the average ratings per support agent, as well as assessment details per each task. As a Customer Success Manager, you can track the overall progress of your support agents and see what you can improve.

The app allows you to export ratings to a CSV file and continue their further evaluation.

Charts and Reports for Jira ServiceDesk

This app lets you create a dashboard for tracking the progress on tickets within Service Desk projects. You can re-use widgets from the pre-defined list or create your own widgets (KPI, chart, or table) on the fly.

You can monitor the progress on tickets in real time and apply filters to compare different reporting periods. Management of the dashboard and widgets is simple and intuitive, so it will not take much time to design what you need.

If needed you can dive into details of each widget and see the raw reporting data. With this app, you can build a custom reporting solution and track the activity and performance of your support department.

Custom Charts for Jira – Reports

This app lets you design an eye-capturing dashboard and output the essential information about the performance of your support team in Jira Service Desk projects.

You can present information about tickets, customer satisfaction, workload per support agents on simple and easy-readable charts. There is a series of different chart types, so you can easily pick the one which better visualizes data and variate the data the way you need.

Configuration of widgets is pretty simple, so there should be no problems getting started with the app.

What’s next?

For assessment of the support services in Jira Service Desk, you may need to use multiple tools to get more insights on the overall status with tickets and individual performance of your support agents. First of all, identify what you want to measure and analyze and only then pick the right tool for doing this.

In the next blog post, we will review the tools to manage attachments and documents in Jira Cloud. Keep following on our blog updates.

Manage Issues in Jira Cloud Like a Pro!

August 6, 2020
#How To#Jira
8 min

Atlassian is actively developing Jira Cloud, making it more convenient and tailored to the real needs of end users. More and more features and improvements are appearing for effective issue management and task tracking.

We continue our series of blog posts dedicated to Jira Cloud. This time we will present a robust set of apps that you can use to manage Jira issues like a pro.

Issue Checklist Pro

The Issue Checklist Pro app lets you create handy checklists with small tasks within your Jira issues. Now instead of creating sub-tasks for tracking the progress on a complex task, you can create a checklist and mark completed sub-tasks.

jira Issue Checklist Pro

The overall status is shown on the progress bar. Moreover, you can format the checklist with additional elements (dates, mentions, links, and so on). You can also re-use checklists by adding them to templates and further selecting them for new tasks.

Any item from the checklist can be converted into a generic Jira sub-task on the fly. If needed, you can set up permissions for the checklist or block issue transition if the checklist is not completed yet.

The app is easy to start even for Jira Cloud newbies, and can be activated only for specific projects if needed.

Spreadsheet Issue Editor for Jira Cloud

Spreadsheet Issue Editor is an inline issue editor which lets you see specific issues in the spreadsheet. You can instantly change values in different field types and see the whole list of issues at once, so you no longer need to open issues one by one.

Spreadsheet Issue Editor for Jira

This way, you can quickly change the issue status, update issue summary, assign tasks, adjust the priority, transition to the next status, pick the due date, set story points or other values, manage labels, or add issues to different sprints.

The app is ideal for backlog grooming, task prioritization, and sprint planning. Viewing all issues on a single spreadsheet allows you to better understand the project context and act accordingly.

Structure – Project Management at Scale

Structure – Project Management at Scale is an app that helps you organize issues from one or multiple projects in a single manageable and adjustable structure. You can create hierarchies of the required complexity and depth to present all tasks in an easy-to-track way.

structure for jira

The app allows you to move tasks and issues between two structures, add automations for grouping, sorting, and updating the current list of issues, edit task details and adjust the look of your structure to better visualize the project progress.

This solution is a must-have for managing complex software projects when you need to combine data from multiple projects into a simple and traceable structure.

Issue Merger for Jira

Sooner or later, every project manager encounters a situation when the backlog contains duplicated issues and it is necessary to do something about it. The Issue Merger for Jira app lets you seamlessly merge Jira issues with all their attachments, comments, and metadata.

issue merger for jira

You just select the target issue for merging, choose fields, and other attributes to merge, and that’s it. After the merging, you can close the duplicated issue as all the relevant information is transferred to the target issue.

This app will greatly help you during the backlog grooming and triaging in Jira Cloud.

BigPicture – Project Management & PPM

The BigPicture – Project Management & PPM app is a solution that lets you manage the project portfolios, plan tasks on the Gantt chart, compare the original estimates against the time spent, plan resources, create roadmaps, manage teams, and develop risks.

This solution is versatile and allows you to plan projects comprehensively, track their progress, and manage the available capacity to complete the project on time.

big picture for jira

You can plan and track tasks on the board, as well as see their cross-dependencies. This gives project managers sufficient capabilities to manage projects and plan all the related activities on them.

big picture for jira board

The app is ideal for managing complex projects and getting the overall overview of projects in Jira Cloud.

What’s next?

You can find the right tool to effectively manage issues in Jira Cloud and start a free trial. Everything primarily depends on your use cases and the tasks that you want to accomplish. That’s why be careful when selecting the appropriate tool.

In the next blog post, we will review the tools to assess the performance of your support team in Jira Service Desk. Keep following our blog updates.

How Project Managers and Scrum Masters Use Confluence for Project Monitoring

July 28, 2020
#Analytics#Bitbucket#How To#Confluence Tutorial#Confluence#Jira#Reporting
10 min

In the Project Management Dashboards in Confluence webinar, we talked about the tools that project managers and scrum masters use, and that help them make data-driven decisions based on the data from Jira and Bitbucket. We showed how you could enhance Confluence’s default functionality to create easy-to-understand reports for management and stakeholders with all the technical and business metrics visualized on Confluence pages.

Here we bring this information back together and provide you with the guides on how to build a dashboard where you can ensure that projects remain on track and see the actual progress compared to the project objectives stated in the plans.

Visualize the backlog: open vs resolved issues graph

As new tasks, features, and bugs are added continuously during the project implementation, the visualization of the dynamics in the project backlog helps spot the bottlenecks in the processes timely. Using it, you’ll be able to find inefficiencies and support the teams, whose backlogs contain more work to do than they could possibly perform.

The Created vs Resolved Issues report shows the difference between the number of created and resolved issues over a given period and whether the overall backlog is moving towards resolution.

Open vs Resolved Issues graph

This chart is built using the Jira Issues macro, which pulls the data from Jira according to a JQL or a link to a filter. 

Check out a full guide on how to build the graph.

See the advancement in the project: Gantt chart

Gantt chart is a tool that visualizes the development process, helps to schedule your work and track the progress. In a nutshell, it is a timeline that’s used to illustrate how the project will run. You can see:

  • what tasks are included in a project or a sprint
  • start and end dates of a project or a sprint
  • tasks duration — project schedule, i.e., start and end dates
  • who works on a particular task.
Gantt chart

Using this chart, you can visualize all the tasks and phases of the project to optimize task planning and distribution, so you can predict when you will deliver the product. By visualizing the dependencies and parallel processes, you’ll also be able to find critical points, such as when the tasks depending on each other are planned at the same time slot.

We have prepared detailed instructions on how to build this kind of chart and recommend you look through the 5 Tips to Become a Gantt Chart Expert Using Atlassian Confluence article to get the most out of it.

Track the sprint progress: burndown chart

A burndown chart is often used in Agile project management to visualize the amount of work completed during the sprint compared to the total work, so a team can keep track of the time remaining to complete that work.

Burndown chart

Based on the data exported from Jira, this chart displays the total amount of work in story points that a team should complete during the sprint. An orange line is the amount of work left. A purple line displays how the sprint should run in the ideal world where the efforts are distributed equally. 

The tasks burn down as they are marked as completed and on the last day of a sprint, no significant tasks should remain. If you see that your teams tend to fail to complete the tasks in time, you need to investigate the reasons for this issue and reduce the workload.

Learn how to build this chart.

Make the development process transparent: engineering metrics

While monitoring the progress of the project, it’s necessary to see the actual change over time. Here we offer you the chart that will show the dynamics of contributions in terms of commits made by users over the chosen period. You can build a similar chart showing the pull requests dynamics and other charts based on the data from Bitbucket by feeding in the corresponding CSV file, which you can get via the Awesome Graphs for Bitbucket’s Export to CSV feature.

Using these, you’ll be able to see the trends in pull requests and commits and find out if your team is committing more code now than before.

Commits Dynamics chart

During the daily meetings, teams try to spot the difficulties that appear in the processes, and these charts can bring more transparency to them. For example, if you keep your tasks between a day or two and see that one of the developers hasn’t committed in a few days, maybe it’s time to talk and find out what difficulties they might have.

Follow the guide to build these charts.

There’s more coming

The graphs and charts described in this article will help you gain more visibility into the current state of the processes and make project monitoring easier. Using the Awesome Graphs for Bitbucket app as a data provider, and the Table Filter and Charts for Confluence app to aggregate and visualize the data from Bitbucket and Jira, you will get the functionality comparable to BI platforms in Confluence.

In the next article in the series, we’ll tell you how to build the dashboard, which can be used by any agile team for a sprint retrospective.

Watch the webinar’s recording on our YouTube channel while waiting for our next post and tell us what you think in the comment section.