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!

I think I saw something recently that indicated Atlassian is planning on forcing their clients to allow them to use their operational (re. proprietary) data for their internal AI learning. This is a no go for my CISO. Hard stop. Opting out seems to be limited to only Enterprise level customers? Is this correct? Am I imagining horrors that will never materialize?

What has been your favorite or most exciting announcement so far?

Environment - Jira Cloud - Jira Service Management source project - Jira Software destination project What I'm Trying to Accomplish: I have an automation rule that fires when a JSM ticket transitions to a specific status. The rule creates a new linked Jira Software ticket in a separate project. When the new ticket is created, I need all public (non-internal) comments from the JSM source ticket copied to the newly created Jira Software ticket as individual comments - one comment on the destination ticket per original comment on the source ticket. Each copied comment should include the original author's name and the date it was originally posted. To be clear: a single consolidated comment containing all the original comments lumped together does not meet the requirement. Each comment must be posted as its own discrete comment on the destination ticket. The Question: What are my options for accomplishing this in Jira Cloud? Has anyone successfully implemented something like this? For disclosure: I've built a solution that *almost* works but not quite. I'm fully up for disclosing what it is, but I'd rather have suggestions that aren't tainted by me leading the witness. A solution that uses only native Jira functionality is preferred, but I do have Scriptrunner for Cloud in my instance, so it is on the table as an option.