Don’t Miss Delivery Dates with Jira Version Reports

Jira Version Reports

Many people don’t know about Jira Version Reports, and even if they do, they might not have realized just how valuable they are (or how to make them valuable). And yet, Jira Version Reports (sometimes called Jira Fix Version Reports) are fantastic for tracking a Scrum team’s progress on a version and understanding what the delivery timeline is likely to look like. They’re particularly useful for product owners, project or program managers, and stakeholders.

This article reveals how the Jira Version Report provides excellent visibility of your delivery timeline so that you can manage risk, identify uncertainty, and find ways of staying on track. It also includes tips for how to get the best out of the report.

What is the Jira Version Report?

The Jira Version Report shows your team’s progress towards the completion of a version. It also gives you a predicted release date based on your team’s average rate of progress (their velocity) since starting the version, and the amount of estimated work that remains. 

The grey area

The grey area shows the scope of estimated issues to be remedied, and any change in the size of the grey area indicates that the scope of the work has changed.

The blue line

The blue line shows the progress made by demonstrating how many story points are being completed over a set period of time. The slope of the line is based on the team’s average daily velocity.

Where the blue line hits the top of the grey area gives you the predicted release date, i.e. the date on which you can expect all the issues in the version to have been fixed/completed. This is based on your average daily velocity and the amount of estimated work remaining.

The shaded blue areas

The shaded areas straddling the blue line give you the predicted release date range, aka the best-to-worst case scenario for the release date. The shaded area to the left of the blue line gives you the earliest date by which you might expect completion of the version (the optimistic date). The area to the right of the blue line gives you the latest date by which you might expect completion of the version (the pessimistic date). 

The red line

The red line shows you what percentage of issues are unestimated. Since the predicted release date and date range are based in part on the estimated work remaining, ideally you want most of your issues to be estimated. That would make the red line low. If the red line is low, it means you can have a decent amount of confidence in the predicted dates. But if the red line is high, meaning lots of your issues are unestimated, then the date range might paint a less accurate or realistic picture of what’s happening. 

Keep on Top of Estimates and Keep Jira Statuses Up-to-Date

The Jira Version Report requires the use of the fix version field and, if you want to get real value from the report, most of the issues to be remedied need to be estimated. In other words, that red line of unestimated issues should be low. The more of the fix version you have estimated the better because this will allow you to have more confidence in the predicted release dates.  

You want to make sure you keep your current statuses up to date, too, as this is what’s driving the daily velocity and the slope of your blue line. So, if a piece of work is done, put it in ‘Done’. Teams that are somewhat lax about moving things through the workflow are going to find the Jira Version Report less valuable. 

What’s great about the Jira Version Report?

The Jira Version Report gives you an instant view of potential release dates as well as any changes in scope on a particular version. It gives you a better sense of the risk in your delivery timeline, which a lot of reports don’t. It also lets you know what your uncertainty is and allows you to measure it. Specifically, as you get more and more issues estimated and your team’s velocity towards the fix version stabilizes, the blue shaded range will start to narrow, indicating an increase in certainty about the release date. 

Most importantly, the Jira Version Report is great for prompting conversations about your delivery timeline early rather than late, when you’re about to miss your delivery date. It’s always better to know in June if you’re going to miss your August delivery date than in August. It means you can decide at that point whether there’s still a way to stay on track, e.g. by decreasing scope or by increasing your team capacity. Equally, your conversations might be about the fact that you’re set to deliver early and whether to add scope.

In conclusion, the Jira Version Report is a super-useful tool for predicting when a release will be ready, for checking how a team is progressing, and for triggering discussions about how to make that progress more fruitful.

Achieve Whole Team Ownership with Jira Sprint Reports

Jira Sprint Report

The Jira Sprint Report is a Scrum team’s best friend and one of several key reports in Jira that help teams gain valuable insights on a daily basis. First and foremost, it lets you know how you’re sprint is doing in terms of progress, priorities and burndown. It also encourages conversations between team members about any progress interruptions, effects of scope changes, and improvements that can be made on the next sprint. 

Importantly, it helps you achieve whole team ownership, a concept that many organizations struggle with. 

This article explores the benefits of Jira Sprint Reports and how they foster shared responsibility and accountability across development teams.

Whole Team Ownership

What is whole team ownership? Let’s look first at the opposite model. A team focused on individual ownership has people who have a specific role and don’t typically act outside of their remit. They own the tasks they’re assigned and other team members should go through them if they have something to contribute. This is all well and good when everything’s running like clockwork. But it can be a challenge when that particular process owner is unavailable or there’s a breakdown in communication. 

Whole team ownership is about pulling down the walls between team members. These teams share responsibility, holding themselves—and each other—accountable for the team’s overall success. With whole team ownership, handing over work to a team member is more than sending an email or assigning an issue or ticket to them. It involves a conversation to confirm that all the relevant information is included and the next steps are clear. Every member of the team has the ability to impact each step, and everyone speaks up with concerns and questions to help make sure there is a collective understanding of the topic at hand. 

Jira Sprint Reports help shift responsibility from the individual to the team as a whole, by facilitating conversations that bring team members together in pursuit of a common goal.

What is the Jira Sprint Report?

The Jira Sprint Report gives Scrum teams visibility of their sprint progress and sprint dynamics. It shows the burndown of work, so you can visualize how you’re doing relative to where you are in the sprint. It allows you to identify what might be stopping you from finishing everything you’ve committed to the sprint.

Burndown charts commonly use Story Points (1), but can also use hours as a metric. The grey line (3), based on the total estimate of the issues at the start of the sprint, is your guideline. The red line (2) is the actual work done. It shows the current total estimate for unresolved issues during the sprint and reflects issues that may have been added to or removed from the sprint. 

The Jira Sprint Report also gives Scrum teams a great view of their sprint dynamics by listing completed and not-completed issues. A little asterisk appears next to any issues that are added to the sprint, giving you valuable insight each day on whether the scope of the sprint is changing. These are things that are hard to see on your sprint board or in the backlog view. 

Jira Sprint Reports also list your priorities. You’re able to see if there’s a load of high-priority incomplete issues, encouraging conversations between team members about whether you’re working on the right things in the right order.

The data displayed in a Jira Sprint Report can be used for mid-sprint progress checks and discussed during the daily stand-up. Equally it is useful for retrospective conversations. You can talk about what incomplete issues have been rolled over to the next sprint and why, and evaluate the reasons for any straight horizontal or vertical lines partway through the sprint. 

In short, the Jira Sprint Report lets you visualise the progress of your sprints and measure team success, both in the short term (are we on track to complete our sprint goal?) and the long term (are we delivering what and when we say we will?).

Note that the Jira Sprint Report is board-specific and will only consume the data that matches your board’s saved filters.

