Sami Shaik Success Champion

@BGajula on the second question, the structure and the content are two different mechanisms, and that decides the approach. The configuration comes from a template. Custom space templates capture Boards, Work types, Fields, Workflows, Roles, Notifications, Permissions, Shortcuts and Issue Security from a source space. They…

@Dieter Lauwers I cannot speak to intent, but the IDs are resolvable today with two more exports, and the gaps you are seeing are already on Atlassian’s public tracker. Resolving the user IDs. The actor column is the Atlassian account ID. Export the directory from Atlassian Administration > Directory > Users > Export…

Hi @Colin Maughan “Atlassian is installed” on the GitHub side only tells you the GitHub App exists in that organisation. It does not tell you that org B is connected to this Jira site, and that connection is what the configuration page lists. Three things cause exactly your symptom, in the order I would check them. 1. The…

@Dwight Holman @Dwight Holman thanks for reporting it here . Two things I can say with sources, and one I cannot. There is no per-element switch today. On the GA thread, Dhruv Mittal (Atlassian Team) answered this class of question on 14 October: “currently all the changes are bundled together. You can still chose to…

@Christian B. no, there is no charge for displaying or editing a work item, and this is not an AI feature. The meter counts executed automation steps only. From Atlassian’s usage page, re-read today: “An automation step is a single executed part of an automation flow.” Triggers, conditions, actions, branches and loops…

Hi @KC Wong , The single email is possible, and you do not need a loop. Automation builds the list for you. The rule Trigger: Scheduled, monthly, with “Run a JQL search and execute actions for each work item” left unticked. You want one run, not one per item. Action: Lookup work items with your JQL, for example: project =…

@Pavithra Sivaprakasam the fastest route for those two is a support request from your site admin at https://support.atlassian.com/contact/ (product: Rovo), quoting the v2 endpoint and asking for the documented access and refresh token lifetimes and whether prompt=consent is required or honoured. Neither value is published,…

@sankalp.khare good, and thanks for posting what you did. For anyone reading later, the two routes differ in one way worth knowing: a custom field holds a value per work item, so it needs something to set it on every request (a request type default or an automation rule) and it drifts when a request type moves portals; a…

@William Gunkel the reaction will depend on whether anyone looks at the meter before 3 December, which is when extra usage billing takes effect according to Atlassian’s usage page. For the two clients you mention, four things done in an hour each will decide whether this is a non-event or a surprise invoice: Read the meter…

@Pavithra Sivaprakasam @Arkadiusz Wroblewski table is right; here is where those values come from, which answers your “supported alternative to calling the endpoint by hand” question and will save you the next migration. 1. Discover, do not copy. v2 publishes standard OAuth metadata, read today: Protected resource:…

@sankalp.khare thank you for marking it. One favour in return: when the queues are live, could you post here whether the queue built on requestTypesInGroup shows the work items for an agent who is not a space admin? That was the part of JSDCLOUD-15966 that bit people in early 2025, and a confirmation from a production site…

@sankalp.khare , @Ciro is right that portal groups have no JQL, but there is a second grouping in service spaces that does: request type groups. They are a separate field from portal groups (on the Request types screen they are two different columns and two different filters), and Atlassian documents a JQL function for…

