Sami Shaik Success Champion

@Bree Polk-Bauman , @Matthew Sinclair has the visibility model right, and it is the reason there is no setting for what you want: a customer sees a request on the portal when they are its reporter, a request participant, or a member of an organization it is shared with. Your migration is writing the real users into the…

@Mathew Lederman , @Christopher Yen Slack route is the best one for desks whose users live in Slack, and it is worth crediting because it removes the two things that kill response rates: the channel switch and the login. If your users are on email, here is what I would check and change inside JSM before buying anything,…

@Venkat Jira Admin , the boundary first, then the two designs that get both of your requirements. The boundary: the customer's request page on the portal shows the fields that were on the Request form at creation, and nothing else. There is no "show after creation" switch on a Jira field. If the field is on the form, the…

@joao zampa , @Matteo Vecchiato is right that no network block holds, and it is worth saying why, because the reason also tells you what does work outside Enterprise. Why the network layer cannot do it: site creation is not a single endpoint you can deny. It runs through Atlassian's own signup and start surfaces on…

@James_Noble , you are on the right route, because there is no shortcut: component lead is not exposed as a smart value ({{issue.components.lead}} renders empty; the request to add it is JRACLOUD-76851), so a Send web request to the component endpoint is how every working version of this rule does it. Your two 404s point…

@Sara Beyer , @Sebastian Krzewiński is right that there is no per-issue-type switch, and the reason is worth knowing because it tells you where the lock can go: Rank is not a field with its own permission, it rides on the Schedule Issues permission (together with Edit Issues) in the project's permission scheme. Atlassian's…

@joris raffin , your isolation is already good enough to point at the mechanism, and Duc's test narrowed it further: the old endpoint returning the same empty set means this is not /search/jql specific, it is how the stored filter's JQL is resolved when referenced by ID, which is a different code path from parsing JQL you…

