Sami Shaik Success Champion

@Peters, Loes (Lloyds Bank - Nederland) , The thread has the pieces right: classic page not live doc ( @Marc -Devoteam-, @Numeric Oasis, @James Gamble, @Abaho Katabarwa (Katabarwa Labs)), native Approvals on Premium and Enterprise ( @Tomislav Tobijas), and the open tickets. The one layer still missing is the one your…

Update, 6 October 2026. Today is the stated start date, and on my own site the slash menu still shows the ten legacy categories as I write this (Formatting, Confluence content, Media, Visuals and images, Navigation, External content, Reporting, Development, plus Rovo). The Insert modal shows the same, which is expected:…

@Mia Tamm _Simpleasyty_ Thank you. The routine was the point. A list of things to monitor is what the old weekly page already was, and your comment on the first piece named why that was never enough: the filter has to belong to the person who knows the site. One update now that the weekly page has actually stopped. The…

@Yagnik Satani , Thank you for closing the loop, and for the second confirmation that the preview panel reproduces it with no host-page code loaded. That one sentence is what turns this from a configuration question into a defect report, and it will be the sentence Support acts on. One practical tip while the ticket is…

@Becker_ Rene , This is the most useful comment this article has received, and it has had good ones. Thank you for coming back two months later with the full field report. Three things in it deserve pulling out for anyone reading past the fold. The versioned exports. Export before and after every bulk change, keep every…

@David Ho , the three replies above are each right about one possible cause, so here is the order to test them in, because one check splits the list in half. First, ask your org admin for one thing: the audit log. Every call that reaches the Atlassian MCP server is recorded in Atlassian Administration → Insights → Audit…

One setting sits underneath all three replies, and it is the one to change first, because it prevents the share rather than undoing it. The KB Trudy linked says plainly that the Share With field and the +Share button cannot be hidden, and then gives the control that decides what the field is set to by default: Atlassian…

@Jason Hills , the write-up is up, with your observation as the framing and a correction I owe you: the Forge rovo:mcp control is off by default per installation, not a single global switch.

@Nagarajan Balasubramanian , thank you. When Gamma answers the retention and training questions, please post their reply here, even in summary; this thread is already the first search result for the integration, and their half next to the Atlassian half would make it the complete reference.

@Jason Hills , that is the finding, and you have named the gap precisely: the pages that say "no AI" are measuring different things from the pages that say "AI is reachable." Rovo Overview's "Users with AI enabled" and the Rovo Access blocklist govern the in-product Rovo features (Chat, Search, Agents) per user. The MCP…

@Monique vdB & @Mohammed Shakhib , a dated data point on the profile-stats recalculation. My profile today (4 October) shows 27 answers, 2 accepted solutions, 15 likes, 59 total posts, Insider badge. The 2 accepted solutions are exactly the two accepts I have received since the relaunch; the 23 accepted solutions shown on…

Thank you for checking the ticket. Atlassian's current CSAT troubleshooting KB still names JSDCLOUD-4038 as the tracking issue for the resolution-set-twice case, which is where I took it from; if the ticket is closed as Cannot Reproduce, the KB is behind the tracker and the symptom in the KB still stands. For the…

@Jason Hills , Thank you for being first, and your line "it is not transparent whether our initial settings were upheld" is the whole issue in one sentence. One concrete thing you can do on Monday: the Data security policy row and the Rovo MCP server pages both show "Updated by" and a date, so you can establish whether…

Thank you, @Betty Sheu , that settles it: Enterprise auto-enrolled now, GA in Q1 2027, and the roadmap is showing the GA date rather than the beta. Admins reading both pages will understand the difference now.

@Jason Wong , thank you, that answers all three cleanly, and the pointer to the stable account ID is the key fact. The governance implications I had in mind are three, all on the Host side: (1) Audit trail identity. If a Host renames an external user, the Host's audit log and page histories will carry the local name while…

