Sami Shaik Success Champion

@Elias Sackmann , What you are describing is the native shape of Jira Product Discovery, and the licensing works in your favour. Why JPD rather than a Jira software space Ideas live in a Discovery space with list, board and matrix views you control, so “a browsable list of improvement ideas” is a saved view, not a filter…

Hi @Heinrich Bärhausen , two things are happening at once here, and both are Cloud behaviours rather than a broken rule. 1. The Sprint field is a list, and the clone carries the history. On Cloud, an issue’s Sprint field holds every sprint the issue has been in, not only the current one. Clone work item copies “all field…

@Salla Aaltonen , the pattern you describe (agents can add other licensed users as participants but not customer-only people) usually comes down to where the customer-only person stands in relation to that service space, not to the agents’ permissions. Two checks will tell you which case you are in. Check 1: is the person…

@Nicolás De León (Vortex Labs), that is the distinction admins need, and I have checked it against the specs: the Set issue property operation caps a value at 32,768 bytes, and the Forge storage pages describe hosted storage as scoped per app installation, so it sits outside the work item and outside the 500 MB. The…

@Lauren Korfhage , I reproduced this on a Confluence Cloud sandbox today rather than guess, because every route above had been suggested and you reported none of them working. Results, so you can pick the one that matches your situation: First, the bug is real and Atlassian has no workaround on record. CONFCLOUD-84591…

@Jesus Nieto , good thread. @Kris Klima K15t, @Ciro and @Arkadiusz Wroblewski have covered the options ; let me add the boundaries, because your three requirements (consistent fields, cross-space reporting, change tracking) each stop at a different native wall, and knowing where is what keeps you out of a rebuild later. 1.…

@Ganarnek Srianuchar , @Lalithesh has given you the right menu paths . Before you build, I would change one decision in step 1, because it decides how much work steps 2 to 5 become. Do not create a space per customer. Create one service space and one organization per customer. In Jira Service Management Cloud, an…

@M , I promised to take this to the Community Managers, and they came back on Friday with a direct answer. For someone with no Atlassian site and no Bugcrowd account, email the Security team at security@atlassian.com. That is the route the Atlassian Community Management team confirmed for exactly your situation. What to…

Update: I have written the method up as an article, with @Becker_ Rene ’s JSON-size approach as the core and the paging and totals checks from the current REST v3 specs around it: Jira’s 500 MB per work item limit arrives in November: find the ones that will hit it first. Still interested in anyone’s real top figure from a…

M, I hear you, and after two attempts I will not pretend the gap is not real: Atlassian’s public pages give a customer route (the support form, which gates on a site) and a researcher route (Bugcrowd, which needs an account on a bounty platform), and nothing in between for a member of the public holding someone else’s…

@Nicolás De León (Vortex Labs) , you are right, and the docs sharpen it further. The Runs on Atlassian apps page allows external domains “used for the purpose of analytics” as long as the egress carries no in-scope End-User Data (category: analytics, inScopeEUD: false in the manifest), and the analytics tool policy…

@Alexey Paveliev , thanks for checking, and credit to @Tintu Paul for the screenshot: your console is on the newer Atlassian Administration layout, where the path is Sites, Site settings, your site, Service Collection, Portal-only customers. The route I gave (Products, the site, Jira Service Management) is what the support…

One more ask on top of the size indicator, @Snehal Shah : a warning threshold below 500 MB. Today the first signal an admin gets is a rejected write with a 413. A soft warning at, say, 400 MB (an audit log entry, a notification to the site admins, or a flag on the item) would let teams fix the integration that is writing…

@Becker_ Rene , thank you, that is the first practical method on the thread and it is close to what I would do. Measuring the serialised JSON is a decent proxy for the text-and-metadata footprint, since that is roughly what the limit counts. Three refinements, based on the Get issue reference: Ask for the things a plain…

@Andrew Rusling , @Arkadiusz Wroblewski KB is the right page for the “deactivated” case. Your sequence has one extra step that changes the picture: you deleted the account, and on Atlassian Cloud a deletion is not immediate. What a delete actually does. Per Delete a managed account, the account is deactivated for 14 days…

