Everyone using Automation Rules and Rovo is going to be impacted, let's talk about it! https://www.skool.com/live/nPHB2P6gbjy

Jira has some new reporting capabilities and we are going to review it and test them out. Join us now! https://www.skool.com/live/nPHB2P6gbjy

https://www.skool.com/live/nPHB2P6gbjy Also, we are hosting a FREE 2 day in-person even in Dallas on Oct 27-28. You should register! https://ace.atlassian.com/events/details/atlassian-the-jira-life-presents-build-it-together-2026-bit-2026-dallas-in-person-only/

The 'c' to create a Jira issue shortcut. I personally hate how it can be triggered in the weirdest places, where I would almost never create an issue (like setting a field context with an issue type and a project that both have the letter c in them). I know keyboard shortcuts can be disabled per user, but it's only that particular shortcut that grinds my gears. What's your Jira/Confluence pet peeve?

Hello everyone, May I have your vote? Link to the suggestion: https://jira.atlassian.com/browse/JSDCLOUD-18979 My implementation and description of the issue as it relates to it: Right now, I have to use this Advanced AQL and then format the columns correctly, just to see the information stored in attributes under objects from one object type that has an outbound reference to objects from another object type in the same schema: objectType = "Homes and Residents" AND "Building Number" HAVING outR("Next Power Wash and Paint Year" = "2026") I want to use the above AQL in Assets Dashboards so non-technical users can repetitively observe the correlation of this information between two objects without constant technical intervention. Further description of the setup: Currently, in the Assets schema tree, I have two particular object types "Buildings" and "Homes and Residents." In my community there are multiple homes or units in each building. Each "Buildings" object has two particular attributes named, "Building Number" and "Next Power Wash and Paint Year." "Homes and Residents" has a majority of home information to include the attribute "Building Number", which is the reference to a unique object from the "Buildings" object type. Do I have your vote yet? What do you think the chances are of Atlassian implementing this anytime soon? Thanks all!