@Fabio Santos , the three replies above cover the switches; here are the two "how can this be verified" questions you asked, plus the order I would run everything in. Verifying the account type. In the JSM project, Customers: a portal-only account shows the email with no Atlassian avatar or display-name link, and the row…

@stephen.edwards , @Martin Runge mirror rule is the right way to build the trail, and one fact underneath it explains why the sends stopped silently last time and how to catch it next time: there is no separate "CSAT send." The rating scale is embedded in the Request resolved customer notification, so the survey goes out…

Update, 2 October: the weekly page has stopped as announced. The last edition published covers 21 to 28 September, and there is no edition for this week. From here, What's new across Atlassian is the source; the fifteen-minute routine for reading it is in the follow-up article linked above.

Thank you @Betty Sheu , that is the list admins needed, and the Enterprise-only scope explains a few threads I have seen this week. One question still open from my first comment: Performance Insights is "open beta" in the digest and "Coming soon, Q1 2027" on the public Cloud Roadmap. Which is current, and where does an org…

@Asier Vadillo , thank you for coming back with the filter and project-type details; that ruled out the permission path cleanly, and @Stephen.Lugton and @Calvin had the right read: the settings sidebar was collapsed, not missing. Good catch, and a useful one for the next person who searches this title, because the symptom…

@Sawan Talwar , @Josh reading is right in general, and there is a specific, documented Atlassian path for exactly this, which answers both your questions. The grant is JWT bearer. Atlassian's own engineering write-up of their XAA implementation describes the flow as: the client exchanges its identity assertion with the IdP…

@Asier Vadillo , the screenshots have not rendered for me, so two checks in order of likelihood, because "General only" is almost always the second gate rather than the first. 1. Board admin is only half the permission; the board's filter is the other half. A board is a view over a saved filter, and Jira will only let…

@Hugo Mora , an honest update on the capture I promised on 8 September: it has not happened yet, and I would rather say so than let the thread imply it is coming next week. The reason is simple: the Field Schemes rollout has started reaching sites in stages, so a before-and-after taken now would compare one site's…

@Yagnik Satani , that is a complete defect report, and reproducing it in Atlassian's own preview panel is what makes it one; there is nothing left for you to rule out. Straight answers to your three questions as of today: 1. Known defect? I cannot find a public ticket for it on jira.atlassian.com, so treat it as unreported…

@Jason Wong , thank you for the billing clarity; "the Home organisation is never billed for a Host invitation" is the sentence admins have been asking for. Three questions from the org-admin side that the post leaves open: Scope of "limited basis." Is local profiles enabled per organisation, per plan, or by region, and…

@Nagarajan Balasubramanian , @Matthew Sinclair is right that questions 2 and 3 are Gamma's to answer, and only their terms, security documentation and your own vendor review can answer them; nothing on the Atlassian side can tell you what a third party retains or trains on. But questions 1, 4 and 5 have an Atlassian-side…

@Mia Tamm _Simpleasyty_ , agreed, and the platform-and-API bucket is the one that turns into an incident with nobody's name on it, which is why it went into the follow-up article as the third question and why the developer changelog gets a monthly skim of its own. Thank you for sharpening it twice.

@Lori Brown , I will not argue with the support view, because it is right: the person building a rule in the product UI should not need to know which of three engines meters what. Two things I can offer instead of agreement. First, the practical one: the split I described costs a Jira admin about an hour once per site, not…

@Josh , agreed on the split, and one number to fix so @Davide Cioranu does not test the wrong thing: the agent port is 51337, not 5137 (Atlassian's system requirements page: Discovery outgoing TCP 51337, agent inbound TCP 51337, configurable in discovery.cfg). Davide, that is the port for the Test-NetConnection .

@Betty Sheu , thank you for the digest. Two questions an org admin will have on reading it, and both would make the next one sharper: Performance Insights. The digest says open beta; the public Cloud Roadmap currently lists Performance Insights as "Coming soon, Q1 2027" for Jira and Confluence. Which is current, and if the…