Creating charts in the All work tab!

[#1]

Hi Atlassian Community  

I'm excited to announce a new feature that's rolling out in Jira Cloud projects, designed to give your team quick and valuable insights into your work!

Available in your project’s All work tab (formerly Issues tab), we’ve developed a simple chart visualisation tool to help you aggregate and sum your project’s work data, helping you to answer questions about how your work is tracking.

Simply navigate to your Jira Cloud project’s All work tab, click on More actions (...) and select View work items as a chart in your Jira Cloud project. From there, you'll be able to transform your filtered issue list into a visual chart, making it easier to analyse the team's work data.

Here’s how it works: The chart reflects all issues filtered by your current settings in the All Work view. For instance, if you’ve filtered to show only “Done” issues and choose to chart by “Assignees,” you'll see how many completed issues are assigned to each team member. If a specific field isn’t available in the Column dropdown, add it as a column in your view.

We would love to hear your feedback, including any suggestions to improve the value of this for you and your team. Please share your suggestions using the Give Feedback button on the feature, or comment below!

[Bill Sheboy]

Hi @Lisa 

Thanks for this information, and I have a few questions about this feature:

• For which project and board types will this work: company-managed, team-managed, JPD, etc. and Scrum vs. Kanban?  I see the feature for company-managed projects but not for others.
• Your screen image apparently shows three chart types selectable with an icon button, but I see only two types from a dropdown list.  Is this feature with more charts rolling out, or are the available charts dynamic based upon the selected work items?
• There is a "share this chart" button which copies a URL to the view to the clipboard, and...
  • I find that URL does not open to the same view with the chart, regardless if one is logged into Jira or not.  Is that a known issue?
  • What has been considered to copy the chart image to the clipboard rather than the URL?

Thanks to you and the team for the improvements!

Kind regards,
Bill

[Rune Rasmussen]

If I filter something for instance worklogdate > startOfMonth(), will I somehow be able to see how many hours has been logged since the start of this month?

Or will I "only" get Work Items where work has been logged in this month, and then maybe a sum of all hours logged for the returned Work Items? 

[James Rickards (Spark-Nel)]

Thank you, Firstly, the change from "Issues" to "All work" is really welcomed, I can't express how much time is wasted explaining to new Jira users that an "issue" is not a risk that's gone bad. 

Secondly, to the developers that wrote this, well done ... nice implementation.

Thirdly, to the UX engineers who approved this design. The report adds visual complexity and thus increases cognitive load on users as it is not directly related to the reason they access the "All work" screen. On accessing the "All Work" tab, I hypnotise that the first thing most people are going to do is close that report, which increases the number of clicks before they complete their desired task. I'd ask you to please keep reports on the reports or summary tab, so we only see them when we desire to see them.

I already get complaints that Jira is too visually complex and overwhelming for new users.

EDIT: I was wrong about the UX, this is only shown if I take action to show it.

Finally, to the product owners who prioritised this ... why was this completed ahead of investment into Dashboards?

If you want to build product reputation at the executive level, please prioritise a UX that supports us Jira Admins to build reports for the directors. A director will often access Dashboards/Reports as their only function. I know their interactions are disproportionally represented in any Application Performance Managment statistics as Jira is not their daily drive, but they are the ones who choose to pay for Jira or replace it with another tool. I can't count the number of times I've seen c-suite and director level managers describe Jira as "crap" because we admins can't build decent dashboards with the few 2000 era looking gadgets and lack of choice around layouts available to us.

To ensure managers and directors have a good experience, we need quality Dashboards to support complex reporting that spans across several projects in a program of work. Capturing complex workflows, and structures of related work is where Jira excels and is its competitive advantage over the likes of Microsoft Planner and other work management tools like monday.com. Jira's ability to be customised and flexible to novel work is what differentiates if from industry specific SaaS solutions. All this hardcoded reporting (e.g. summary screen) assumes that you know what our use-case is, and how we want to report on it.

Due to the lack of investment in Dashboards over the last decade, we are having to revert to pulling data out Jira via API's and then using Microsoft Power BI to create reports that meet the business's needs. This greatly increases the barrier of entry to Jira into novel use-cases.