What’s Great about Jira Sprint Reports?

The Jira Sprint Report supports and facilitates the micro-planning that should be happening in your daily stand-ups, enabling you to stay on track with achieving your sprint goal. It also triggers useful discussions in retrospect, improving the quality of future sprints. Teams can ask the following questions:

  • What were the scope changes? Were any good or bad?
  • Were any stories added to the sprint that were unestimated? 
  • Did we complete all the high-priority stories?
  • Did any high-priority stories get rolled over?
  • Was there a steadily descending line on the burndown chart with a sudden drop-off at the end? This normally means that you’re handing everything over to Quality Assurance (QA) at the end of the sprint, triggering a further question…
  • How are we going to start handing over work more incrementally to QA in the future?

What’s particularly useful about the Jira Sprint Report is that it breaks down functional silos and fosters whole team ownership of the progress and quality of a sprint, and the processes therein. It encourages team members to talk to each other about how they’re going to move the team forwards, and to share responsibility for the team’s successes and failures. The sorts of questions listed above can only really be answered by the whole team coming together. 

The end result? More effective sprints, and more effective teams.

Now you’ve got the hang of Jira sprint reporting, it’s time to go faster! Check out this blog on Jira Velocity Charts

How to Use Reports in Jira – the Basics

Reports-for-Jira-Basics

Reports in Jira help everyone analyze the progress of a project, track issues, and manage time and sprints. Provided you are using Jira to manage your projects, reporting is something you will do every day. However, for someone using Jira for the first time, things can get a little complicated. Finding your way around with reports can be painstakingly challenging and time-consuming. 

Jira simplifies projects by streamlining team activities, and highlighting useful snapshots around dashboards. Through Jira, teams perform tasks in sprints or scrums. Most importantly, reporting on progress helps teams to continuously evaluate performance. The ability to zoom in and drill down on important issues is the key to using Jira productively. This post will guide you on how to use reports in Jira but first, let’s explore why the basics of Jira project reporting is crucial. 

There are different types of issues and projects that Jira administrators can create, assign, and manage within Jira. They include Kanban software development, project management, task management, process management, Scrum software development, and basic software development.

Types of Reports in Jira

Jira helps manage projects but also is an issue tracking tool, so creating reports forms an integral part of everything you do with it. The more Jira projects/issues you create, the more reports you will need. 

In Jira, there are four main types of reports:

1.) Jira Agile Boards

2.) Forecast & management

3.) Issue analysis

4.) The others.

Between these four, there are all kinds of reports to be made:

  • Time tracking reports.
  • Scrum project reports.
  • Kanban project reports. 
  • Pie Chart Reports.
  • Created vs. resolved issue reports.
  • Version workload reports.
  • Version time tracking reports.

Using Reports in Jira – the Basics

These reports help project managers allocate and analyze the utilization of sources assigned to teams. For example, budget allocation and usage tracking within Jira ensure productivity and effective resource utilization.  So the first step to using reports in Jira is learning how to generate one.

Steps to Generating and Accessing Reports in Jira

To generate a report in Jira, navigate to your Kanban, or Scrum board. Next, click ‘reports’ to view the last one you created. If you want to view all or a different report, click ‘switch reports’. Note that in the first instance, you can only view reports from agile development projects.  Upon clicking ‘switch reports’ on the agile board, you will see reports such as a burndown chart, control chart, Jira velocity charts, cumulative flow diagram, and sprint report.

Provided you have an ongoing project, you can access reports easily with a few clicks. Navigate to the specific project, and locate the menu for projects between dashboards and issues at the top.

Basic Features of Jira Reports

To use Jira reports effectively, you should understand what each report is showing, as well as the features of each report generated

The following are the main reports you can access and use in Jira:

Agile Reports in Jira

Burn-down charts tracks the quantity of pending work and the efficiency of each sprint. A sprint chart is another agile report, tracking completed tasks and feature backlog. Other features include cumulative flow diagrams, velocity charts, version reports, epic reports, control charts, release burn down, and epic burndown charts.

Forecast and Management Reports in Jira

Forecast and management reports include time tracking reports, version workload reports, and user workload reports. You will note that the forecast and management reports detail time estimates for every assigned issue.

Jira Issue Analysis Reports

Issue analysis reports give an average age report that shows the duration of unresolved issues. Another feature of this report is a pie chart report that groups projects based on specialization. Analysis reports include resolution time reports, created vs. resolved issue reports, reports on recently created issues, and reports on time since an issue was assigned.

The Bottom Line

The usefulness of reports in Jira boils down to understanding when, why and how to create Jira Reports. Jira admins and project managers can, therefore, proceed to implement necessary changes based on issues identified in the reports generated from different boards and Jira Dashboards.

Jira Agile Boards: Why and How to Create Swimlanes.

Jira Swimlane Agile Project

In a conversation my wife overheard yesterday she heard me mention ‘swimlanes’ which led her to excitedly expect that we were going to the leisure centre this weekend.  Of course as each year passes we have a tendency as a species to reuse and reapportion the meaning of words into new and fancy things. Apparently back in the annals of time the word ‘Nice’ meant ‘Silly , foolish , simple’ and the word ‘Silly’ originally meant ‘to be worthy or blessed’.  Luckily for us and our Jira musings the concept of swimlanes is very similar in use to that most of us grew up with albeit in a slightly different context.

To put it simply, ‘Swimlanes’ are normally used to separate your project ‘to-do’ lists into ordered, actionable and easily identifiable ‘faster /more important’ sections often by individual users or project areas.  They are a clever and query driven way of producing dynamic lists with a logical workflow and, significantly, are a visual way of seeing the health of a project and any outstanding blockages that need rapidly addressing.  Hitherto in most definitions this is a ‘view’ of a Kanban board and is not dissimilar to physical board forms used throughout many Agile organisations in the world. There are advantages and disadvantages of using virtual boards using swimlanes over physical boards but that is for another time.

If you choose to have such a project or set of tasks with a Kanban and swimlane approach then Jira has most bases covered. Once you have a project in mind then there are a number of key decisions that the project needs to make before creating the swimlanes on a board. (blog for further info on Visualizing Work with Jira Kanban Boards).

Get your Jira Workflow Right

It may sound obvious, but without an appropriate workflow, swimlanes are not very powerful and possibly very unusable. When you set up a project there are a number of basic workflows out of the box which you could choose but it is often better to start with fundamentals and draw your own workflow on a piece of paper before mapping it into Jira . The number of times I’ve scribbled down and modified what I was trying to do in a meeting has saved me time in the long run  – the measure twice and cut once still applies at a rudimentary ‘tech’ level! Most workflows have similar concepts such as a starting state, an end state, and one or multiple loops in the middle, but it is key for you to choose what is right for you based on what statuses you plan on reporting on, or are wanting to see.

