Gabriela - LeanZero Community Champion

Hi Daniel, I don't think you're misusing the API, which is the first thing I'd settle. The create-request field reference documents exactly that shape, describing Attachment as "Attachments, using IDs of temporary attachments as provided by the /attachTemporaryFile API", so passing temporary IDs inside requestFieldValues…

Hi Sveinung, Work item security and data classification are separate features, and the security doc frames itself against permissions rather than against classification: "work item security schemes let you control who can see specific work items within that space". That route governs who can open an item and will not set a…

Hi Stefanie, Before you spend time on the JQL that was suggested, I'd say it won't do what you need here, because the trigger's JQL isn't a date gate at all. The docs put it plainly: "You can also choose to enter a JQL query. If you do, actions in this flow will execute on the work items included in the query." Since your…

Hi Scotty, There's a detail in your own paste that I don't think anyone has picked up yet. Your remote reads git@bitbucket-gigprompter:scottyhuff/gigprompter.git, and bitbucket-gigprompter isn't a Bitbucket hostname at all; it's a Host alias out of your ~/.ssh/config. That means the key your push offers is whichever…

Adding the numbers to Gor's point, because the figure is what tells you whether 400 at once was ever going to work. The service limits table gives "Number of flows that can run at the same time" as Free 5, Standard 10, Premium 20, Enterprise 30, alongside a separate cap on total rule executions in a one-hour window. You…

The KB that comes up first for this one is about Git operations rather than this call: "This article covers three scenarios where you may encounter the 403 error while performing Git operations such as push/clone." Its three causes are IP allowlisting on the workspace, the two-step verification requirement, and having no…

I went looking for a documented size limit on the board export and could not find one, and the limits page only covers object counts like cards and checklists, where it even says those figures "are not meant to be the documented limits". So I would not assume that is your wall. History is capped regardless. "The JSON…

Adding the bit that settles it either way. The trial doc says outright, "During the Rovo Dev Standard trial, Rovo Dev CLI and Rovo Dev in the IDE are not available." So the 2,000 credits won't tell you which one you're on. That number is the standard monthly allowance per user and it shows either way, which is probably why…

There's a path that avoids handing out repo admin, though it isn't that settings page. Repository access tokens carry an "Edit variables" permission on its own. It maps to the pipeline:variable scope, documented as access to "create pipelines environmental variables in repositories and deployments". Deployments included,…

Don't wait on that export to arrive. The API will hand you the same list today, and it comes with a catch that matters more than the export bug does. The endpoint is GET https://api.statuspage.io/v1/pages/{page_id}/subscribers, and it takes a type filter, so you pull email and sms separately. There's also…

Your reading of that ticket is right, and there are better ones to put your weight behind. CLOUD-3048 is Closed as Won't Fix, it was raised in 2010, it carries 8 votes, and its title is "Include the LaTeX plugin", so it really was asking Atlassian to bundle somebody else's tool rather than build one. It sits in the CLOUD…

Your error names the exact spot, and the payload you pasted underneath it is the proof. It complains at line 1, column 2, expecting a double-quote to start a field name. Column 2 is where "data" begins, and your text has data= rather than "data":, so the parser is right to give up there. That shape isn't JSON at all. Look…

Then the key wasn't it, and my last answer was aimed at the wrong thing. You'd said the key, I explained the key back at you, which is no help at all. With the dash detail in, what stands out is what actually made it work. Checkboxes and Multiselect dropdown sit in the same group in the docs, both under "The following…

Placement is the wrong axis for cost. Where the rules live doesn't change what they consume. "Step allowances are pooled at the organization level and are the sum of all automation steps across your apps", so one global rule scoped to forty spaces and forty space rules draw from the same place. What does change consumption…

The variable probably isn't the space, it's that one attachment, and there's a test that separates the two in about a minute. Jira splits attachment deletion into two permissions and they behave very differently. "The Delete own attachments permission allows users to remove attachments they've added to a work item." The…

