Sami Shaik Success Champion

@Richard, Thanks for the detailed follow-up, and you are right to rule out versions: purging the page removes every version of its attachments, and purging the trashed spaces removes theirs. Three days is well past the four-hour refresh window, so the snapshot explanation is spent. What is left is to measure the site…

@Arkadiusz Wroblewski , thank you, and you are right. I re-read the Set up your virtual service agent page this morning and it says it plainly: “Rovo agents are currently only available in Jira Service Management portals for Atlassian Accounts.” So the portal-only customer route in my answer does not work for a Rovo agent…

@Jeff Gibson , Glad it helped, and thanks for marking it. One thing worth taking into the conversation with your Cyber team: the connector’s permission list on Atlassian’s page is the document to put in front of them, because it is the list Entra will show them at consent time. If the outcome is “Assist only” for now, that…

Hello @Johnny Gonçalves , Welcome. Good news: all ten items are covered natively in Jira Cloud plus Confluence Cloud, with one caveat on BI that depends on your plan. One heads-up before you start a trial: Jira Cloud now calls projects spaces in the UI and docs (same thing, renamed in late 2025), so the menus will say…

M, The link you want is not the forum and not the general support page. It is Atlassian’s Report a Vulnerability page, which gives two routes that work without being a customer: A “Security Concern” ticket through support.atlassian.com/contact. Pick the security concern option rather than a product; if the form asks you to…

@alfredo.murguia , @Matthew Sinclair & @Arkadiusz Wroblewski are right on the first half: enforced SAML SSO is an Atlassian Guard Standard control (or included in Enterprise), and there is no way round that. The half nobody has answered is the one that matters to your finance team: you do not have to pay for everyone. How…

@Tomas Greif , Thanks for coming back with the result, and for the correction: the expression I gave was wrong for JPD. A JPD Date field is not a plain date underneath; it is stored as a start and end pair, which is why {{now.jiraDate}} into the field did nothing and why your JSON object worked. For anyone finding this…

@Jeff Gibson , @Josh has the split exactly right, and it is worth being precise on the one question you actually asked, because your security team will ask it too. What Chat.Read.All grants. It is an Application permission, not a delegated one. That means the Atlassian connector reads with its own app identity, with no…

@Louis Serio , Matthew’s pointer is the right starting line. Here is the rest of the route, from the vendor-review side of the table. 1. Get everything Atlassian already publishes before you ask anyone. All of it is self-service on the Customer Trust Portal once you accept the NDA by entering your email: the SOC 2 Type II…

@Richard, Two things are going on, and the first one may already have solved it. 1. The number you are reading is up to four hours old. Atlassian’s storage page says the storage figures “are refreshed every 4 hours”. You purged the page and read the overview straight after; 2.1 GB is very likely the previous snapshot.…

@nboreddy , Short version: in a company-managed Cloud project there is no native switch that hides a work type from Create while keeping it in the scheme. The only thing that removes it from the dropdown is removing it from the work type scheme, and Atlassian’s scheme docs are explicit that you “will be automatically…

@Myles Boyd , The reason it answers you with internal articles is not the test account, it is the agent’s identity setting. By default an agent runs as User’s account, and Atlassian’s agent identity page is explicit: “If the agent adopts a user’s account, then the agent can access whatever that user can.” Test it as a site…

Glad it held up, @Vikrant Yadav, and thanks for confirming in the thread. One thing to watch after a few weeks: the reminder labels will accumulate on closed tickets. A rule on transition to Done that removes reminder-1 and reminder-2 keeps the label list clean for everyone else’s JQL.

Thanks for accepting, @Frank Fu , and for the detail. Two parts. Is the Free plan the cause? Not according to anything Atlassian publishes. The automation actions reference gives Free one email limit, 100 emails in 24 hours, and Explore Jira Cloud plans gives Jira Free 150 automation steps per month. Hitting the step…

@Michael Bibby , Thanks for testing it, and I owe you a correction. I flagged the blank-URL idea as unconfirmed, and your result settles it: do not leave the base URL fields blank. Atlassian’s own Okta setup guide (step 7) fills all three: Jira Base URL https://yoursite.atlassian.net, Confluence Base URL the same with…