… that includes State Transformations

So many times I have been called to look at a Jira Kanban board that cards cannot be moved on screen as they are not ‘in the right state’.

TIP:  Before you start to create your swimlanes ensure that each item can be dragged freely from one status to another within your on screen/project modelling.

Which Workflow Statuses to Report on the Jira Dashboard?

A workflow in simplest terms might have a simple three-part model with a beginning, middle, and end but this would be rare. It is more common to have many more statuses that you could group on a singular board. Jira provides the opportunity to merge multiple workflow statuses into the same columns and relabel columns in any way that suits you so you are able to have a useful board setup quickly, e.g. when presenting ‘test’ and ‘retest’ in the same column on the board to reduce space under some mapping, which is very useful when creating a board with swimlanes on it.

What Type of Jira Swimlanes Should I Use?

Jira comes with six distinct options for swimlanes each with differing purposes and uses…

Base Jira Swimlanes on Queries, Stories, Assignees, Epics, or Jira Projects

Story (or Jira Epic) Swimlanes

As you would envisage selecting to create Story or Epic related swimlanes will simply present the stories or epics in the project and in what current status they are in. There will be other information on the cards but it is a standard view of seeing the state of a project and very much looks like a traditional Kanban board.

Jira Issue Assignee Swimlanes

Selecting this option simply shows a person by person view of what work is assigned to them which might be useful for a quick view on workload at scrum master level or to see what reliance a project has on an individual e.g. if they were ill/unable to work for a period of time.

“For smaller teams, we actually prefer to do quick filters for each assignee.
On the kanban for our waterfall teams who are executing a project plan, I see a lot of value in using swimlane by query to dedicate a swimlane to critical path and another to behind target.”

Patty Land, Project Management Consultant, PwC

Jira Project Swimlanes

If reporting on multiple projects (or sub-sections of projects) then this option will allow you to see the status of each in a way so you can see what is happening from a very global perspective …. perfect for the Big-Picture megalomaniac amongst us all!

None

This option simply applies no filtering to a board and is not something I would often use but is probably useful at getting to grips with vanilla Jira Kanban boards.

Jira Query

Here’s the thing… I use query-driven swimlanes almost all the time.  You have full control, can add new queries at any time and can adjust what is seen on the screen to help present the information you are trying to show.  With the query-based approach you can create swimlanes for each of the other types described by simply writing appropriate JQL. I tend to write query-based swimlanes for each member, or team, in the project(s) and also like to have a priority-driven view i.e. highest at the top. This can be defined in the appropriate JQL and then dragging the ‘Name’ column into a relevant order on screen.

Reorder Jira Swimlane Priority

TIP:  Swimlanes can use any valid JQL so different lanes shown on the same report don’t even need to relate to each other but simply show a grid view of how a query models against a workflow

The configuration options and uses are endless here. When you suddenly have one of those meetings with ‘The Boss’ who suddenly determines that an issue you deemed insignificant has to be fixed for a big demo coming up… but don’t want to change the priority.

By utilizing a label and adding a new swimlane at the top of your settings then this and other tagged issues will suddenly be the prime focus of the next catchup meeting and can be dealt with accordingly.

JQL Jira Swimlanes Sort by Priority
Jira Board Best Practice Swimlanes

TIP:  Jira will allow as many boards as you want so you don’t ever have to stick with one view. Why not have a swimlane board dedicated to priorities and one dedicated to individual workload? The options are endless….

Conclusion

Jira Swimlanes are a fantastic way of presenting information for individuals and teams. With minimal JQL knowledge, you can create Agile Project boards within Jira containing items that you want showing and in the order you wish them to be displayed. You can hide items you don’t want displaying and use such organized boards to drive an agenda for any meeting that updates dynamically in real-time as the meeting progresses. Jira swimlanes can also be used in conjunction with quick-filters, card layout and details, and other board features to present a perfect view of your project for your audience.

Exporting Jira Data to Excel or Google Sheets

Learn how to get all of your Jira issues into Excel and Google Sheets with just a simple click.

Numerous teams all over the world use Jira and part of what makes it an amazing platform is its ability to help teams create reports.  A lot of users have been giving feedback that they want to create a custom report, which is why Jira has created a feature to help users build more customer reports for their stakeholders. Users are now able to get their Jira data into google sheets so that you can customize it more depending on your needs. You can create pivot tables and charts and relay your analysis to the stakeholders.

Why do you need spreadsheets?

When you’re working for a company or a team, team meetings are often. In daily check-ins or weekly reviews, reports are necessary to give updates and to show everyone or the stakeholders where they are in development. When generating reports, teams most likely have data that they generate or created manually based on their methods. Excel and Google Sheets are the most widely used tools for data gathering. Jira Software recognizes that it is critical to give users the ability to build their reports which is why this feature to get Jira data imported to Excel and Google Sheets exists.

Getting Started Exporting Jira to Excel

Go to your Jira project. Go to the Issues panel and Your screen should look quite similar to this.

Jira Software Advanced Search

Click on any issues that you want, depending on what data you need. Next, click “Advanced Search”, if you have Jira Software open it will be located on the top right of the screen.

When done, you’ll notice that the main panel changed and that more icons appear in the top right corner of the screen.

Advanced search in Jira Software now allows you to export, share, or automatically link your issues to Google spreadsheet or Excel. For this example, we will be generating a report from a Jira data to google spreadsheet. 

Generating a Jira Report in Google Sheets

After following the previous steps, you can just easily click the Google spreadsheet icon then allow Jira to connect to your google account. It’s that easy!  After allowing both software to connect, your Jira data will be imported to the spreadsheet.

Jira Cloud for Google Sheets integration

If you’re wondering why there’s a button saying “Install now” in the top portion of your sheet. That’s because Google has an add-on app that allows you to do more than import your Jira data to a spreadsheet. Clicking “Install now” should take you to the GSuite Marketplace.

There, click install, and you’re done.

Jira Cloud for Sheets

What’s the benefit of this add-on? Previously reports had to be manually updated, and users had to update the Jira board to rebuild the reports. This process takes time, so to help users, this add-on allows you to schedule an update so that reports are automaticaly updated.

To schedule the update, click on “Add-ons”, select “Jira Cloud for sheets” then click “Open.”
This opens the Jira Integration directly within the spreadsheet.

Jira Cloud Data Exported to Google Sheets
Jira Cloud for Google Sheets

The Jira integration should open up in the right-side panel of the screen. Click “Get issues from Jira” then navigate to the “Schedule data refresh”. Now you can select how often you want your update.