What you're seeing lines up exactly with what the email path is documented to produce, which is the frustrating part: it isn't ignoring your instruction, it was only ever going to act on part of it. The AI summary is documented to "summarize an email, extract due dates, create a relevant title, and put action items in a…

Glad you're moving again, but that wasn't magic, and the same thing will bite you on the next form unless you know where to look. Form smart values don't resolve on the field's name. They resolve on its field key: "you'll need to know both the field type and the field key which acts as the unique identifier of a field in a…

While you wait on that engineer, go and look at your old machines, because that route doesn't depend on what Support finds. Every machine you ever cloned those repos onto still holds a complete copy. A git clone carries the full history, not a working snapshot, so an old laptop, a backup drive, a CI worker or a colleague's…

Varun's read on the mismatch is right, and there's a small syntax thing that will make his fix look like it didn't work. Text functions take parentheses, list functions don't, and it catches people out. The docs show text as "{{issue.summary.length()}} -> 12" and "{{issue.summary.isEmpty()}} -> false", while the list forms…

Then you were never going to find it, and I sent you looking. Sorry about that. The corner notification Ollie described is the portal experience. If your requestors reach the form by its own URL instead, there's nothing to spot, because that path doesn't show a key at all. JRACLOUD-98607 describes your screen almost word…

No read-only path, I'm afraid. The ping endpoint itself lists both, "read:ops-config:jira-service-management" and "write:ops-config:jira-service-management", so the write scope isn't something you can configure around. It's what the operation is documented to need. The thing I'd give more attention to is what that same…

Your instinct is right, and it's really one ticket rather than two: 94494 is closed as a duplicate of 94516. They rule themselves out on something sharper than filters or tabs. Both need a board that belongs to a person, which 94516 states in its opening line as "If you have a board that belongs to a user (not a project)"…

You can't, and it isn't your configuration. Branch restrictions exempt users and groups, and an access token is neither. The access token docs put it plainly: "Access tokens are tied to a repository, project, or workspace (rather than a user) and should not be shared." Nothing tied to a repository can go in a list that…

The inconsistency Arkadiusz describes has a cause that sits outside JSM, and it's separable from the question of whether something changed. It's an account setting. Email address visibility belongs to the individual Atlassian account, not to JSM or the project, and the holder controls it at…

Signed out, the tracker shows you the words but not the control. "Vote for this issue" is rendered as plain text with no link behind it, and its tooltip says "You have to be logged in to vote for an issue." Watching is the same. The toolbar carries a Log In button with os_destination=/browse/JRACLOUD-95244, so signing in…

On the account question, yes. The address is unique per member and per board: "Each Trello board has a unique email address for each member. Sending an email to that address will create a card as you." So the card lands under your account and is attributed to you, the same as if you had typed it. Retention is documented,…

Good, and your correction on the Project columns stands. The KB I quoted describes the single-project case, where you pick the target in the wizard and the columns are redundant. Importing across projects is a different shape and the importer asks for what it asks for. PRO-222 itself is still unexplained, though. A 404 on…

Your reading is right, and the doc closes it rather than leaving it open: "TWG CLI uses OAuth 2.1 as its only supported authentication method. The one exception is Bitbucket, which isn't covered by OAuth yet and requires a separate Bitbucket token." So TWG_BBC_TOKEN being the only environment variable you found is the…

Atlassian staff do read these forums, and you've seen that on other threads, but their own bug-reporting page puts the community beside Contact Support rather than in front of it: "then go to our Trello support page and click on Contact Support to report the bug, or ask for help in our Trello Community". Nobody answering…

Hold the 30k run until you know where PRO-222 went. Atlassian has a KB for this exact operation, updating an Assets object custom field by external import, and the recipe in it is much narrower than what you sent. Verbatim: "You'll need at least three columns: Work Item Key, Summary, and Custom Field. During this setup,…