Germán Morales Community Champion

Hola @Soporte Comtecsa, para poder ayudarte hace falta concretar un poco más, porque "no muestra todas las funciones" y "fecha de corte" pueden referirse a cosas muy distintas. Te paso las preguntas que necesito resueltas para dar una respuesta útil: * ¿Dónde no ves los tickets activos? ¿En un Board (Kanban / Scrum), en el…

Hi @Duong Nguyen Hong, @Juan Carlos Pin's direction is correct. To make it concrete and avoid the most common pitfalls, here are the exact steps and the gotchas around mapping a Jira custom field into a form. The capability is called Linked Jira field on Atlassian's native forms (the same engine for Jira Software, Jira…

Hi @Mark W_ McColgan, @Trudy Claspill already pointed you to @Bill Sheboy's classic answer, which is the right reference for an Automation only solution. Let me add the trade offs by approach so you can pick the one that matches your use case. 1. Native Automation, rough estimate. The closest built in primitive is…

Hi @ana_lugo, welcome to the Community. @Arkadiusz Wroblewski already covered the core path well, so let me add a few things specific to your rebranding case that often catch teams by surprise. The subdomain change happens at admin.atlassian.com under Products (or Apps in the newer UI) > Product URLs, performed by an…

Hi @Claudia Ardura, @Liam Do's suggestion is a solid path if you can budget a Power-Up, but since you specifically want a free route inside Atlassian tools, there is a way using Jira Cloud Automation (available on Free) plus a single call to the Trello REST API. No third party app needed. The flow: * Trigger: Field value…

Hi @Sarah McCauley, just to complement @Trudy Claspill's answer with a detail and a workaround. The shortcut to open the shortcuts panel is documented as ?. On a US keyboard layout you get it with Shift + /, but on other layouts (Spanish, German, French, etc.) the key combination to produce ? is different. Either way, the…

Hi @confluenceadmins, two things to check. ScriptRunner Cloud is built and maintained by Adaptavist, not Atlassian. Their issueFunction JQL extensions depend on their app being properly registered with your Jira instance, and the metadata sync needs to complete fully before the functions become recognized. The error "field…

Hi @Louis Kueh, since several of your questions touch hierarchy, dependencies, and cross-project visibility, here's a structured answer. Hierarchy in Jira (native) * On Cloud Free and Standard, the hierarchy is fixed: Epic, then Story/Task, then Sub-task. Three effective levels, no custom levels above Epic. * On Cloud…

Hi @Svetlana Risteska, this trade-off is a known limitation of Plans: archived versions are excluded from issue sources, but unarchived versions all show up in the Fix Version picker. A few workarounds I've seen work at scale: * Don't archive, label instead. Add a label like stale-version to versions you'd otherwise…

Hi @Leandro Cardoso, the confusion is common because there's no UI flow in Atlassian Cloud labeled "create Bearer token". The way to get a real Bearer token in Cloud is through a Service Account. The personal API tokens you've been creating only support Basic auth against your-site.atlassian.net (Authorization header with…

Hi @Adam Todd, a few things stand out from the headers you shared. The Server: awselb/2.0 and the CloudFront headers confirm this 429 is coming from Zephyr Scale's own infrastructure, not from the Jira Cloud rate limiter. These are separate systems with separate limits. The fact that waiting 60 seconds (as Retry-After…

Hi @Dominik Zöbl, the combination of Server: AtlassianEdge and X-Cache: Error from cloudfront tells you this 500 is coming from the CDN/edge layer, not from the Jira application itself. If the Jira backend had returned the error, you would see a structured JSON body with an error message. A short, empty-ish body from the…

Hi @Rajagopal V, I notice from your profile that you are a Product Admin, so @Marc -Devoteam-'s suggestion to "contact the admins" might not apply here since you are the admin. A 403 on /servicedesk/customer/portals for an admin usually points to one of these: * You're accessing the customer portal URL while logged in as…

Hi @Robert Henson, the Jira Cloud audit log has a configurable retention period. By default it keeps a limited window of data (often around 6 months), and anything older is removed permanently. If you can only see back to February 2026 and the change you're looking for was September 2025, those records have already aged…

Hi @Martin Vali, I can see the issue from your screenshots. In your Lookup JQL you have assignee = {{user.accountId}}. The problem is that {{user}} in Automation always refers to the person who triggered the rule (you, the admin who clicked Run), not the current participant from the branch. Inside a "For each smart value…

Hi @Caryn Yeoh, on Standard you have a few native options for this. The most direct one is a cross-project board. Create a saved filter with JQL like project in (PROJ1, PROJ2, PROJ3, PROJ4, PROJ5) AND status != Done, then create a new board from that filter. You get a single Kanban or Scrum view across all five projects.…

Hi @Crystal Kim, the direction you have (Slack to Jira) is the easy one. Going back from Jira into a specific Slack thread is trickier. The built-in Send Slack message action in Jira Automation can post to a channel but cannot reply inside an existing thread. Slack threading needs a thread_ts identifier and the native…

Hi @Daniel Hamngren, just tested on a Hiera site. I was able to create a new OAuth credential for a fresh service account and it appeared in the credentials list as expected, so that org is not impacted. Combined with what you already shared (Atlassian aware and working on a fix, another admin affected on a different org,…

Thanks for clarifying, @KatherineM, and well done finding the path through the Contributors area. You're right, what you were after isn't the old Jira "project/space" Team field but the newer "Project" entity inside Goals, which is a different object entirely. My earlier reply was answering for the older meaning of…

Hi @Sourabh Gandhi , your investigation is solid. Pinpointing the exact byte offset where the parser breaks tells me you're on the right track. Two things to add to what @Arkadiusz Wroblewski already said. The change that buys you the most is moving from /rest/api/2/search/jql to /rest/api/3/search/jql. In v2, rich text…

Marc and Rudy are pointing in the right direction. Two things to add. The Board / Backlog split is by design in Scrum boards. There's no setting that merges them, and trying to force it usually makes things worse. So either: * Switch to Kanban. One view, every item in the filter, your "manually postponed" idea becomes a…

The HTML body on a 400 is the most useful clue. Jira's REST API returns JSON when it rejects a request at the application layer, with response headers including x-arequestid and x-ausername. HTML means your request isn't reaching Jira itself; it's being rejected upstream at the edge layer. Next time it happens, grab…

Hi @Daniel Hamngren , Thanks for the extra details. If the service account has app access, project permissions, and the token was created with `read:jira-work`, then I agree this starts to look less like a normal Jira permission problem. One thing to check: Atlassian’s documentation says OAuth 2.0 credentials for service…

Hi @Nick Boemo , Since this is a team-managed software space and you want the form-created work items to be linked to an Epic, I would treat this as setting the Parent field, not as moving something out of the backlog. You could try an automation rule like this: 1. Trigger: Work item created, or Form submitted if that…

Hi @Daniel Hamngren , I would check two separate things here. For the 401 Unauthorized, make sure the request is using the correct endpoint format for scoped service account API tokens. Atlassian’s docs say these tokens should be used through the Platform API Gateway, for example:…

Thanks @Prashanth , I really appreciate it. If you do take a look, I’d be especially interested in whether the hierarchy, dependency and workload angle maps to the kind of cross-project planning problems you see in enterprise Jira setups. Any candid feedback would be very useful.

This matches what I have seen in Jira environments too. The hard part is rarely just “send ticket A to system B”. The real complexity appears when both sides have different ownership models, status meanings, SLA expectations and audit requirements. For me, the key design question is: what should be synchronized, and what…

Hi Prashanth, I would start by separating the problem into two layers: 1. The operating model 2. The tooling Jira Cloud and Rovo can be a strong foundation, but I would avoid starting with configuration first. For an enterprise-wide setup, the main risk is usually ending up with many department-specific workflows, fields…

Hi @Param Kelkar, @Walter Buggenhout 's answer is a good starting point. I would just add one important distinction: ACA-900 should not be prepared in the same way as ACP-120. ACP-120 is more focused on Jira Cloud administration. ACA-900 is more focused on practical Jira Software usage: navigation, basic concepts, work…

Hi Aseel, Assuming this is Jira Cloud with the GitHub for Jira integration, I would check a few things separately because the Development page and the issue-level Development panel depend on several pieces working together. 1. Confirm the GitHub integration is still connected correctly Ask a Jira admin to go to the…