Now, if you’re running daily standups or weekly reviews out of Microsoft Excel, or Google Sheets, you can rest assured that your data is always up-to-date. You can build or own reports, or even import your formulas to give more comprehensive and detailed presentations.

Can We Integrate Jira Data with Excel?

Excel may be more popular than Google Sheets, and thankfully Jira has you covered, with an app that integrates with Microsoft Excel. To enable this feature in Excel, simply click “Insert” in the navigation bar then select “Add-ins”. This will take you to the Microsoft Office Add-ins store. Search for “Jira Cloud for Excel” and the first result should be the integration app. Now you can start creating your reports on Jira data from within Excel as well.

Jira Cloud for Excel Atlassian Marketplace addon

Excelling with Jira Reporting. Why Give a Sheet?

Documentation and reports are essential to project management. This is why Confluence and Jira exist. So why does Jira need to integrate with Excel and Google spreadsheets? The answer is to maximize productivity. When gathering data; experts and analysts use spreadsheet software to interpret, manipulate, and organize data. These experts might not be familiar with the Jira environment.

The best report is the one everyone can access, and the best tool for the job is the one everyone can use. Failure to let people use the tools they know how impairs process, and breed bad data practices.

The ability to export to Excel helps everyone do their work without adjusting to an unfamiliar platform or tool. It also helps less technical people combine data from multiple sources.

Jira Software offers simple yet powerful tools that enable users to maximize their productivity. Although Developers and Administrators are well versed in the Jira Ecosystem, features such as this show that non-developers can also experience and benefit from the Atlassian environment.

Thoughts from the Atlassian Community:

“There are great use cases for easy export, like a shared multi-client environment where single engagements come to an end and they will no longer have access to the environment, but still need an export of their data. It would sure be nice if built-in Jira reports like requirements traceability were also exportable for this purpose. Thinking about exports as a barrier to full adoption of the tool is valid, but the functionality is a necessity nonetheless.

Patty Land, Project Management Consultant, PwC

“Sad but true. A lot of users love the metrics but revert back to the systems most familiar. I encountered in training employees to JIRA with a bit of encouragement utilizing the charts and tables available in JIRA combined with verbal presentations sold it to new users.”

Liz Bowman: Change Management Training Specialist at Johnson & Johnson

“Still a good hack to know since many, especially higher management, prefer to use sheets/excel”

Andrey Stukan, Technology Consultant, Accenture

Planning on Migrating Jira Server to the Cloud or Data Center?

No Need to Panic (Even if You Weren’t Planning It)

Last week, the news broke that Atlassian are putting an end to their vestigial Server licenses for Jira, Confluence, and everything else.

Few were surprised:

If you were to play a drinking game every time Cloud was mentioned at an Atlassian event or in a shareholder report, you’d need medical attention.

Atlassian are offering three options to those currently on Server:

1.) A one-year free cloud migration trial for up to 10,000 users.

2.) A 20-55% discount to move to Cloud (for 1001 users+) or a 15%-40% discount to move to Data Center. The sooner you move, the higher the discount, so go for a 24-month deal before June/July 1st, 2021 (for Cloud/ DC respectively) to lock-in the highest discounted price for the longest time.

3.) Stay on Server, knowing that support will end for it by February 2024. Prices will go up for 1-25 users, but for most people who hadn’t cut a special Advantaged plan price deal with Atlassian, there will be very little change. You may however notice the lights slowly turning off, as fewer and fewer add-ons are supported on a dying platform.

I presume the comments section will be cynical enough about all of the above, so here are some practical considerations to help you with the migration plan.

  1. Are all your apps / add-ons supported on Cloud and Data Center? It’s simple enough to check whether your most important apps have a hosting option for Cloud and Data Center. If you’re not sure what your most important apps are, simply turn them off, and see how many people complain.
Atlassian Marketplace hosting on Cloud, Server or Data Center.

Be aware that apps may have a different marketplace listing for each platform. This can be a sign that it’s a different app, and migration may be a pain.

2. Migrating from Server to Data Center is almost no work at all. It’s practically the same platform, but the apps will have gone through rigorous testing to prove they’re reliable and stable at scale.

You may lose some of your older, less well-supported add-ons during the migration, but moving house should always be an opportunity for a spring clean!

3. Atlassian are continuously updating this handy guide on which Vendors have made migration paths from Server to Cloud. The best apps have worked hard to make sure nothing is lost in the move.

4. If in doubt, contact the Vendors directly, or your Atlassian Partner, and ask how complicated your migration might be, and whether any data or work will be lost during the migration.

Cómo hacer gráficos y diagramas en Confluence

Las herramientas de gráficos y diagramas más populares para Confluence son:

1.) Draw.Io Flowchart & Diagram Maker para Confluence

2.) Diagramas de Gliffy para Confluence

3.) Lucidchart para diagramas de Confluence

4.) SmartDraw para diagramas automáticos en Confluence

Confluence ayuda a diversos equipos a colaborar; Desde conversaciones casuales hasta documentación de cara al cliente, las plantillas de Confluence, los proyectos estructurados, la edición de imágenes, la creación de diagramas y los gráficos en Confluence hacen que la comunicación sea clara, fácil y divertida.

Una imagen puede decir mil palabras, pero con los complementos adecuados, Confluence puede ayudar a todos a comunicarse fácilmente, creando y compartiendo diagramas increibles con quien necesite verlos. Aquí hay una guía útil de las mejores aplicaciones de Confluence para crear y compartir gráficos y diagramas en Confluence.

Draw.io Flowchart & Diagram Maker para Confluence.

Draw.io es una asociación conjunta con Seibert Media , el mayor socio y vendedor de Atlassian Platinum de Alemania, famoso porsu suite de intranet Confluence, Linchpin

Lo que Draw.io hace bien:

Draw.io hace que sea muy rápido configurar diagramas de flujo con un clic intuitivo y reproducir UX.

Tienen un precio muy razonable (una décima parte del precio de algunas de las otras opciones aquí).

Anuncian con orgullo que no utilizan servidores de terceros para sus datos:

“Guardar / cargar diagramas se realiza directamente entre su navegador y los servidores de Atlassian, sin almacenamiento ni tránsito a través de servidores de terceros”.

Y han hecho que sea muy fácil importar sus propias bibliotecas de formas (si es que es el tipo de persona que tiene bibliotecas de formas).

Diagramas Gliffy para Confluence.

La aplicación de creación de diagramas Confluence más grande y popular desde 2005 con 20.000 instalaciones y 15 millones de usuarios, pero pocas integraciones compatibles.

Lo que Gliffy hace bien.

Los diagramas vinculados de Gliffy le permiten cambiar algo en un lugar y actualizar automáticamente sus vínculos en cualquier otro lugar.

El hecho de que el texto del diagrama se pueda buscar por completo lo convierte en una característica muy útil cuando intenta encontrar algo en una instancia grande.

