Sami Shaik Success Champion

Hello @Darshan Panchal , Good question, and since nobody has taken it yet, here is an answer from the enterprise admin side of the fence, because that is where your adoption decision will actually be made. Is the pain real? Yes, but only in one of the two use cases. For the Atlassian Rovo MCP Server specifically: *…

Hi @Shivam Kadwade , @Vladislav Tsaregorodtsev has pointed you at the right area, and there is a level below "Top users" that gives you the complete picture you are after. The full per-user view: go to Atlassian Administration, then Insights, then Platform usage, and open Rovo credits. That page has three tabs: Usage…

Hello @Lleyam Bartholomew , @Trudy P Claspill is right that nobody here can act on your account, and support is the guaranteed path. But before you wait on a ticket, there are two self-service checks that resolve the most common versions of exactly this situation, and one reassurance you asked for. Check 1: are you signed…

Hello @Eric Pujo , @Gor Greyan has it right, and it is worth spelling out exactly why, because the boundary here is precise. Why the import cannot create checkboxes in the description: the interactive checkboxes you see in Jira descriptions are the native action items feature, created in the editor by typing [] followed by…

Hello @joao zampa , Great question, and you have already found the actual boundary: where a field lives is easy, where its data flows is the hard part. Here is the approach that works, split by how auditable each consumer really is. Question 1: yes, there is a programmatic way, and the piece you are missing is the JQL…

Hello @Chris Bezile , @Matteo Vecchiato has the certifications side well in hand, so let me answer your first question directly, the one still open: is it linked to me or to the company account? The honest answer: it is linked to the account, and because yours is a managed account, the account itself is controlled by your…

Hi @Luisa Di Domenico , @Jean Horn is right on the core point: you cannot pin Jira Cloud's outgoing calls to your own organization's IP, and her three alternatives are all workable architectures. But before you build a proxy or change direction, there is a simpler documented route worth putting in front of the other…

Hello @Gurinder Summan , @John Funk and @Marc -Devoteam- have identified the core of it: the two projects behave differently by design. Your Project 1 uses the classic Service Management template, where the Organizations concept auto-associates the reporter's organization. Your Project 2 uses the Customer Service…

Hello @Pricilla , @Ajay _view26_ has covered structure and the Rovo split well, so let me take your fourth question, the read-only and permission groups one, since nobody has touched it and it is the piece that decides whether this is safe to run unattended. The core mental model: the MCP connection never acts as "your…

Thanks for clarifying, @Tahir_Mohammed . Two different things control colour on the card, and it helps to name them separately. The Card colors setting we described renders as a thin coloured strip on the left edge of each card, and that strip is what changes automatically with status via the Query rules. The cover is the…

Thank you, @__ Jimi Wikman , much appreciated. The interesting part was how differently the rollout is landing across sites; if yours shows the Approvals row under New Features already, I would be curious whether your space settings matched the four gates or surprised you somewhere.

@DOUGLAS THOMPSON this is a great piece of testing and your conclusion is the right one. The two-condition combo is the correct general-purpose check: exists() rules out the null case (field never populated), and the not-empty comparison rules out the empty-string case (default set then cleared), which was the exact…

Thanks @Tomislav Tobijas , that matches exactly what I saw. Worth adding for anyone landing here: sandboxes get enabled separately from production, so a site can show it in one and not the other even within the same org. @Kris Klima _K15t_ , if the New Features row still hasn't appeared, the support ticket Tomislav…

Hello @Tahir_Mohammed , building on @Varun Chillamcharla pointer to Card colors, here's the part that answers your "based on status" specifically. In the Select method dropdown the built-in options are Work type, Priority, Assignee, and Query. Status is not one of the direct options, so the way to color by status is the…

Hi @Calvin , @Kris Klima _K15t_ & @Evgenii Adding one data point from a Premium sandbox where I switched Approvals on tonight and walked it end to end. What I found is that there are four separate gates in front of "Start approval", and the support page only mentions the first: * Plan: Premium or Enterprise. * Rollout: the…

