zoltanersek _outpostlabs_dev_ Atlassian Partner

I don't believe JSM has native support for audience-targeted announcements in the customer portal today. Portal announcements are generally intended to be broad rather than segmented. If your goal is to communicate with a specific subset of customers (for example, everyone involved in Project A), I'd be inclined to model…

yeah, I agree, remote made it way harder, and it's already been like 6 years from when things started moving to remote but I guess, it's easier to make friends when you're younger as well

Thank you @Brita Moorus I agree, I would keep standup only for blockers or unclear items as well, quick on track statuses would make this meetings go a lot faster

This is a really nice addition. I can already see a few automation rules disappearing from our instances. One thing I'd love to see over time is support for date/time calculations using now(). There are quite a few use cases like issue age, days until due date, or "days since last updated" that currently require automation…

I think you've hit on an important distinction: AI is much more effective when it's given evidence, not just a problem statement. I've found that the best results come from feeding it the API response, stack trace, field metadata, or audit log and asking "what does this tell us?" rather than "write me a script that does X."

If every product roadmap competes equally for the same engineering team, no tool can solve the prioritization problem. We found it helpful to agree on capacity allocation first (for example: 60% roadmap initiatives, 20% tech debt, 20% support/interrupt work), then use the portfolio tool to visualize whether reality matches…

One thing I'd add is that it's worth separating capacity planning from sprint commitment. Plans is great for asking "When can this work be delivered?" across teams and releases. Sprint Planning is more about "Can this team realistically commit to this work over the next two weeks?" We've found it works well to use Plans to…

I'd recommend agreeing on a single source of truth for deliverables, then using Jira only to reference it. For example: Confluence for living documents (requirements, user guides, runbooks, etc.). SharePoint/OneDrive/Google Drive for Office files like PowerPoint or Excel that need collaboration and version history. Jira…

Thanks Luis, I used to do async at one of my previous companies and I enjoyed it, so much more efficient that way. But the sync standup is engrained in the company's culture, not much I can do about that. 

I agree, this is pretty much my take on it as well, thanks for replying @Ilia Fainshtroy 

Congrats @Koval_ Yuliya 

That's a solid improvement, did you get much help from ai coding agents on this, I'm curious how good they are when it comes to frontend performance tasks

I'm actually good friends with past coworkers, however I see a trend, my past coworker friends are all from the beginning of my career.

I like Inline control over related work, it saves me from having to open up a new tab with the issues 

Unfortunately, issue numbers are allocated from the destination project's sequence, so there's no supported way to preserve KEYA-123 as KEYB-123 during a move. One thing I'd add is to think about who actually consumes those issue keys. If they're referenced in reports or external systems, it can be worth introducing an…

I really like the direction of this. One thing I've learned is that people rarely struggle because they don't know a feature exists, they struggle because they don't know how someone actually uses it in their day-to-day work.

One thing I've noticed is that Jira rarely becomes difficult because of the current configuration, it becomes difficult because of the history of configuration.

One thing I'd love to see is a proper test mode for SLA changes. Before publishing, let me run a few existing tickets through the new configuration and see exactly which goals would apply, when the timer starts/stops, and why. It would make refactoring complex SLAs much less risky.

like @Dave Mathijs said I'd definitely like users to see who owns the space/project, project roles, board admins, workflows (read-only), and configured fields. Those are the questions admins answer over and over. What I'd keep hidden are implementation details like permission schemes, notification schemes, automation…

great detailed breakdown of what's blocked vs. what isn't. That's the part most admins will care about when planning a migration window.

Admin-controlled allowlists would feel like a good middle ground. Users get a smooth experience with approved tools, while companies keep governance where it belongs.

I'd love a proper 'Configuration Health' view that shows last used, dependencies, and confidence that something is safe to archive. Cleaning up Jira shouldn't feel like defusing a bomb.

I hadn't thought about it from the Enterprise admin side, but that's a really good point. The intent is probably to reduce friction for new users, but at enterprise scale it creates fragmentation instead.

Resolution is one of those concepts that makes perfect sense once you know Jira... and confuses almost everyone before that. Restricting it to terminal statuses would probably eliminate a huge percentage of support questions.

good call, duplicate names might be manageable with 20 fields, but with hundreds they make automation, JQL and reporting much harder to maintain @Matt Doar love your idea of a warning

One thing I've noticed is that retrospectives and incident reviews are gold mines for KCS. If an action item or workaround keeps coming up, that's usually a signal the knowledge should be captured instead of rediscovered every sprint. Making knowledge capture part of the team's normal workflow is the hard part, though

nice write-up, really like the idea of treating identity as a shared infra piece, identity mapping across multiple systems can be a really tough challenge sometimes, and don't even get me started on Entra ID 😂

solid addition, especially for teams relying on comments. the automation support is awesome, it will allow some cool workflows 

Great to see continued investment in Data Center.

I would say summer: things are busy, there's plenty of growth happening, it feels like the season where everything pays off