zoltanersek _outpostlabs_dev_ Atlassian Partner

Hey @Priscilla Sobreira dos Santos congrats and welcome! 

Wow, that's a huge number, congrats @Tomislav Tobijas 

Great roundup! A lot of announcements around AI, and not just MCP and Rovo but also great everyday improvements.

If the main issue is page length rather than where the files live, another option is to split the content by month or year and use the Include Page macro to surface only the current period on the main page. Older months stay on child pages, but users can still navigate to them when needed.

doesn't work for me either

Wow, that's a beautiful bridge, I must visit sometime

I voted for the JAC suggestion as well. Even a read-only dashboard experience would be a big improvement over having to switch to the mobile browser.

One rule of thumb I've found useful is: if a native connector already supports the system you need, I'd start there. You get a managed integration with less operational overhead.

I laughed out loud when reading you comment :D jira could certainly provide more sensible defaults in terms of what goes to email and what doesn't. 

Wow, tracking beer huh? That's certainly a unique way of using it. 

Welcome Brita. It's great to have your vast experience here in the community 

Nice idea. I think improving the visual hierarchy would go a long way. I'd also love an option to auto-collapse other expanded sections, once you have Spaces, Filters, and Dashboards all open, the sidebar gets surprisingly hard to scan.

Welcome, Mauricio! A Cloud migration for 7,000 users is a huge milestone. I'd be especially interested to hear what works well for driving Rovo adoption at that scale once you're further into the rollout. Best of luck!

like others pointed out if your organization owns the email domain, check whether your IT team can temporarily restore access to the former admin's mailbox. That's often the quickest path if company policy allows it.

From your description, it doesn't sound like the Epic is being recalculated, it sounds like the rule is incrementing the existing value. A change from 6 → 0 should always reduce the total, not increase it. I'd also check the Lookup issues step in the audit log. Does it return only the non-Done child issues you expect, and…

I think this would make the overdue indicators much more meaningful. Right now the formatting only answers "has this date passed?" when what most teams actually care about is "is this work late given its current state?"

Thanks, The Trigger agent action rule definitely stood out to me as well. It'll be interesting to see how teams balance deterministic workflow logic with AI-powered actions as that capability matures.

Nice work! I can't count how many times I've ended up opening DevTools or the REST API just to grab a custom field ID. This definitely fills a small but annoying gap.

I never thought you could do that in confluence lol, interesting idea

I agree with @Trudy P Claspill If Time Estimates are enabled and the Original Estimate field is added to the subtask layout, it should appear in the full Create dialog for team-managed projects.

Congratulations, Shivain, and welcome to the Atlassian Community! 🎉 Looking forward to seeing what you build next. Best of luck on your Forge journey! 🚀

Welcome to the Atlassian Community, Dani! It's great to see your background in community moderation, Congratulations on completing the Google Project Management course as well! Wishing you all the best on your Jira learning journey. 

If your goal is simply to start fresh, you have a couple of options: Cancel any active product or app trials from Atlassian Administration → Billing → and manage each individual subscription to make sure they don't convert to paid subscriptions. If you no longer need the current site at all, it may actually be easier to…

Likes, likes for everyone! Here's a picture from a hunted forest near to where I live

Nice addition! automations I'd build is: Notify the executive channel when a strategic goal changes to Off track. Create a follow-up Jira issue for the owner. Ask Rovo to draft a status update summarizing the impact and next steps.

Great to see Journeys becoming more integrated into the work item experience.

This is a really interesting direction. As a Forge developer, my biggest question is where the boundary will be between lightweight Studio apps and Marketplace apps. I like the concept of removing friction for personal productivity tools. One thing I'm curious about is whether these apps will expose the same Forge…

This is great. Recruiters often don't know what "ACP-620" or "ACA" means, but they can immediately recognize the credential level when the badge itself communicates it.

In company-managed projects, the Parent field only applies to issue types that actually support a parent (for example, Subtasks or, depending on your hierarchy configuration, child work types). If you're trying to require Parent for a standard Story, Task, or Bug, Jira won't enforce it because those issue types aren't…

how well it handles longer recordings with multiple topics. Does it identify separate actions, or is it intended to stay focused on a single request per video?