Mia Tamm _Simpleasyty_ Atlassian Partner

Thanks @Jason Wong that clears it up, and the docs update is really helpful. The distinction between global account data and local profile context is exactly what I was trying to understand.

Love seeing where you took this, @Sami Shaik, especially turning it into an actual routine rather than another list of things to monitor. The three-question filter is something I can genuinely see myself using. Thanks for the credit too 🙂

The part I’d love to see covered in this series is change intake. Sandboxes, release tracks and freeze windows are great once you know a change exists. The harder problem is making sure the right admin notices it early enough — across product release notes, developer changes, Marketplace apps and deprecations — and…

Hey @Tomislav Tobijas a manual “Sync progress” option would be really useful here. If someone has already completed the learning path, they shouldn’t need to repeat it just because the challenge was added later. It would also make the To Do list more useful: you could see what’s actually left to learn, without completed…

Hey @Jason Wong this is an interesting improvement for companies collaborating with a lot of partners. Since the account ID remains global while things like display name or job title can now be organization-specific, I'd be curious how that is represented in audit exports and events. Is the stable account ID always…

The context side looks really clean. One thing I'd be interested in from the admin side: when ChatGPT or Codex performs a write action back into Jira or Confluence, is there a clear way to identify that origin in the audit/history? Permissions are one half of the trust model; provenance becomes pretty important once these…

Hi @Andy Atkinson I wouldn't treat this purely as a prompting problem. If the request has three observable actions — add the comment, mention the person, attach the file — the useful outcome is knowing that all three actually happened, not getting a plausible answer from the agent. Better prompting can help, but reliable…

Hi @Anita Mahip I wouldn’t trust either signal on its own. “No one opened it for 90 days” tells you about visible usage, but not dependency. And “nothing references it in configuration” can miss content or workflows where the app is quietly doing its job. Before removing an app I’d want to answer four things: Is anyone…

Just finished all three modules 🙌 The biggest improvement for me is that it feels much more practical now. The walkthroughs and everyday scenarios make it easier to see where Rovo actually fits into normal work, instead of just learning a list of features. Nice refresh.

I think the last point is probably the key one here: once external customers are part of the workflow, JSM starts making more sense even if the process itself isn't really “ITSM”. The portal/customer model gives you that separation between customer-visible replies and internal collaboration without having to recreate it…

I’d probably add one more lens to your three: does this change something an app depends on? For me that would make the filter roughly: user-facing change, admin/configuration change, or platform/API dependency. The last bucket is usually the quiet one, nothing obvious changes for users today, but it can become the most…

The visual editor is definitely easier for day-to-day changes, but I think losing a compact/text representation is bigger than it looks. For complex workflows that view wasn't just another way to edit — it was also a debugging and audit tool. Even if the old text view doesn't come back, having some way to inspect the whole…

Hi @Elia Fratucello, the app password may be the issue here. Bitbucket Cloud stopped accepting app passwords for Git operations in June, so you’ll need an API token with repository read access for clone and pull, and write access for push. I’d first try cloning from a terminal, outside the VS Code extension, using the…

Hi @Brian Barnett, is the new email address already associated with another Atlassian account? That’s one thing I’d check first, though the error message doesn’t tell us for certain what’s failing. If the goal is to give another person access to the boards, I’d invite their own account to the relevant boards and Workspaces…

Hi @Jeremy Wood, I wouldn’t deactivate those Atlassian accounts if the people still need the JSM portal. Atlassian says a managed Trello user stops being billable for Guard Standard when they’re no longer a member of any Trello Workspaces. I’d check that first, including any personal Workspaces they may have created. You…

I'd add one thing to the checklist: take a baseline of the handful of dashboards people genuinely depend on before migrating them. Not just the gadget keys — capture the layout, filters and important configuration too. Knowing that every widget migrated is useful; being able to quickly check that the dashboard still…

I can see why that’s frustrating, @Dave Mathijs. Databases seem like a natural fit for the kind of structured information @Clara Vega _Simpleasyty_ is describing, but it’s hard to build a workflow around them when you’re still waiting for key capabilities to develop. I’d be curious which gap is the biggest blocker for you…

I like “human minutes per accepted outcome” a lot more than agent runs or credits consumed. I’d probably pair it with one quality signal though. Otherwise a team could make the metric look better simply by reviewing less. Reopens, rollbacks or defects after acceptance might be an interesting counterweight: less human…

The preview-before-apply + stale-state protection is the bit that stood out to me here. Bulk admin actions get dangerous very quickly when the UX optimises only for speed — showing exactly what will change, and refusing to overwrite something that changed meanwhile, feels like a very good default.

One rule I'd add: use spaces/projects for ownership, and components/labels for classification. Once labels start deciding who owns the work, which workflow applies or where people are supposed to look for it, the Jira structure gets difficult to understand very quickly. One work item, one owner — then use links, boards and…

One thing I'm curious about: how does BearQ distinguish a genuine regression from an intentional UI change between runs? If autonomous tests are going to keep adapting with the product, keeping that signal clean feels almost as important as generating the tests themselves.

Dashboard-wide filters! 🙌 Also really interested in how the Marketplace gadget migration evolves. There are some very sophisticated dashboards out there, so that transition is probably going to be just as important as the new charting experience itself.

Personal pin/reorder/hide without changing the view for everyone else 👏 Small detail, but I can see that removing a lot of the usual "can we change the issue layout?" discussions inside teams.

This feels like one of those admin features that isn't flashy but could save a surprising amount of time. Being able to go from "Confluence feels slow" to actual site-level data without immediately opening a support ticket is a pretty big improvement. I'm particularly curious to see how granular the Confluence diagnostics…

The dedicated Agent Accounts are probably the most interesting part of this for me. Separating an agent's permissions from the person who happened to configure the automation feels much easier to reason about, especially once companies start having a lot of these running.

This is a really useful change to call out. I suspect quite a few admins still have the old weekly page bookmarked and won't realise it has effectively been replaced until it stops updating. I actually like the move towards a continuous stream of release notes rather than a weekly batch. The challenge now is probably…

Congrats on 4,500! 🎉 For me, one of the most interesting things about Rovo is actually quite simple: reducing the amount of time spent looking for context across Jira and Confluence. Finding the right page, issue or decision is often harder than creating new content. AI becomes much more useful when it helps surface what…

Hi @Sabina Sequeira this makes sense, especially for such a privileged role. Having Organization Admin access explicitly assigned rather than implicitly inherited from group membership feels much clearer. One thing I’d be interested in is how this will work for larger organizations from an auditing/reconciliation…

Hi @Admin Mia here from Simpleasyty. Just to be transparent and respectful of the Community rules: I'm part of the team behind Simple Tables. What you're describing is actually a use case we support with the Confluence Content data source. You can create a table directly from the content already in a space, show fields…