Lucidchart: gráficos integrados de Confluence multiplataforma.

El espectacular ascenso de Lucidchart hasta ser adoptado por el 99% de las empresas Fortune 500 se puede atribuir a su excelente marketing, experiencia de usuario y gran cantidad de integraciones.

Lo que Lucidchart hace bien.

Lucidchart es la mejor opción si desea que varios usuarios editen simultáneamente un diagrama en cualquier dispositivo, en múltiples plataformas. Es más una aplicación independiente, donde Confluence es uno de los muchos lugares donde puede compartir sus diagramas.

También puede crear gráficos automáticamente a partir de datos importados de Excel, Zapier, Salesforce o LinkedIn Sales Navigator. Hay algunas integraciones inteligentes con Google Docs, Drive & Sheets; Powerpoint y Dropbox Paper para llevar tus diagramas a donde quieras.

SmartDraw para automatizar diagramas en Confluence.


Smart Draw tiene algunos autoformato inteligentes, por lo que ya sea que esté haciendo clic o usando los atajos de teclado, es muy rápido hacer, ajustar y reformatear diferentes tipos de diagramas en Confluence. También tienen un precio muy razonable y mantienen los datos de su gráfico en su Confluence.

¿Qué complemento de diagramación de Confluence es el mejor?

Todas estas opciones le permiten importar gráficos de otras herramientas (como Microsoft Visio, y entre sí), por lo que debería ser bastante fácil migrar sus gráficos si cambia de opinión más adelante.

Cada herramienta se especializa en mejorar ciertos tipos de gráficos, si está satisfecho con los gráficos básicos, entonces la capacidad de importar datos, integrarse con otras herramientas o compartir con usuarios externos podría ser el factor decisivo.

Compartiendo diagramas fuera de Confluence.

Compartir diagramas de Confluence con usuarios externos.

Independientemente de los diagramas que esté compartiendo en Confluence, tiene muchas opciones para expandir la colaboración más allá de Confluence, a donde sea necesario y para quien necesite verlo.

Un punto importante a considerar al compartir diagramas externamente es cómo compartir el texto de apoyo y circundante. Los diagramas son una parte crucial de la documentación que está compartiendo, pero si el texto y otras macros de Confluence son la forma en que comunica el panorama general, necesita más que una herramienta de creación de diagramas aislada.

Si está buscando compartir sus diagramas externamente más allá de Confluence, hay algunas consideraciones que informarán la mejor opción, según con quién está compartiendo, por cuánto tiempo y con qué propósito.

Uso de diagramas de Confluence en documentación pública.

Es bastante sencillo configurar un espacio Confluence individual como una wiki de cara al público para que todos la lean.

Para habilitar el acceso anónimo a su Confluence:

  • Vaya a Configuración> Configuración general> Permisos globales.
  • Elija Editar permisos.
  • En la sección Acceso anónimo, seleccione la casilla de verificación Puede usar. También puede elegir si desea permitir que los usuarios anónimos vean los perfiles de usuario.
  • Elija Guardar todo para aplicar los cambios.

Para hacer público su espacio:

  • Vaya al espacio y elija Herramientas de espacio> Permisos en la parte inferior de la barra lateral.
  • Elija Editar permisos.
  • Desplácese hacia abajo hasta la sección Acceso anónimo y seleccione los permisos específicos que le gustaría que tuvieran los usuarios anónimos.
  • Guardar todo para aplicar los cambios.

¡Felicitaciones, ha creado una base de conocimientos de solo lectura para sus clientes y fanáticos!

Aquí está nuestro recurso compartido externo para la documentación del cliente de Confluence:

Esto es genial si desea compartir el acceso de solo lectura no solo a sus diagramas, sino a todo el texto, las imágenes y las macros en sus espacios de Confluence con todos. La única limitación es que no podrán comentar, cargar sus poseen diagramas como archivos adjuntos, ni hacen sus propias páginas. Si está buscando darle a alguien más acceso para una colaboración más profunda, la mejor opción es:

Dales acceso completo a tu Confluence:

Realmente no tengo un párrafo para escribir aquí, simplemente cómpreles una licencia de Confluence y déles el acceso correcto según los esquemas de permisos que ha configurado en Confluence .

Brinde a los usuarios externos acceso seguro para ver, comentar y agregar archivos adjuntos a páginas individuales de Confluence.

Si desea que los usuarios externos vean páginas de Confluence específicas y todos los diagramas geniales alojados allí, considere Compartir externo para Confluence . Invite a cualquier persona a contribuir agregando comentarios y archivos adjuntos, comparta todos sus gráficos y diagramas (cualquier complemento de Confluence con el que los haya creado) sin la necesidad de dar acceso completo a nadie, ni la carga administrativa de configurar esquemas de permisos individuales para cada usuario.

Luego, puede compartir los enlaces de forma privada, limitar el tiempo antes de que caduquen, protegerlos con contraseña y desactivarlos y volver a activarlos cuando sea necesario.

No es necesario comprar una licencia, no es necesario dar acceso completo, no es necesario asegurarse de que todos estén usando los esquemas de permisos correctamente en su Confluence Space.

Entonces, si está utilizando gráficos y diagramas en su Confluence y desea compartirlos con usuarios externos, tiene tres opciones:

1.) Darles acceso de solo lectura,

2.) Darles una licencia de Confluence.

3.) Utilice External Share para Confluence .

Así que echa un vistazo a External Share for Confluence en Atlassian Marketplace hoy para comenzar una evaluación y ver por qué es una elección del personal de Atlassian para 2020.

Como Crear Gráficos de Jira en Confluence

Crear Gráficos de Jira en Confluence

Los gráficos de Jira en Confluence para informar al resto de su equipo:

1.) Agregar asunto de Jira o filtrar macros a las páginas de Confluence

2.) Utilice el plano del informe de Jira para crear un registro de cambios o un informe de estado

3.) Utilice el macro de gráfico de Jira para mostrar datos como un gráfico, incluidos gráficos circulares, gráficos creados vs resueltos y gráficos bidimensionales

4.) Utilice los gadgets de Jira para mostrar gráficos e informes detallados de Jira en las páginas

5.) Utilice los complementos de Jira Charts para Confluence para personalizar y agregar funciones a sus gráficos

Ya sea que esté compartiendo el progreso de un sprint con marketing, la alta gerencia o toda la compañía, probablemente querrá compartirlo en Confluence. Si Jira es la herramienta de colaboración para los equipos de software, Confluence es el mejor lugar para compartir actualizaciones con todos los que no utilizan Jira en el día a día.