@s_gridnevskii , That is a better shape than mine and I will take it: a smart-value conditional inside one component costs no step, where an if/else component costs one plus whatever runs inside it. {{#if(webResponse.body.match("pattern"))}}...{{/}} collapses the branch into the action that was going to run anyway, and…

@Monique vdB , thank you for answering all four, and for doing it before the freeze rather than after. The one that mattered most to me was the second: accepted solutions and accepted-answer counts carrying over means the record people have built here stays theirs on the new platform, and knowing that in advance is exactly…

@Anne Saunders , thank you, this is the comment the post needed, and you are right in a way that changes the headline for most readers: IP allowlisting is a Premium and Enterprise control, so on Standard and Free the token door has no network guard at all. The domain list never sees token traffic, and the one preventive…

@Ryan Hormann , @Trudy P Claspill has the two documents that settle it, so just the direct form of the answer to your "once, per trigger, or other": Per execution of the action, not once and not per trigger. Enabling the rule costs nothing. Each time the rule runs and reaches the Use Rovo component, that is one billable…

@Chris Green , you have already eliminated the easy answers, so let me name the mechanism that kills them and then the two routes that survive it. Why every Confluence-side route fails: the portal reader is, in most cases, a portal-only customer with no Confluence licence. The article they see is the Confluence page…

@Nicolás Diego Apolonia , with @Dávid Sass-Kovács and @ben reports the thread now has enough evidence to stop diagnosing your setup and name the pattern: * OAuth 2.1 to /v2/mcp fails; API token to the v1 and Bitbucket paths keeps working, on the same accounts, at the same time. * Every client behaves the same: ChatGPT,…

@Viswanathan Ramachandran , thank you, and the redirect-origin explanation is the sentence the post was missing: OAuth 2.1 has a browser redirect to a domain Atlassian can check, a token in a request header has nothing to check against, so the domain list was never able to see that traffic. That is why I would rather…

@s_gridnevskii , Correct, and it is the cleanest example of the gap: in Data Center a scripted post function did the transition-bound work for free, and in Cloud the built-in post functions are a fixed short list. The Cloud equivalent is a Forge app that registers a workflow post function, which runs on Forge invocation…

@Becker_ Rene , no apology needed; the vocabulary collision is Atlassian's, since "flow" is the new name for a rule and "workflow" kept its old meaning. With the correction, your design reads differently and I agree with it: trigger plus Send web request is the cheapest shape there is, two steps per event, and everything…

Glad it was the Re-fetch step, @Liza Gonzalez , that race is silent in the audit log, so it is the first thing I check on any "Work item created" rule that reads a field. If the three boards ever outgrow the routing rule, the first-column mapping is there as the no-rule fallback. Thanks for closing the loop, and credit to…

@Siimon Härm , thanks for the accept, and the "cannot select the right board" moment usually has one of two causes. 1. The form is by product, not by topic. Go to support.atlassian.com/contact, choose Technical issues and bugs, then the product is Confluence (the cloud one, not Data Center), then your site from the list.…

@Becker_ Rene , you are right that Log action counts; it is an action component like any other, so a rule that logs at every step doubles its own cost for the privilege of being debuggable. Two practical answers: log only inside failure branches and error paths, and strip the logs out once a rule has been stable for a…

@Rafa , the discrepancy you describe is worth chasing rather than shrugging at, because the two pages you are comparing are not the same meter. /jira/settings/automation#/tab/usage is the space-level view for one Jira space's rules; the notification that says 5,000 with 80 left is the organisation meter in Atlassian…

@s_gridnevskii , Post functions are not metered, so the instinct is right for one class of rule: anything that only ever fires on a transition (set a field, assign, clear a value, add a comment) belongs in the workflow, and moving those out of automation is the cleanest step reduction there is. Two limits worth keeping in…

@Maria Reisinger _MetaFrazo_ , both points are sharper than anything in the article, and the second one is a deadline I had not put together: the automation audit log keeps 90 days, so a chain that doubled the count in December is unreconstructable by March. That makes the December read of Performance insights an artefact…

@Darryl St_ Pierre , @Scott Boisvert has the right call, and I want to add why it is needed and a design that keeps it out of every rule you write. Why the form cannot just read the profile. Automation's user smart values expose exactly six things: accountId, active, avatar URLs, displayName, emailAddress and timeZone…

@Patrice Champet , good question, and it is the one the RBAC rollout leaves for admins to answer on their own, because app access is where the "role equals a bundle of permissions" model meets a user that is not a person. What I have landed on: one custom role per app purpose, never a standard role, and never one role for…

@Dayna Portillo , @Gor Greyan has the principle right and I want to add the source and the two cases it does not cover, because the difference between "I think" and "the doc says" matters when you are budgeting for December. The unit is the component that executes, not the criteria inside it. Atlassian's definition: a step…

@Chris Milton , the issue security scheme everyone has pointed you at controls what the external user can see; your question is what they can manage, and that depends on something nobody has asked yet: what kind of external user this is. There are three, and the answer is different for each. 1. A JSM portal customer (free,…

@Pavan Kumar Pinniboyina , you have three answers that each hold one piece of the rule, so let me put the pieces together from Atlassian's current guest documentation (updated May 2026), because they are all in force at the same time. Guests are free, up to 5 guests per paid user. @Tomislav Tobijas has this exactly. The…

@Jose Cordero Velez , @Arkadiusz Wroblewski pointed you at the right page, so let me spell out what it does not say plainly, because it is the part that confuses everyone the first time. Canned response variables are a fixed short list, not smart values. You cannot type {{issue.summary}} or {{reporter.displayName}} into a…

@Hugo Mora , all four go straight into the runbook, and the pagination one is the trap I would have walked into: a two-thirds snapshot that diffs cleanly against another two-thirds snapshot is worse than no snapshot, because it looks complete. Asserting the returned total against the collected count and failing loudly is…

@Siimon Härm , @Arkadiusz Wroblewski is right that this goes to Support, and @Mihai_LeanZero has the one tracked piece (CONFCLOUD-80330 explains why the Child pages macro skipped the folder level). Two things to add so the ticket lands as a bug rather than a how-to, and one documented cause to rule out first. Rule out…