@Nicolas Mylle , @Matthew Sinclair & @Ismail Bin Ibrahim have the two gates (a signed BAA, and an eligible paid plan with org admin rights). Three things from the docs that would narrow it further before you open the Support ticket: Check each product's plan separately. Eligibility is Standard, Premium or Enterprise for…

@Frank Fu , @Matthew Sinclair and @Ballon Apps have the two checks that matter (the smart value, and the recipient's email visibility). One thing explains your other symptom, "I cannot manually enter an email address": You are on the deprecated action. Atlassian's automation actions reference marks Send email as deprecated…

@Roderick , Two things to add to @Matthew Sinclair and @Josh answers, because they settle your questions 1 and 2. 1. Your Date field is already a range, just not an arbitrary one. Under the hood a JPD Date value is stored as a start and end pair, {"start":"2026-10-01","end":"2026-10-31"}, which is why Josh's precision…

@paul.price , Thanks for marking it, Paul. If the per-group order ever drifts again after a Save, a screenshot of the Manage queues dialog is the thing to post.

@Yagnik Satani , That is a clean reproduction, Yagnik. A brand-new space, one plain-text intent, Atlassian's own built-in greeting failing in both the preview and a blank-page embed, with valid ADF on the wire rules out everything on your side. Support cannot ask you for anything you have not already given them. One note…

@Donna Bates , Glad it was that simple in the end, Donna. For the record, the sandbox test you ran is exactly the right proof: a ticket created after hours with the clock not running means the goal is now on the calendar your users expect. Two things before you promote it: Make the same calendar change in production, all…

@Ilya Vinogradsky , Your site is almost certainly fine. The diagnosis your agent produced is built on a field type that does not exist on Jira Cloud, and Matthew's instinct was right to question it. What the endpoint actually wants. Per the Create customer request reference, POST /rest/servicedeskapi/request takes three…

@Vikrant Yadav , @Sagar Mahajan and @Anwesha Pan have the shape right (two scheduled rules). Two details in your requirement break the simple versions, so here is the build that survives them. Problem 1: the reminder resets its own clock. If the rule posts a comment, updated moves, and the second rule (day 5) never…

@Tomas Greif , There is no built-in "moved to Done" column in a JPD view, so the clean fix is to make one and let automation fill it. Two rules and a field, ten minutes. 1. Create the field. In the space, add a Date field called Done on (Fields panel, Create field, Date). Add it as a column to your "recently done" views…

@Michael Bibby , Two separate things are tangled in "one tile", and splitting them is the whole answer. 1. The SSO and SCIM app is not your tile; it is your plumbing. Set up the Okta Atlassian Cloud application the way Atlassian's Okta SAML guide describes: verified domain, Atlassian Guard Standard, the SAML wizard under…

@paul.price , Probably not broken, and probably not you either. JSM keeps two different queue orders, and they do not sync. The Queues tab order (Queue settings, Queues tab, drag to reorder). This is the sequence agents see under View all queues, and it is the one most admins reach for first. The per-group order. Each…

@Mohammed Shakhib , Closing the loop on my 4 October question about the profile counters, with a dated data point for the record. 6 October, profile page: Rising Star badge, 151 answers, 23 accepted solutions, 20 articles, 641 likes received, 341 total posts. Those are the exact figures from my 10 September pre-migration…

@Sawan Talwar The correction stands, and the accepted answer is wrong on that point. I checked the discovery document again today: https://auth.atlassian.com/.well-known/oauth-authorization-server returns "issuer": "https://auth.atlassian.com", the bare host, and your ID-JAG with that audience is accepted at the v1 authv2…

@Donna Bates , First, a correction to my own 28 September answer. I wrote that nothing in your calendar or goal configuration was wrong. That was wrong, and the evidence was in the goal table you posted. Look at the Calendar column: every Incident row (Highest, High, Medium, Low) is on "After Hours Calendar." Only the…

@Becker_ Rene , That answer changes the article, so thank you for checking. Three things worth pulling out. "None (remove access)" exists as a fallback. I had written the fallback section as a choice between roles. It is also a choice between failing open and failing closed. Collaborator by default fails open: anyone left…