Sami Shaik Success Champion

Hello @Liza Gonzalez , @Ajay _view26_ shape is the right one (one create transition, one initial status, a rule that routes), so let me go straight to why that rule usually fails, because "it isn't working" with that design has two common causes and both are silent. 1. The rule runs before the team field exists. A "Work…

@Neo Apps , @Mihai_LeanZero has the first half exactly right, with the doc quote: with extra usage off, hitting 100 percent stops every flow until your usage billing date, and that date is your subscription's date, not the first of the month. Let me take the second half of your question, whether to enable extra usage now,…

@Lucienne Flynn , thank you for adding this, because it changes the picture and I want to correct my earlier framing rather than leave it standing. I described @Olivia Makin and @Maree Milne reports as a one-off that cleared on its own. Yours is intermittent and per-user: two people viewing the same page at the same…

@Hugo Mora , this is the most useful thing anyone has posted on this thread, and I want to say why before I add to it. Every earlier answer, mine included, was about what to do after the tool reports; yours removes the dependency on the report altogether. If the before-state is in files, the optimiser's summary becomes a…

Hello @Said Bennaceur , good question, and the honest answer to "what does a mature JSM environment look like" is that it looks boring from the outside. The signs of maturity are things nobody screenshots: fewer request types than you started with, workflows an agent can explain in one sentence, and automation that nobody…

Hello @Vinay Kushvaha , one question decides this, so let me give you the check and both outcomes. Which Confluence are you on? Look at the URL when you are editing. If it is something.atlassian.net, you are on Cloud. If it is your own domain, and Administration, General configuration, System information shows a version…

Hello @MaxKorlaar , your instinct about the custom field is the right one to test first, and there is a quick way to prove or clear it. Why the form goes blank rather than erroring. The Teams create modal builds its form from the create screen for the site, space and work type you picked, through the same metadata Jira…

Thanks @Monique vdB, and good luck with the migration; ten years of content is not a small move. Four continuity questions from an admin's point of view, because a lot of us link to threads from internal documentation and change notices, and a lot of members' contribution history lives only here: * URLs. Will existing…

Hi @Claudia Renner , @Arkadiusz Wroblewski split is the right first question, and I would add the mechanism, because "only the owner gets an email" is usually not a delivery failure. Owners and followers get different emails. The owner receives a reminder on Friday to write the week's update. Followers receive a digest on…

@Olivia Makin , glad it cleared, and @Maree Milne , since you saw the same thing on the same day on a different site, that pattern matters: two sites, same symptom, same window, no page or macro change on either side, gone without anyone touching it. That is a service-side blip in the path the Jira macro uses to fetch…

Thanks @Mia Tamm _Simpleasyty_ , one refinement for @Carol Pretorius , prompted by re-reading the original post: the error Rovo returns is a 404, "The requested resource could not be found." That matters for the order of the checks. A data security policy blocking an AI read presents as a refusal (no access, cannot…

@Julia Foden , that is the sharpest example on this thread of why "unused in a space" is the wrong test, because your chaining field is not seasonal, it is transient by design: it holds a value for the length of one rule run and is empty at every other moment, so any snapshot, before or after migration, shows it as unused…

Thanks @Chris Adams , that changes the diagnosis, and I would rather narrow it than guess. If safe customer notifications is off and the same stripping happens in regular Jira spaces, which have no customer notification stream at all, then the compliance setting is not the cause, and nothing else in Atlassian's…

@Adithya Ramesh , thank you for turning it into a ticket, that is the outcome I was hoping for. I have added my experience on CLOUD-13019 in the shape we discussed (which app-owned configuration was silent in the pre-flight, and the three lines an admin would need to see: a per-app reference line in the pre-flight, a…

Hello @Caleb Rabbon , @Dan Breyen tracker search and the support route are right for a genuine hang, so let me add what the Services filter is actually doing, because in my experience that turns most of these into a two-minute configuration check rather than a ticket. What the filter resolves against. With "Filter by…

Hello @Mike Perera , your direct question first, because it has been left hanging: can Atlassian manually sync it? Not in the direction you mean, but there is one case where Support is exactly the right call, and the three-minute check below tells you which case you are in. Why "Atlassian can force a sync" is half wrong.…

Hello @Sveinung Solhaug , the thread has two opposite answers, so here is what Atlassian's documentation says, and then the rollout order that makes the answer safe either way. @Gabriela - LeanZero has it right: a default is not forward-only. Atlassian's definition of a default classification level is that it "applies to…

@Danny Daniel , @Gor Greyan and @SPHIOR "write the change down as you make it" both apply to rules too, so let me add the part that is specific to automation, because it explains why your rules need review after every refresh. Rules are not included in the production-to-sandbox copy. That is an open suggestion,…

Hello @Mic Wang , @Rudy Holtkamp is right, I will give you the exact mechanics behind his sentence, because I think it explains why your workflow attempts failed. Why it fails where you put it. The Approve and Decline buttons on the portal do not run workflow validators. So a validator on the approval transition itself…

Hello @Carol Pretorius , @Mia Tamm _Simpleasyty_ isolation is the right one, and your answer to it (Rovo in Confluence reads the page, Rovo in Jira resolves the link but fails on the content) points at a specific layer that "the page is unrestricted" does not cover, because it sits above page permissions. The first thing…

Hello @Tomi Sofowora , @joris raffin conclusion is right (there is no team scope on a token), so let me add the mechanism, because once you see it the fix is a role change rather than a workaround. Alert visibility in Operations follows team membership plus role, not a permission scheme. Atlassian's API reference states it…

Hello @klevenick2 , @James Gamble has the right layer (the form field key is your category; the work item's Attachments collection has no idea which field a file came from), so let me add the two conditions that make it work end to end, because the second one is where this usually breaks. 1. The smart values exist only on…

Hello @Chris Adams , direct answer first: no, there is no allowlist. Safe customer notifications is a site-wide compliance setting (Settings, then Apps, then Compliance settings under Jira Service Management) and it masks summary, description, comment and attachment content in every customer notification the site sends; it…

Hello @Melissa C , the condition is close, and it fails for one reason worth knowing because it bites everywhere in automation: when a Lookup work items action returns no rows, {{lookupIssues.size}} is empty (null), not 0. So {{#if(equals(lookupIssues.size,0))}} compares nothing to zero and is never true, and your "None"…

@Ben Dangelmayr _Dangel Studio_ , welcome, and thanks for being upfront about the app; that makes the point easier to take on its merits, and the merits are real. "Unused is a snapshot judgement about something that is not a snapshot property" is the best one-line summary of the seasonal-field risk on this thread. The…

Thanks @Keri Miriello , this is a real throughput win, and I would add one practitioner note for admins reading it: the most common bulkfetch call in the wild sends only issueIdsOrKeys and no fields, which means the default navigable set, which means it stays at 100. Nothing errors, nothing gets faster. So the first step…

Hi @Mic Wang , the Partner answer above is correct on the one thing that matters: the Approve button on the portal bypasses workflow validators, so you cannot force a field at the moment of approval. But that only rules out one design. The design that works moves the mandatory selection to before the approval step, and JSM…

Hi @Finn Witzenhausen , @Mia Tamm _Simpleasyty_ is right that "read everywhere, write only here" is the governance boundary everyone will need. The good news is that it already exists today, just not as an agent-level setting, and the agent-level version is on its way. Here is the model as Atlassian documents it, so you…

Thanks @Akhila RAMANAN , that confirmation narrows it down, and the no-admin constraint changes what you should do next rather than what the cause is. Two things you can check yourself, then one message to send your admin. What you can check without admin access: * Open the editor on a page you own and type / followed by…