La siguiente es una guía práctica de las diferentes opciones, herramientas, trucos y mejores prácticas para las integraciones de informes de Jira y Confluence de Atlassian. Comenzaremos con las integraciones e informes más simples, y gradualmente nos volveremos más complejos. Existen algunas diferencias significativas entre la funcionalidad del servidor Confluence y la nube. En este blog usaremos Confluence Cloud para las capturas de pantalla y agregaremos notas a las diferencias encontradas en Confluence Server.

Integraciones de Jira y Confluence listas para usar:

Servidor y Centro de Datos: antes de que pueda usar cualquiera de estos macros, sus aplicaciones Jira y Confluence deben estar conectadas a través de enlaces de aplicaciones .

Nube: los enlaces de aplicaciones se configuran automáticamente entre Jira y Confluence, por lo que no es necesario que haga nada

Agregar un macro de asunto / filtro de Jira a las páginas de Confluence

Puede mostrar una lista de asuntos o un solo asunto, según la búsqueda, el filtro o la URL de Jira Query Language (JQL) que ingrese en el macro. También puede crear un nuevo asunto de Jira desde el macro, sin salir de la página de Confluence. Aquí también tendrá la opción de seleccionar y mostrar un asunto visto recientemente. Finalmente, incluso existe la opción de mostrar un recuento de asuntos.

Para insertar este macro, o cualquier otros macros en Confluence, tiene algunas opciones:

Insertar un macro de Jira en Confluence Pages

Ver todas las macros del menú completo

Top Tip: Puede accesar directamente a la página de macros con el atajo en el teclado ⌘+⇧+A en Mac o Alt+⇧+A en PC