@Testing the error text tells you which endpoint you are hitting, and it is not the one @Andrea Robbins assumed (her notes are correct for request creation, which has its own rules). “User does not have permission to create customer accounts” is the 403 from POST /jsm/csm/cloudid/{cloudId}/api/v1/customer (Create customer…

@Ash Young thanks for the two pages. I read the role comparison table on “What are app roles in Jira Service Management” and it answers James Clark’s question precisely: App admin is Yes on every app-level row (settings, usage, user management, audit logs, compliance, email, authentication, customer organizations,…

@Germán Morales makes the right call on scope; the steps below are for finding the page when you need to know which one it was. @Nico Maikranz that error means the account the rule runs as (the Actor in the rule’s Settings) could not read the page that fired the “Page edited” trigger. Nothing after the trigger runs, which…

@Rudresh Singh that dialog is a plain list of the sites in the organisation you are administering, so “No options” means the admin portal does not see a site in this organisation that qualifies, rather than a missing Studio setting. Checked this morning on an organisation where Rovo is active: Atlassian Administration > AI…

@Zheng, Rox there is no separate published range for mcp.atlassian.com, so here is what you can actually give your firewall team. 1. The official source is the machine-readable list, not a fixed set of addresses. Atlassian publishes all of its ranges at https://ip-ranges.atlassian.com (JSON). The feed generated on 27…

@Maksym Mishchenko yes, five separate condition steps can cost more than one JQL condition, with one important nuance. Atlassian’s definition on the usage page is that a step is “a single executed part of an automation flow, including triggers, conditions, actions, branches, and loops”. The word that matters is executed.…

@Fabio Peruzzo good questions, and the short answer today is no on all three, with one workaround. Approval status as a smart value: the Confluence automation smart values page lists content properties such as {{page.status}}, {{priorContentStatus}}, {{page.state}}, labels, owner and classification, and nothing for…

Thanks @Srini Chakravarthy for the response. It would significantly enhance the flexibility and extensibility of the new Jira Service Management (JSM) interface if Atlassian enabled Forge global pages to be integrated directly within custom pages. Expanding support for Forge modules in this area would allow developers to…

Thanks for sharing this. Quick Question: Custom pages, can you explain us more what can we do in the custom pages? Can we host forge global pages in the custom pages?

@Fabian Aguilar thank you, the Marketplace API flag on the latest cloud version is a useful third signal alongside the badge and the vendor, with the caveat you repeated: it describes the vendor’s latest version, not necessarily the one installed on a given site. Readers should treat any catalogue-wide count as one…

@Snehal Shah thank you for the clear answer on all three points: no pre-warnings, size display or size API for now, with usage tracked; the same non-destructive cleanup for migrated Data Center work items (comments without custom permissions zipped into an attachment such as comments.zip, the item editable again); and the…

@Marc -Devoteam- is right, and I was wrong on the first point. I quoted the request-form page, which says mandatory system fields such as Summary cannot be hidden; on a request type today the Summary field does offer Use preset value and hide from portal with a value box, and it saves. I checked it on a sandbox this…

@Dhruv Mittal one more from day four, reported by @Andrew Tagg on my checklist thread with screenshots and reproduced on my site: the Atlassian Intelligence dropdown (Improve work item) that sat on the classic view is not visible on the new work item view. Has it moved somewhere we are not finding, is it rolling out…

@Andrew Tagg thank you for the before and after screenshots; that is exactly the kind of day-three report this checklist was asking for. I can reproduce it on my site: in the new view there is no Atlassian Intelligence (Improve work item) dropdown where the classic view had it. I have added it to the open-questions list in…

Glad it works @Heinrich Bärhausen , and thank you for coming back to confirm; that is what makes the thread useful to the next person who migrates and hits the same list. @Gabriela - LeanZero , thank you for rebuilding it on a test site. Your point about .last is the better rule: when the clone carries the old sprints…

@M, Short update for anyone landing here later: I asked the Community team whether the non-customer route (security@atlassian.com) could be documented on the Report a Vulnerability page. Their answer (20 Oct): that page belongs to Atlassian’s Product Security and Trust team, and the recommendation has been passed to them.…

@Dhruv Mittal three things from day three on the new view , following your 14 Oct answers. 1. Manually triggered rules now sit at the bottom of the page. In the classic view the automation (lightning) icon was at the top of the work item, one click away. In the new view, manually triggered rules live inside the Automation…

Hello @Keval Rana (CTR) , Short answer: you cannot hide Summary or give it a preset value on a request form. Atlassian’s request type docs say it directly: “Mandatory system fields, such as the Summary field, cannot be removed or hidden, because they are essential for work item creation and processing. However, you can…