New Dashboard for Jira Cloud family: Feature requests and bugs resolved recently

[#1]

Hello everyone! I'm Rene from Atlassian Cloud Support. 

I noticed that although our bug tracker jira.atlassian.com is well known by most people, we do not have any single place where it is possible to visualize all the work being done to improve Jira Cloud and as well as the systems and tools used to enable it to function like the Identity system and the Automation module.

Thinking on this, and taking inspiration from a similar dashboard in the On-premise side I assembled a JAC dashboard so customers can see what has been resolved in terms of bugs and feature requests in the Jira Platform, JSW, JWM, JSM, Identity, Migration, and Automation projects, as well displaying the recently resolved issues that you are watching or have voted on.

This dashboard can help you keep track of anything resolved without necessarily having to be watching actively a request, allowing you to see all the work that is being done on topics that you are directly interested in as well as all the other improvements and fixes delivered, in a single place.

You can find the dashboard at: https://jira.atlassian.com/secure/Dashboard.jspa?selectPageId=110790

I'm more than happy to receive feedback and adjust the dashboard to make it more useful and let me know what you think!

[Bill Sheboy]

Hi @Rene C. [Atlassian Support] 

I suggest adding the Resolution field to the relevant gadgets to help to see final disposition.  Thanks!

Kind regards,
Bill

[Rene C. [Atlassian Support]]

HI @Bill Sheboy the gadgets currently only consider one resolution for all the issues, Fixed. All the non-implementation ones (like Timeouts, Obsolete, Won't do, Duplicates) are filtered out.

Since there are many feature requests that get bulk closed due to timeouts, lack of traction, being Duplicates, etc. as well as bug reports being marked as Duplicate, Obsolete, Not a bug, etc. maybe it is better to have a section just for Resolved issues with a Non-implementation cause.

What do you think?

[John Funk]

Thanks @Rene C. [Atlassian Support]  - this is fantastic!

I do have one question - what is the definition of the Timed Out resolution? 

[Bill Sheboy]

Rene, the filter issue, dashboard gadget can show the Resolution field.  Do you mean the saved filter used by the gadget only includes "Fixed" Resolution issues in the JQL?

Regarding which Resolution values to show, several of the suggestions / defects I have created were:

• bundled with others,
• closed without a solution (i.e., Fixed),
• no longer accessible to customers (e.g., the old CodeBarrel issues for automation rules), or
• just plain "disappeared". 

Seeing the Resolution on the dashboard regardless of solution improves transparency of disposition.  And I understand issues may be bulk closed for various reasons...possibly without product champion consideration.  Improved visibility of the volume of those bulk closures seems like valuable information for customers.

Thanks!

[Rene C. [Atlassian Support]]

@Bill Sheboy that's correct, the filters are only considering the resolution "Fixed", as that is the only resolution used to indicate something has been fixed for bugs, or implemented for Suggestions/Feature requests. From your comments, I did some adjustments and additions:

• Since using the word "resolved" was too broad, I updated the names in the corresponding gadgets for Bugs and Suggestions/Feature requests to clearly indicate that they include issues Fixed. The idea is to keep one gadget for each issue type to highlight what has been implemented.
  • Update: The resolutions for these gadgets now include "Fixed" and "Deployed".
• Following on the previous point, I added a new gadget that includes all the Bugs and Suggestions resolved with other resolutions besides "Fixed" and "Deployed", which are non-implementation ones. This gadget is called "Jira Cloud Bugs & Features closed with a Non-implementation reason in the last 6 months", it includes the Resolution field, and will show all Bugs and Suggestions/Feature requests resolved with all resolutions except "Fixed". 
• Adjusted the gadget of "Watched or voted by me" to include all resolutions, as I agree that you would like to know what happened with all those issues you are following, not just which ones were implemented. 

@John Funk: since we at Support create the bugs and Suggestions, and our Product Managers and Dev teams take over after that I am a bit detached from the process but issues that haven't had a case reported (as Support does link support requests to the relevant Bugs and Suggestions), no comments or votes have been added in a certain time threshold, and had a low impact, among other criteria might be closed as timed out.  The closure comments added to issues resolved as "Timed out" usually indicate the reasoning.

[Yatish Madhav]

Brilliant thanks for this @Rene C. [Atlassian Support] 

How can I watch updates on the dashboard?

[Avery W_ Krouse]

Hi Rene, great dashboard! I think your “implemented” issue filter might not be catching tickets you’d expect. Example:

https://jira.atlassian.com/browse/JRACLOUD-73607

The note at the top makes it seem like this was rejected, not implemented, but it is in your filter.

Also, left hand side of the dashboard at the bottom left, which free text plugin do you guys use? I want to install one into our dashboards.

[Rene C. [Atlassian Support]]

Hi, @Yatish Madhav ! Dashboards do not have a subscription system to be notified about changes in them, and this is because they don't work based on events, they have a series of gadgets and each gadget displays information based on a JQL query, so every time the page is loaded, or every 15 min (depending on the configuration of the gadget) the results are refreshed, but this happens on an individual gadget level, not on a dashboard level.

It is possible to subscribe to the individual Filters that the gadgets use to receive daily, weekly, or monthly emails with the results and I will link the JQL queries used in the dashboard here so you can subscribe to the ones you are interested in:

• I'm also discussing this with our staff to ensure the correct resolutions are set to avoid this type of confusion.

Filters:

• Cloud only: Watched or voted by me Resolved (Any cause) in last 6 months
• Cloud Only: Issues fixed/deployed in the last 6 months
• Jira Cloud Bugs & Features closed with a Non-implementation reason in the last 6 months
• Jira Cloud Bugs fixed in the last 6 months
• Jira Cloud Suggestions Implemented in the last 6 months

@Avery W_ Krouse Thank you for pointing that out. The issue JRACLOUD-73607 was resolved with the cause "Fixed" so it was appearing under the "Implemented" gadget, as that is what that resolution is meant to indicate. This was an error by the user that marked the issue as resolved and this has been corrected to now indicate the actual resolution ("Won't do"), making it appear in the "Non-implemented" gadget now.

Additionally, the gadget I am using for free text is called "Rich Text", which is only available on Server/Data Center versions of Jira.

[Avery W_ Krouse]

So you’re saying that the tickets for Jira cloud are being hosted on Jira data center? Hmmmmmmmm…

[Rene C. [Atlassian Support]]

@Avery W_ Krouse Our public bug tracker system is a Jira Data Center, so all bugs and feature requests of all our products (whether on-premise or Cloud) are there. 

[Avery W_ Krouse]

I know, just giving you a hard time. Cloud being such a huge component of Atlassian's strategy, you'd think they'd have eaten the dogfood by now!

[Rene C. [Atlassian Support]]

I have thought about this as well, and the easy answer I got myself to (without actually knowing the full extent as I am not involved in the administration of it) is that the number of integrations, links, references, customizations and work already done through 15+ years is kind of difficult to migrate, adding to this, it gets its very specific job of getting a public facing version of the work done internally, which is hosted on multiple other platforms, including Jira Cloud sites. 

So at least for this very specific case I guess we are following the good ol' "if it works, don't fix it".

[Dave Liao]

@Rene C. [Atlassian Support] - thanks for putting this together!

Suggestion: make the filter for the Watched Issues gadget visible to the public - it looks “broken” when you’re not logged in. (I know… permissions.) 🔒 

[Rene C. [Atlassian Support]]

Hi @Dave Liao Thanks for mentioning that, I configured it on purpose to require users to be  logged in as the gadget doesn't work if Jira doesn't know who you are, but I didn't think about it looking "broken" when viewing it as anonymous. I adjusted the filter now and now it will only show an empty gadget instead of an error.

[Dave Liao]

Yay, thank you! 🙏🏻