@Alexey Paveliev , your own fix points at the cause, and there is a documented sentence that matches your symptom exactly. What most likely happened. Somewhere along the way an Atlassian account came into existence for the same email address as the portal-only customer: an invite to another product, a Confluence share, a…

@Nicolas , that is a useful correction from the vendor side, and a sharper rule than the one most admins carry: a CDN font, an error tracker or a library that phones home is egress, and the badge goes. Bundling fonts in the app is the right call and the kind of detail that never reaches a listing page. To your question: I…

@Mihai_LeanZero , thank you for running it on a test site; those are three findings I did not have and they change the plan. For @Akshad Katke, folding Mihai’s results into the steps above: Leave the importer’s link columns empty. They write a link onto the source item as well as the copy, which breaks your “source…

Thank you @Dhruv Mittal , that cleared most of the list in one pass. I have updated the article with your answers and credited the thread. Two follow-ups, both from replies that arrived after yours: JSM scope. You wrote that the new view “does not impact the JSM work items”. @Charlotte Reynolds reports this morning that…

@Akshad Katke , Short version: CSV is the only native way to copy (rather than move) work items on Jira Cloud, it is reliable for 3,000 rows if you prepare the file properly, and it has three hard limits you should accept before you start. Details, in the order you asked. Is CSV reliable for this? Yes, with one design…

I have collected the open admin questions from this thread in one place, together with what the support docs and the admin console confirm as of today: the “New work item view” row under General configuration, Options (on by default), the “Modern work item view” Beta features switch and its “Not supported in Jira Service…

Glad it is sorted, @Yamin ZAKARIA, and thanks for closing the loop. For anyone landing here later: the App admin role alone did not give him Create; membership of the jira-admins-<site> group (the group holding Administer Jira under Global permissions) did. Worth a look at the Atlassian Administration audit log to see who…

@M thanks for coming back with the screenshot, that is useful. What you hit is the form’s entitlement gate: once you pick Opsgenie under “Which app is this for?”, it wants a Site URL it can tie to a paying Opsgenie account, and with none it routes you to “Ask the community”. The route I gave you works for customers and for…

Thank you, @Snehal Shah , this is the kind of limit admins want to hear about a month early rather than from a 413. Two questions from the operating side: Is there any way to read a work item’s current total size before November? The post names the inclusions (comments, worklogs, properties, links, voters and watchers, SLA…

@Francisco Castrillo , @Arkadiusz Wroblewski is right: there is no REST or GraphQL endpoint for agent conversations today. Two facts from the live documentation that shape what you can do in the meantime, because the second one is a deadline. 1. What Live conversations gives you, and to whom. Per Atlassian’s page Review…

@Jo Heylen , I cannot give you the activation conditions for ConfluenceDatabaseEditTool, because Atlassian does not document the tool by that name anywhere I can find; it is an internal tool name that leaked into an execution message. What is documented tells you most of what you need, though. The capability is still Beta…

@Yamin ZAKARIA , @Arkadiusz Wroblewski has the cause: organisation admin is an Atlassian Administration role, and creating a space is a Jira permission. The two are granted in different places, and “member of all the admin groups” can still leave the Jira one missing. Two checks, in this order. 1. Are you an App admin for…

Hi @Kaitlyn Hoban , @Josh rule shape is the one to build, and @Aaron Pavez [ServiceRocket] “prove it in Postman first” is the right order. Two additions from the Create project reference as it reads today, both about making @Matthew Sinclair point (“company-managed, standardised schemes”) actually happen. 1. Add…

@Richard, that is the number that settles it: 9.02 MiB of attachments across every status against a meter reading 2.1 GB. Nothing you can see accounts for the difference, so this is Atlassian’s to fix, not yours. When you write to them, lead with those two figures and the date of the last purge; that is the whole case in…

@Utkarsh Chandel , @Josh has covered the Permissions and Domains tabs correctly. One update on the point he flagged as “check before you count on it”: there is a control that keeps MCP out of specific spaces even when the signed-in user can open them, and it is documented. The Atlassian Rovo MCP server control in Data…