Si ya sabe el nombre del macro que quiere usar, la manera mas sencilla de insertarlo es teclear el corchete { en la página y comenzar a escribir el nombre del macro.

Nube: El nuevo editor de la página Nube utiliza barra inclinada / para abrir busqueda rápida

Cree un plano reporte de Jira a partir de una plantilla

Si quiere mantener las cosas sencillas,puede crear un cambio de registro o un reporte de estado sin usar Jira Query Language.

Para crear una página de Confluencia desde una plantilla haga click en crear página, buscar Jira y después seleccione reporte de Jira.

Crear un cambio de registro estándard estático no podría ser más fácil, solo selecciona el proyecto de Jira que desea y ponga un título.

Tan pronto como pulse crear, vera una lista estática de asuntos de Jira mostrando el cambio de registro.

Si desea crear un cambio de registro dinámico de Jira, vuelva a la pantalla de ajustes de cambio de registro y cambie a avanzado.

Después inserte su consulta o peguela en la URL de búsqueda de Jira (aprenda más sobre usar JQL en la documentación de Jira).Esto crea un página de reporte dinámica en Confluence, resumiendo los asuntos de Jira definidos por su Query de Jira.

Este macro dinámico de Confluencia se actualizará automáticamente cuando quiera que los asuntos relevantes sean actualizados.

Para un resumen más detallado, consulte la página de documentación de Atlassian para los asuntos del macro de Jira.

Cree un reporte de estado de Jira en Confluence

Como anteriormente, dé click en crear página, buscar Jira y seleccione reporte de Jira, pero esta vez seleccione reporte de estado.

El reporte de estado de Jira muestra el progreso del proyecto de jira seleccionado y la versión corregida en gráficas circulares.

Puede representar mefiante asignado, proyecto, componente, reportad, resolución, sprint, prioridad o tipo de asunto. The Jira status report displays the progress of your chosen Jira project and the fix version in pie charts. El estado de reporte utiliza el macro de gráficas de Jira y está basado en la información que inserte.También es una gráfica dinámica asi que su reporte de confluence se actualizara cuando sea que sus tickets de asunto de Jira sean cambiados.

Para crear sus propias gráficas, puede simplemente editar una pagina de confluence y escribir:

{Jira Charts

Esto le dará una selección de gráficas a escoger:

  • Gráfica circular: La cual ya hemos cubierto.
  • Creado vs Resuelto: La cual compara el número de asuntos creados con el numeto de asuntos resueltos en una gráfica de lineas
  • Bi-dimensional: la cual muestra un cuadro de estadísticas. Elija por : estado, versión corregida, nombre de asignado, prioridad, componente, tipo de asunto y más.

Personalizar gráficas de Jira en Confluence reportando plantillas de plano

Listas para usar las únicas personalizaciones que puede hacer a las plantillas de plano son:

  • Moverlas alrededor de la página o borrar cualquier gráfica que no quiera incluir.
  • Ajustar el ancho de cada gráfica
  • Poner o quitar el borde de la gráfica
  • Escoger mostrar información de la gráfica.
  • Cambiar el nombre de algunos encabezados y modificar el texto con las instrucciones.

Si estos ajustes de personalización parecen limitados, hay un número de apps de Macro que ofrecen muchas más opciones de personalización.

Gráficas Personalizadas de Jira para Confluence

Las gráficas personalizadas de Jira para confluence ofrecen las siguientes opciones:

  • Escoja los colores de los segmentos de la gráfica circular,embudo o gráficas de barras usando un seleccionador de color o un codigo hex
  • Reorganize el orden de los segmentos de alto a bajo o de bajo a alto con un click, o bien, arrastre y deje cualquier orden personalizada.
  • Represente con graficas por asignado, proyecto, componente, reportado, resolucion, sprint, prioridad, o tipo de asunto y campos creados por usuarios.
  • Mostrar/ ocultar segmentos que no desee ver.

una vez instalado introduzca {Custom o search para Charts

Gráficos de Confluencia personalizados para informes de Jira

Para empezar y verlo por usted mismo, revise las gráficas personalizadas de Jira para Confluence Playground aquí. Disponibles en la Nube, Server y Data Center!

Visite Atlassian Marketplace para gráficas personalizadas de Jira para Confluence y saber más.

Hacer una grafica de Jira en Confluence para tareas resueltas dentro de un intervalo de tiempo específico

Para este reporte avanzado necesitará una app como Table Filter y Charts de Stiltsoft.

Primero, combine sus graficas desde el macro Table y del Pivot Table Macro.

Ahora puede visualizar la distribución de las tareas que fueron resueltas dentro de las fechas que usted definió para su proyecto.

O puede encontrar los reportes de asuntos más activos para un proyecto específico dentro de un período de tiempo y mostrar su número de asuntos en forma de gráfico de barras.

Vea el video a continuación para ver una demostración:

Este movimiento combinado avanzado de macros permite muchas opciones de informes personalizados para usuarios avanzados. Si sabe lo que está haciendo, puede aplicar rápida y fácilmente los filtros correctos y elegir el conjunto de datos correcto desde el modo de vista de página, sin necesidad de presionar el botón editar página.

Como puede ver, hay una gran cantidad de opciones para informar y registrar los asuntos de Jira en Confluence, según sus necesidades.

Ni siquiera hemos entrado en muchas herramientas excelentes de hoja de ruta que vinculan a Jira con Confluence.

Pero esa es otra historia para otro blog. Por ahora, eche un vistazo a los gráficos personalizados de Jira para Confluence Playground y descubra lo que podría hacer con algunas opciones más personalizables en su informe de gráficos de Jira.

Why are Jira Dashboards Useful?

When you open up Jira, the Jira Dashboard is the first thing you see. That’s why making sure it displays the information most relevant and useful to your day-to-day operations can help keep teams focused, motivated and efficient.  

The following is a simple guide to making useful Jira Dashboards for those new or relatively new to Jira Software. It also offers tips and tricks for how to get the most out of them.

A successfully growing organization will have an expanding volume of projects, and programs, many of which will be launched in parallel. This makes it vital to have a Interactive Jira Dashboards that put all the information you need in one place.

What are Jira Dashboards?

Your Jira Dashboard appears on your home screen when you log in to Jira. It’s your at-a-glance picture of what’s going on across all of your projects without having to click on one or open an email.

A Jira Dashboard displays blocks called gadgets. Each gadget provides dynamic and very visual summaries of Jira project and issue data. Jira comes with a set of standard, pre-installed gadgets out of the box. A few examples are:

  • Activity Stream Gadget—displays a summary of your recent activity
  • Assigned To Me Gadget—displays all open issues in projects assigned to the user viewing the dashboard
  • Filter Results Gadget—displays the results of an issue filter
  • Pie Chart Gadget—displays issues from a project or issue filter in pie chart format (issues are grouped by statistic type, e.g. status, priority, assignee)
  • Administration Gadget—displays a checklist of common admin tasks and links to admin functions and documentation

You can also download more gadgets from the Atlassian Marketplace. More on that later.

The default dashboard

The default dashboard, called the system dashboard, is the screen Jira users will see the first time they log in. It comes loaded with gadgets from Jira’s pre-installed selection and is limited to only one dashboard page. 

Jira administrators can add, remove, reorder and in some cases configure the gadgets displayed on the default dashboard. The layout, such as the number of columns, can also be changed. You can do this by clicking Administration > System and then User Interface > System Dashboard to open the Configure System Dashboard page.


There is a limit of 20 gadgets on a single dashboard page, which means that’s all you can display on the default dashboard. If you need to, you can raise the 20-gadget limit by editing the jira-config.properties file in the Advanced Settings page of Jira’s administration area.

Just set jira.dashboard.max.gadgets to your preferred value and restart Jira. That said, we recommend a maximum of 6 gadgets per dashboard for ease of use and clarity.

David Berclaz from Apwide has helped compile an overview of some of the best apps for Interactive Jira Dashboards. Let us know if we missed any, and we’d be happy to keep this list growing!

A Project Manager’s Living Nightmare

If your projects are being managed according to a template that senior management got on a training course crammed with acronyms, it’s SAFe to assume different teams will regularly be forced to shove a lot of square peg data into round holes.

Anyone that’s worked alongside a Jira power user, sees the true potential of interactive Jira Dashboards unleashed directly in Jira.

Sadly, these organisations will often then force these subject matter experts to export the reports into Excel, and then Powerpoint.

These are exactly the sort of organisations what will forward round the data in an email chain cc’ing everyone, or if they’re hip and cool with the kids, they’ll upload the spreadsheets to a shared folder, and a master weekly report called july_reports_ulitmate_merged_final_3.pptx

Some are able to resign themselves to this minor and unnecessary evil, some complain, but few are able to challenge the growing avalanche of reports.

Unsurprisingly admin that’s considered an unnecessary and burdensome chore by most, isn’t always promptly, and fully completed. This makes the reports even less valuable as their accuracy is uncertain. Sometimes management will try and fix this by tying performance reviews to the results in the reports. Thankfully, this fixes all the problems, and doesn’t make the reports even more resented.

Sigh. As no one is now sure whether the reports are accurate or not, management will send a Slack or Whatsapp message, whenever they need information for the impending meeting.

So why would busy team members update the official reports, when a new data black market has emerged? Only the most acquiescent are still complying with the semi legalized bad data wasteland.

Eventually, the digital transformation consultants will come in, they will suggest migrating to a new platform for collaboration. Some key information will get lost in the move, and the people who embraced the old process the most zealously will be most punished for their compliance.

Now the cycle can repeat!

So before we get stuck in this groundhog day, let’s go back to basics, and get the fundamentals right!

Custom Jira Dashboards 

It’s really easy to create and customise your own dashboards. 

In Jira Cloud, just go to Dashboards > Create dashboard. 

In Jira Server & Data Center, click Dashboards > Manage Dashboards. Then click Create new dashboard in the top right of the page. 

Give your dashboard a name and description so your team knows when to use it. Fill out the remaining fields, then click save

You’ll now have an empty dashboard in front of you. Click Add gadget and choose from the available gadgets to populate your dashboard. Custom dashboards are not limited to one dashboard page. You can also edit the layout; there are five options to choose from.

You can create a different dashboard for each project you’re working on, or even multiple dashboards for a single project. However, less is quite often more, and setting up more dashboards than you need can create clutter and confusion. 

Note: some of the gadgets require filters. This means that if you share your dashboard with people who aren’t able to view the results of your filter, it means they’re not going to see any data on the dashboard. So if you want them to see any of the gadgets that have filter results, make sure the filter is turned on for those people.

Tip: you can save time creating a dashboard from scratch by copying an existing dashboard and simply changing a few of the gadgets. Just click Copy dashboard from the More menu (…) on the top right of any dashboard. 

Standard Jira Dashboard Gadgets

Filter Results

This gadget gives you easy access to the results of commonly used filters. If you find that you are constantly trawling through menus, dropdowns and individual filter screens to find the filters you use all the time, Filter Results gives you immediate visibility of them.

Issue Statistics

This gives you a breakdown of issues on a particular project, so you can track workloads, flag bottlenecks in the system and identify where you should allocate resources. 

Road Map

This list versions due for release and displays progress bars for each, showing resolved versus unresolved issues. This lets you visualise how you’re doing on each release.

Created vs Resolved Chart

This lets you see whether the overall workload is being addressed or if issues are being created faster than they are being completed. It’s one of the few actual Jira Reports that gets imported over into Gadgets. (Another is the Sprint Burndown.)

Two-Dimensional Filter Statistics

This shows the data for a particular issue filter in a configurable table format. It lets you zoom in on key areas of interest. For example, you can select a filter to retrieve all closed issues on a certain project or display the workloads of individual team members. 

Sprint Health

This gives you a snapshot of your sprint dynamics. It tells you what’s in your ‘to-do’ category (which is blue), what’s in your ‘in-progress’ category (which is yellow) and what’s in your ‘done’ category (which is green). It also tells you what percentage of time has elapsed and what percentage of work is complete. It makes for a great conversation starter; you can how see you’re doing, what the scope changes are, if any issues have been flagged, etc. It acts as a great heads-up for your Scrum master when it comes to removing roadblocks.

Useful Jira Dashboard Add-ons

I’m not saying all your problems will be solved by a good project management software stack, but let’s have a look at some of the options, and see how they could at least make things better.

Jira’s utility comes from its ubiquity, it’s expanded well past its bug tracking software days.

It’s never been easier to make useful reporting dashboards in Jira that can be presented to all stakeholders, anywhere. 

Out of the box, vanilla Jira Reports are somewhat limited, which is why there are a plethora of options on the Atlassian Marketplace with all of the options your reporting dashboards might need.

To take your Jira Reporting to the next level, embrace best practice, and set up a functional, automated, integrated, and non siloed interactive Jira dashboards that will aggregate everything you need in one place.

Check out the following add-ons on the Atlassian Marketplace, they may be just what you need to enhance your Jira reporting.

Idalko’s Jira Pivot Gadget

Idalko’s Jira Pivot Gadget provides spreadsheets and business intelligence functionality, allowing you to take a multi-dimensional view of your data and aggregate or drill down into any information you like. 

Supported dimensions include basic issue fields, all custom fields that can be enumerated, and table grid data.

Panorama – Scale Project Management.

Panorama for Jira lets you make multi-level structure of your work in Jira crossing project tree hierarchies to better plant and monitor progress, and summarize epic story points of everything you need.

Digital Toucan's Panorama for Scaled Project management in Jira hierarchies.

Find out more about Panorama Hierarchy and Structure for Jira

Panorama is available for cloud only, if you’re on Server or Data Center, you’ll need to try Structure for Jira

eazyBI – Reports and Charts for Jira

If you have a lot of data in Jira as well as other sources, and need extensive reporting options, consider eazyBI. This will export data from your Jira overnight so you can splice and visualize a snapshot of the data in your Jira. At its simplest, it’s like a pivot table for Jira data. For the more complicated reports, you’ll have to hire a full-time dedicated expert to code on behalf of the teams that need them.

Check out eazyBI for yourself 

eazyBI Reports and Charts for Jira

Jira Project Tracking With Profields

Vanilla Jira as standard offers limited reports with regards to Jira Projects.

Deiser’s Profields allows your Jira reports all the project fields they’d ever need. These powerful reporting gadgets directly inside Jira dashboards, which provides crucial insights, and works nicely with your other reporting dashboards, no need for a silo, and a bunch of reports on another tab.

Find out more about Profields for Jira

Profields for Jira Dashboards

Golive – Release and Environment Hub for Jira

If you need a simple way to publish your Release Plan, or a single source of truth for all activities taking place on your Test Environments. Display a project level timeline on a on a Jira on a timeline is important to you, I’d strongly recommend you check out Golive. It’s the best way to display and manage information on releases, test environments, and deployments.

Once again, it has the benefit of being local on the Jira Dashboard, or Confluence pages, so it’s exactly where you need it.

More info about Find out more about Golive’s Environment Hub.

Apwide's golive Test environment management dashboards for Jira

Custom Charts for Jira and Confluence

Custom Charts simply makes customizable Jira reports and charts, directly on Jira Dashboards. The customization options are broad, but more importantly, they’re easy to use. Find out more about how Custom Charts for Jira helps with enhanced Jira Reports.

Custom Jira Dashboard Rerporting

With the right addons, building a live user-friendly dashboard within Jira with all of the information you need is a relatively straightforward task for most of your team.

In Conclusion: The Importance of Jira Dashboards

Jira Dashboards enable you to walk into a status meeting knowing whether things are on track before anyone says a word. They let you come back off holiday and get a quick project update without having to trawl through emails. They also let you know the moment something goes wrong, like when a growing bug fix pile overtakes current velocity, as well as identify potential bottlenecks ahead of time.

As most users aren’t Jira experts and don’t want or need to be exposed to all of its powerful but complex features, Jira Dashboards are essential for helping technical and non-technical teams find the information they’re looking for quickly. The dashboard is the first thing users see and it’s the place where they expect to be able to find all the relevant information for their role, such as a list of issues assigned to them or the progress of the team on a version. The goal of your Jira Dashboard is to incite emotion or action. Providing the right information in the right way is the key to making sure that happens.

Of course, it’s not always possible to get your dashboard right first time. It may not be clear to your audience why the data you’ve included is relevant, in which case, take their feedback and change it. It may take a few iterations to get your dashboard properly tuned to your team and stakeholders. But remember, that’s what agility’s all about.

One final piece of advice: Is to take the time to show your team your reports, and how to use them. There’s no point in having the perfect place to share and collaborate data visualization if it’s a best-kept secret.

Business Intelligence with Jira

Written by Jens Bormueller of atlasteam.de

The Need for Change Requests in Jira.

Our clients often need to evaluate change requests in Jira, organizing them by year and by state, as well as by department and specialist groups.

Our recommendation? The eazyBI add-on, available for Jira and Confluence on the Atlassian Marketplace. It integrates with a lot of professional software, and is purpose built for such ​​business intelligence.

Using it for some things can be as simple as using a spreadsheet.

Compile fields from Jira as pivot tables and draw them as diagrams. Display the individual diagrams in dashboards.

Getting Started with eazyBI for Jira

Here is the interface for employees to ask for change requests, with a customer portal using JSD, and a linked knowledge database in Confluence.

Change requests are then shown in Jira using the process navigator.

Evaluating Change Requests

As an example, here are the dashboards for evaluating the change requests.

The second diagram from the top shows Change Requests (CRs) by Approver.
It’s easy to create a report using the field “Project” and the Jira custom field “Approver” with a simple drag-and-drop interface to chart by “issue created”, to see the total number of all existing issues, split by row.

Now let’s turn it into a “Pie” diagram.

And now we’re finished, you’re ready to add the chart to the dashboard!

Set up eazyBI so once a night, it will import the data from your Jira, it’ll then be permanently stored for use within eazyBI. This does limit its application for when you want real time reporting (as a CRM, or for Support Desks, and outages), but for more long term trends and developments, they can be continuously updated and represented with new data over time. 

Other diagrams possible are Gantt charts or even the visualization of geodata on a world map. Perform calculations in new columns, such as the number of remaining time left on a project, minus the time available until the delivery deadline.

If you’re interested in Atlassian training, hosting, or licenses, please reach out to the team at atlasteam.de

And thank them for writing this excellent blog.