Germán Morales Community Champion

Hi Camille, That limit looks like it is coming from the Blue Cat import Power-Up, not from Trello itself. Blue Cat’s own pricing information for “Import to Trello” currently says the free tier includes 10 free imports, while unlimited imports are part of the paid tier. If this appeared after an account management change, I…

Olá Andre, Em Jira Cloud, essa diferença normalmente acontece porque o painel e o CSV podem estar contando coisas ligeiramente diferentes. Eu verificaria primeiro estes pontos: 1. Na exportação, foi selecionado “Only active users” ou “All users”? A opção “All users” pode incluir usuários ativos, suspensos e desativados. 2.…

Thanks Trudy, that makes sense. Good clarification: for supported fields, using the “Copy from trigger issue” option in the Edit issue action is cleaner than typing smart values manually. I would still use smart values when the field is not available in the picker, or when the value needs to be transformed before being…

Hi Philip, I think there are two slightly different cases here: 1. No audit log entry for the work item If there is no execution entry at all, the flow probably did not trigger. In that case I would check the trigger configuration, trigger filters, project/space scope, and whether the event was caused by another automation…

Hi Jamie, Trudy’s approach is the direction I would take as well: avoid nested branches and use a JQL branch that returns all descendants of the Initiative. One important detail: inside the branch, the “current issue” becomes each child issue returned by the JQL. So when copying values from the Initiative, make sure you…

Hi Emma, This depends on how the Perforce ALM app exposes that information inside Jira. Perforce/Helix ALM can link Jira issues with ALM items such as requirements, test cases and test runs. However, for Xporter the key question is whether those linked ALM values are stored/exposed as Jira fields that Xporter can read. I…

Olá, Como você perguntou diretamente por uma opção de Marketplace: eu desenvolvo o Hiera, então minha recomendação não é neutra. O Hiera pode ajudar quando você precisa manter uma hierarquia virtual entre issues independentes, sem usar subtasks. Por exemplo, você pode representar algo como: Entregável -> Epic -> Story ou…

Hi, In Jira Automation, an If/else block behaves like a mutually exclusive chain. Once one condition matches, that branch runs and the later else/if branches are not evaluated. So it will not behave like several independent checks executed one by one. In your screenshot, if you want condition 1 and condition 2 to both be…

Hi Nisha, Assuming you are on Jira Cloud and you have permission to create automation rules, I would start with a simple scheduled rule. Example approach: 1. Trigger: Scheduled - Run weekly, monthly, or whatever cadence matches your regression cycle. 2. Optional JQL in the trigger: - Use this if you only want the rule to…

Hi @Mahanth Prudhvi P , If your main problem is future/planned sprints, I would not try to infer the current sprint from the order of values in the exported Sprint cell. That order is not a reliable business rule. For Jira Standard, the safest no-automation workaround is to split the export by JQL before exporting: -…

Your clarification is important: you are not just looking for post-delivery reporting, you want to forecast project allocation before the work happens. For that use case, I would separate two models: 1. Resource scheduling Tools where you assign specific tasks to specific people on a calendar. 2. Project allocation /…

I would be careful relying on the order of Sprint values in the exported cell. A work item can move through multiple sprints, and the export is not a great source of truth for “current sprint” logic in a spreadsheet. If you need reporting in Google Sheets, I would avoid parsing the first or last sprint from that…

I would separate the concepts here, because Jira uses “Project/Space”, “Team”, “Goal” and “Epic” in different places. Assigning a Team to an Epic or to a Goal does not necessarily mean the project directory’s Team column will be populated. That column is tied to the Jira project/space metadata, not to the Team field you…

A resposta da Trudy está correta: um link personalizado ajuda a conectar os itens, mas o Jira não vai tratar isso como uma hierarquia real de pai/filho. Eu separaria em duas opções: 1. Se você precisa apenas navegar entre os itens, um issue link personalizado pode resolver. 2. Se você precisa de comportamento de…

The workflow condition suggested above is a good fit if the children are sub-tasks. If your Feature’s children are regular Jira work items connected through the Parent field, I would handle it with Automation instead: 1. Trigger: Work item transitioned to Done 2. Condition: Work type = Feature 3. Lookup issues with JQL:…

Good discussion here. A couple of things that might help: On the Browse Projects permission: worth double-checking that the service account has Browse Projects at the project level specifically. The getIssuesForSprint endpoint can return an empty issues array when the user can see the sprint (via…

Hi Jagadeswar! To read a YAML file from an issue attachment in Jira Cloud using ScriptRunner Behaviors (Groovy), you need to: 1. Get the issue key/ID from the current issue context 2. Use the Jira REST API to fetch the list of attachments 3. Download the attachment content using the attachment URL 4. Parse the YAML content…

Hi Dikla! These are great questions that many organizations evaluating Rovo are asking. Here's what I can share based on current knowledge: **Question 1 — Intelligent Data Relevance Filtering:** Rovo does use relevance mechanisms when indexing and searching data — it applies semantic search and contextual ranking to…

Hi Jubin! Great investigation — the root cause is almost certainly related to how StreamContent serializes and sends the request body compared to StringContent. Here's what's happening: 1. **StreamContent vs StringContent**: When you use StreamContent with a MemoryStream, the Content-Length header may not be set correctly…

Hi Catherine! This is a known change Atlassian rolled out to the new issue create experience in Jira Cloud — the "simplified" create form now only shows Title and Description by default to reduce friction. Unfortunately, there is currently no admin-level setting to force all fields to show by default in the new create…

Good catch John, thanks. You're right: the rightmost column mapping is the trigger for sprint close in both project types. Resolution matters in company-managed for reports, filters and workflow hygiene, but it's not what sprint close actually looks at. Editing my post to correct this so nobody gets the wrong info.

Great post, Yashodip. Answering your question: the biggest shift for me was auditing custom fields and deleting the ones with less than 20% usage. We had around 90 fields, only 35 were actually populated across issues. Every screen got faster, and people stopped ignoring the "required" ones because they were finally…

EDIT: Thanks to John Funk for the correction below. Updated to reflect that the rightmost column mapping drives sprint close in both project types, and Resolution is a separate consideration in company-managed. Quick clarifier that should save some back-and-forth: the mechanism for sprint close is actually the same in both…

Just two small additions to Ajay's and Arkadiusz's great answers: 1. The endpoint is **api.atlassian.com/admin/v1/orgs**, not admin.atlassian.com (which 301-redirects and can drop auth headers in some runtimes). Worth double-checking from your screenshot. 2. The manifest snippet that's required: permissions: external:…

Thanks Bill! Sorry about that, I'm new to the community. Happy to have it moved to App Central.