@DOUGLAS THOMPSON you were right, and I owe you and the thread a correction. I reran this properly and reproduced your row 3 exactly. First, the correction. My earlier "clean" test was measuring nothing: I had the rule on the Issue created trigger, and per Atlassian's own documentation, forms.last.* smart values are only…

Hello @Jan Pfeifer , glad it brought some calm to the IT department, that is exactly what these threads are for 🙂 Two answers to your two questions. On sources beyond Jean's link: yes, Atlassian documents the permission model in a few places, and they all say the same thing. The Teamwork Graph connector types page states…

Hello @DOUGLAS THOMPSON and @Marc -Devoteam- , I read through this exchange and decided to settle it with a clean test rather than add another opinion, so here is what I actually did and found. Setup: fresh text field, key ghosttest, no automation if/else (avoided a syntax mismatch on this instance), just a direct print of…

@Shawn Stevens Do not sell yourself short, "no expert" is doing a lot of work in that sentence 🙂 You brought the one thing nobody else on this thread has: what actually happens inside a company when the AI bill lands. That is field data, and it is worth more here than another architecture opinion. On responsibility, I…

Hello @Leela VenkataSatish Kolla , Great question, and it has a precise answer as of today, because "trigger a Rovo agent from Forge" means one of three different things, and Forge supports each differently. 1. Open a conversation with an agent from your app UI (supported): the Forge bridge rovo API. From any Jira or…

Hello @Gaurav Sharman , good design already, and both symptoms are recognisable, so let me name them and then give you the shape that fixes both at once. I have built exactly this kind of audit agent, and these two failure modes are the ones everyone hits. Symptom 1, the agent misses values you can see in the UI: it is not…

@joao zampa Count me in on the wish 🙂 The volume of good material here now outruns any search box, and a Rovo agent that could read this Community with permissions of its own would be a lovely dogfood. Two practical notes: the Community's own AI search is where I would expect it to surface first, and this is worth posting…

Hello @Miguel Velazquez , welcome, and these are exactly the questions to ask before enabling Rovo, so here are the answers as Atlassian documents them today, with the one setting that changes the picture. Which LLM: both, and it is not one model. Rovo routes across a mix: open-source models Atlassian hosts itself (Llama,…

@Naveena Tati Happy to point you the right way. The two sources I trust are both Atlassian's own: the exam guide for your certification, which usually includes sample questions in the exact scenario style you will face, and Atlassian University, where the free courses aligned to your exam end each module with knowledge…

Hi @Elfi von Natzmer , @Marc -Devoteam- is right that nobody here can act on your instance, but the answer to what to do and who can do it is quite specific, so here it is. What the message means. "This account isn't managed by your organization" means the person's email domain is not one your organization has verified and…

Hello @Ellanor Hall_ Vodafone , @Nikola Perisic is right that permissions are the first place to look, so let me add the detail that decides which admin has to click what, because there are two different exports and they are governed differently. Single page export (the ⋯ menu on a page) needs only the ability to view the…

Hello @Matthias Leipert , good list. Adding to @Marc -Devoteam- and @Viswanathan Ramachandran pointers, three things that change your next steps: 1. You do have a sandbox. Your post is tagged Premium, and a Confluence sandbox is included on Premium (one per production site). Your org admin creates it in Atlassian…

@Shawn Stevens Thank you, and you just named the cost side that nobody had said out loud yet 🙏 Agent-scoped identities would answer the "whose access is this" question. But every scoped identity is a new object an admin has to create, review, rotate and one day decommission. Multiply that by the number of agents a team…

Hello @alvina_hr , @Florian Bonniec is right on the mechanics: OAuth 2.0 client credentials do not carry an expiry, and API tokens are the credential type built for one. Let me add the governance layer, because your 90-day mandate is achievable and, on service accounts specifically, better than you might expect.…

Hello @Yamil Daniel Ali , good question, and the wall you hit is not a Jira limitation, it is an identity-model choice, so let me separate the two sides. Atlassian's side is per-user by design. The Rovo MCP server authenticates with OAuth 2.1 through an interactive consent flow, and the docs are explicit: tokens are never…