Jayesh Raghuvanshi Expert

@Mark Carroll The "Your Atlassian Cloud site is currently unavailable" message for a site inactive for about a year strongly indicates deactivation rather than full deletion, especially for free plans where Atlassian automatically deactivates unused sites after 120 days of no activity (like logins or page views).…

@Checalomexico Your Confluence documents from months ago are likely unrecoverable if your site was on the Free plan, as Atlassian deactivates such sites after 120 days of inactivity and permanently deletes data after an additional 60 days (total 180 days). Paying for a subscription now won't restore them, since the…

There is option to see if queue visibliltiy is set to particlular group or open for all

@Alok Deo It is not possible to add a custom “Report a problem” link directly into the built‑in left sidebar of Jira Cloud projects on the Standard plan, and you also cannot control it to open in a new tab from there The project sidebar in Jira Cloud (the left menu inside a project) is not configurable for arbitrary custom…

@dzaidi Common root causes when an agent can open an issue by link but not see it in queues: No Jira Service Management license In User management, confirm the user has the Jira Service Management (JSM) application/license enabled.​ Not in the Service Desk Team role In the service project go to Project settings → People…

@Shruti Kulkarni JSM is useful if you also need a portal, customer approvals, or the polished Approve/Decline experience (including non‑licensed approvers via email/portal). For an internal Ops board on Jira Software Standard, a workflow‑plus‑groups model is usually sufficient and avoids adding JSM just for this use case…

@MidnightExe Use the app when you want live, interactive reports directly on Confluence Data Center pages (filters, pivots, charts, SQL-like joins, and in-page spreadsheets) so users consume and manipulate data without leaving Confluence or juggling Excel files/attachments. This “no media break” approach plus reusable…

@Camille Mallet Dans le nouvel assistant de création d’espace de Confluence Cloud, il n’est pas possible de définir votre propre modèle d’entreprise comme modèle par défaut ; seuls les types Collaboration, Base de connaissances et Personnalisé sont proposés. Pour homogénéiser les nouveaux espaces, mettez à jour le…

@Navira Zainab Direct iframe embedding of Confluence Cloud pages on your own website is generally blocked by Atlassian’s security headers (X-Frame-Options SAMEORIGIN and CSP frame-ancestors ‘self’), so a native “preview panel” via iframe isn’t reliable across pages or tenants. The workable pattern is to fetch page HTML via…

@Navira Zainab Yes—this can be delivered on Confluence Cloud today using an app-backed site with a custom subdomain, or via Jira Service Management’s Help Center custom domains; Atlassian is also rolling out native custom domains for Confluence Cloud in an early access program. The Sprinklr-style branded help portal you…

@Guro “Ready to test” is the workflow transition label being shown on the board card (transition name or its i18n title), not the status name, so status translations don’t affect it. In other words, that action comes from the transition configured in the workflow for those issues, which is why it appears in English while…

@Christian Tarzia Use the Original Estimate in seconds and add business days to Start Date; then set Due date with one calculation, not chained methods like divide(6h) which isn’t valid in Jira automation smart values. Also ensure Time tracking is enabled and the Time tracking field is on your create/edit screens,…

@Siva Kedari Veerla Here are the official Atlassian vendor docs you can use to set up test environments and validate Jira Cloud functionalities end to end https://developer.atlassian.com/cloud/jira/platform/getting-started-with-connect/ http://developer.atlassian.com/platform/forge/build-a-hello-world-app-in-jira/…

@Rémi Chemin This is a race condition: advanced branches edit the same field in parallel, so updates collide and some participants are lost; fix by doing a single bulk update (JSON add operations or one JSM REST call with all accountIds) instead of per-email edits inside the branch. Avoid setting the field via the basic…

@Pasi Vepsä You can migrate spaces between two Confluence Cloud sites using the built‑in “Export space (CSV)” plus “Import spaces” flow, or use a temporary Confluence Data Center as a bridge if you need to consolidate at larger scale; keep the Confluence that lives on the same site as your Jira to minimize broken Jira…

@VLAS1 The message “Your Confluence Cloud subscription has been deactivated due to inactivity, and the data will be permanently deleted soon” is Atlassian’s standard notice for a Free or inactive site that has crossed the inactivity threshold and entered the deletion timeline. Atlassian also cancels linked Marketplace app…

@David Soucie Scoped API tokens in Confluence Cloud only work via the Atlassian platform domain and require your site’s cloudId, so calling your site URL with a scoped token returns 403 even though an unscoped (classic) token works against the site URL. Use https://api.atlassian.com/ex/confluence/{cloudId}/… with Basic…

@Christopher Carvalho There’s no native “auto-create Organization by email domain” in Jira Service Management Cloud, but you can fully automate it with the JSM REST API (create Organization, attach it to the service project, add the reporter to it, and set the issue’s Organizations field) or use a marketplace SSO/Identity…

@Marcelo Viana de Siqueira No, there isn’t a native per–issue-type “Create” permission in Jira Data Center; the Create Issues permission applies to all issue types in the project. The supported built‑in workaround is to give the restricted issue type its own workflow and add a Permission validator on the Create transition…

@Sheri Seldes No—Advanced Branching is not needed for this single-select dropdown use case in Jira Cloud; use a “Field value changed” trigger with an If/else block to route a “Send Slack message” action to the correct channel based on the selected team Setup Steps * Trigger: Add “Field value changed” and monitor the Team…

@Christopher Carvalho Don’t use groups for portal customers in Jira Cloud; use Jira Service Management Organizations and auto-assign customers to their org by email domain, then restrict customer sharing to their own organization so they only see their company’s requests. You can optionally use automation to always add the…

@Jacob Beatty A 200 OK on the incoming webhook endpoint does not guarantee the rule fired; confirm execution in the rule’s audit log and ensure the secret token is passed correctly with each POST.​ Always validate using the audit log, not the HTTP status, when diagnosing incoming webhook triggers For Jira Cloud * Send the…

@Rene Fox Lee Jira Cloud is very likely preventing the extension’s UI from injecting or opening an overlay due to its security headers (CSP/sandbox) and/or recent editor DOM isolation patterns, rather than a fault in Harper itself, which runs fully on‑device and continues to work on other sites without network…

@Admova Set this up with an “Issue created” rule that checks “Issue type = Incident” and uses “Edit issue” to set Priority to the value(s) you want; automation can set the field but can’t change which priority options are shown on the create form itself. To actually restrict which priorities appear, use a Priority…

@MARCO ANTONIO TOTH Set up a Jira automation that triggers when a Story’s Fix Versions changes, branches to its Epic (Parent), and sets the Epic’s Fix Versions to match the Story’s value. This keeps the Epic aligned automatically whenever the Story is updated * Go to the project’s Automation (or Global automation if you…

@Dan Allenby Yes—but natively creating a Slack channel with Jira automation is only built in for Jira Service Management incidents, while Jira Software/Kanban use cases require calling Slack’s API via the Send web request action or posting to an existing channel via the Slack action after connecting the Slack app For…

I too have submitted the form, have done most of the automations in Jira DC but will love to do it on Cloud.

* We use Slack integrations for Alerts, people reach out to slack channel if Jira/Conf is not available * We use MS Teams for Internal Team Collaborations * We use Confluence for documentation

@Oliver Hilger Root cause: Product information lives in many spaces with inconsistent structure and no shared metadata/labels, so it can’t be auto-aggregated into a single public index safely for external audiences. Fix: Standardize a “Product overview” page with Content Properties + a common label per product, roll…