Gabriela - LeanZero Community Champion

Hi @Dulari Vikas Pawar, Jira Software tracks work items, it isn't a document editor, so a requirements doc doesn't really live there. Write the PRD in Confluence, which ships a Product Requirements template with the sections you'd expect (background, assumptions, user stories, scope); inside it you type /jira to link the…

@Shikhar Bind your data isn't gone yet. A deactivated Free site is retained for 15 days from the deactivation date (60 for paid), so there's a window to act. The reason there's no Reactivate button is that Free has no billing subscription to "resume", so it doesn't surface the way it does on paid plans. Two routes that…

Hi @Jade Zavitoski, That's expected rather than a bug. Workforce routing runs at intake. It assigns when a new item arrives with a team set, and it doesn't re-evaluate when the Team field changes on an existing issue, so clearing the assignee on the L1 to L2 hop won't re-arm it. The native way to cover the escalation is…

Ha, fair hit. You compressed my whole wall into one line. Agreed though, no native way to skip a level, so JRACLOUD-89913 is the one to watch. Thanks Arek.

Not via acli, no. workitem view only takes -f/--fields (plus --json and --web), there's no --expand equivalent, so the CLI can't surface expand-only data like transitions, changelog or renderedFields. For those you'd hit the REST resource directly, e.g. GET /rest/api/3/issue/<KEY>?expand=transitions,changelog You can still…

Hi @Pavan kumar Mamidipaka, You don't actually need ScriptRunner for this. Native automation can send straight to a Jira group and every member of it gets the email. The one thing it won't do is turn your group-picker field's value into member addresses on its own: the email action's recipient dropdown (Send customized…

One correction to my own answer above, because I sent you the wrong way on the auth. Bearer is fine for a scoped token. The api.atlassian.com gateway accepts both Bearer and basic auth, and Atlassian's own service-account token doc uses Authorization: Bearer <token> in its example, so your original header wasn't the…

Hi @jaya krishna gonuguntla _CW_, your own test is the answer here: this isn't a propagation delay, so there's no wait time to expect. Getting the email back for a user set to "Only you and administrators" is only possible when the account your API token authenticates as has admin-level visibility, even if you personally…

@Trudy P Claspill good catch, thanks - the tags do say Data Center, so scratch the Cloud/DC question. On DC the config side is "Create with shared configuration" rather than the company-managed share I described. The issue-copy gap is the same though: a clone leaves Epic Link pointing at the original epic, which is what…

You're right, my bad. acli's transition command runs a transition, it doesn't list them, and view won't expand them either, so there's no acli flag that shows them. Quickest path is to hit the endpoint directly: GET /rest/api/3/issue/<KEY>/transitions (curl -u email:token). Same list, scoped to what you can actually do…

Quick correction to my own answer above, because the timing caught me out on this one: skip the v1 org user-search endpoint I mentioned - Atlassian retired the v1 organization user APIs at the end of June, so it won't get you anywhere now. Reach for the v2 one instead: POST…

The propagation angle is a dead end, so I'd stop waiting on that one — this isn't a setting that just hasn't caught up yet. Two things are actually happening. First, the email you get back tracks the privilege of whoever your API call authenticates as, not only the target user's visibility choice. The fact that you still…

There are really two separate things tangled together in what you're after, and Jira treats them very differently: the project's configuration, and the issues that live inside it. The configuration side is native. When you create a new company-managed project there's a "Share settings with an existing project" option —…

Quick reframe before you start pruning: the 1,700 isn't a cap on how many automation rules you can build — it's how many times your rules can successfully run in a month on Standard. You can have as many rules as you want; what you're actually rationing is executions. Two things stretch that number a lot further than it…

Short version: native parent-child can't skip a level, so what you saw in your test is the expected behaviour rather than something you set up wrong. Jira's hierarchy is a single ordered stack of levels - in your case Initiative > Feature > Epic > Story - and the Parent field only ever links an item to the level directly…

The thing that decides this is whether the account was deactivated or actually deleted - they behave very differently, so it's worth pinning down first. If it was deactivated (suspended for inactivity but not purged), those are often recoverable. For a personal / unmanaged account, try logging in and running a password…

Good news, in a way: that "admin approval required" screen isn't coming from Jira at all - it's Microsoft's, which means the fix lives on the Microsoft 365 / Entra side and not in JSM. Here's what's actually happening. When you add the mailbox, JSM kicks off an OAuth consent with Microsoft so it can read that inbox. Your…

Trudy and Viswanathan have basically covered the hygiene side already (archiving, trimming custom fields, auditing apps), so instead of repeating that I'll point at the thing that's usually hiding behind "it got slow as the issue count grew" - because on Cloud it's often not the issue count at all. Two different problems…

Hi, There are two things that specifically bite people when it's a service account doing the calls, and they're easy to miss: Service accounts can only create scoped API tokens, and a scoped token behaves differently from a normal personal API token in two ways. First, it has to go through the gateway URL -…

Hi Adrian, The null there isn't really a bug - it's that transitions aren't a field, they're an "expand" on the issue resource. So --fields '*all' will never populate them, because *all only pulls fields, and the available-transitions list is generated separately from the workflow based on the item's current status. That's…

Hi Barbara, Yeah, Forms on their own won't enforce the summary format - the summary stays a free-text field no matter what. But you've got two nice ways to get there, depending on whether you'd rather have the summary built for people or have Jira reject the ones that don't fit. The one I'd reach for first, since your form…