Gor Greyan Expert

Hi @Yannick Jarra, In Jira Cloud, it's important to distinguish between space-level insights and classic board reports. The Reports tab includes space insights, which are based on the space rather than individual boards. Therefore, configuring a filter for Team 1 doesn't necessarily create an independent reporting scope…

Hey @Jonathan Porta, Yes, exactly. I would recommend revalidating the current issue state before performing each critical action, especially since your listener modifies the same issue and may trigger additional update events. Regarding Adaptavist's response, that's quite interesting! :) Since Jira expressions are…

Hey @Jonathan Porta, By "webhook's field value," I meant the value available in the event payload passed to the listener, rather than the value retrieved through WorkItems.getByKey(). For example, you could log logger.info("Event Conversion type: ${issue.customfield_12689}") logger.info("Current Conversion type:…

Hi @Jonathan Porta, I suspect this could be related to the difference between the issue data available in the listener condition and the issue data retrieved by WorkItems.getByKey(). Your Jira expression evaluates the issue context associated with the triggering event, while makes a WorkItems.getByKey() separate REST API…

Hi @Saba Iram, Based on your description, this appears to be a billing or subscription restriction left after the Standard trial expired. Since you've already reduced the user count, checked for outstanding invoices, and attempted to reactivate the Free plan, I would recommend contacting Atlassian Billing Support directly.…

Hi @Kim Clark, To add to Thanasis's answer, if your goal is to export individual worklog entries for detailed analysis, I would recommend using the Jira REST API rather than relying on JQL and CSV exports. For a specific issue, you can retrieve its worklogs using: GET /rest/api/3/issue/ABC-123/worklog The response includes…

Hi @aslead-community, Mihai has already covered the main API limitations quite well. One additional recommendation for automated license monitoring is to distinguish between active users, provisioned users with product access, and billable users, since these numbers may differ. For monitoring, you could use the…

Hi @Josh, Thank you for the detailed explanation! This confirms the limitation I was experiencing with team capacity planning in Jira Plans. My original goal was to keep a single Story representing the business requirement, with separate BE, FE, and QA sub-tasks, each contributing to its respective team's capacity. I…

Hi @Project Commander, Thanks for the answer and the introduction to that app. Will try to review it on the job :) Thanks! Regards, Gor

Hi @Danut M _StonikByte_, Thanks for the introduction of the app, For now, we'd prefer not to introduce an additional paid app just for this requirement. Most probably will implement with the custom solution. Thanks again. Regards, Gor

Hi @Tomislav Tobijas, Thanks for sharing your experience and the related discussion/ticket, Tobi. It looks like Automation is the most practical option for us as well. We would prefer to keep the calculation within Jira rather than introduce a third-party reporting tool just for this roll-up. Hopefully Atlassian will…

Hi @Habib__Plugio__, Thanks for the detailed answer and for confirming that JRACLOUD-93508 is still the relevant ticket. For now, we'd prefer not to introduce an additional paid app just for this requirement. Since there is no native solution, we'll most likely handle the roll-up using Automation or our existing…

Hi @Anwesha Pan, Thanks for providing the different approaches. Our BE, FE and QA teams are currently configured as separate Teams in Plans, and we'd prefer to keep our existing hierarchy: Epic → Story/Task → BE/FE/QA Sub-tasks I tested the Team/capacity behavior, and a Story assigned to one Team correctly consumes that…

Hi @James Gamble, Thanks for the detailed explanation. This confirms what I was seeing during testing. We would strongly prefer to keep our current structure: Epic → Story/Task → BE/FE/QA Sub-tasks because the Story represents the functional requirement, while the subtasks represent the actual work performed by each…

Hi @Abilash, Thanks, the workflow makes the requirement clearer. You can handle this with one automation rule, you don't need separate rules. Configure it like this. Trigger: Work item transitioned to the Statuses - Sales Approval, Executive Team Approval, In Progress Then add an If / else block: IF Status = Sales Approval…

Hi @Abilash, Welcome to the Atlassian Community! From your audit log, the Assign work item action itself appears to be working correctly. In the 13:34:07 execution, Jira shows, If block → The following issues did not match the conditionLISM-1799 It then continues through the Else-if blocks until one matches, and only then…

Hi @AnimeSalt App, Welcome to the Atlassian Community! For larger Jira Cloud environments, I’d focus on reducing the amount of work Automation needs to start with, rather than only optimizing the actions at the end. A few practices that make the biggest difference: - Use the most specific trigger possible. For example,…

Hi @rafiqi, Welcome to the Atlassian Community! Matthew’s suggestion is the first thing I would check. The error Error retrieving the work type fields for project/typeId - 10371/10424 usually means Automation cannot access the create metadata for that target space/work type. I would verify three things 1. The rule scope…

Hi @Larry Hofmann, Welcome to the Atlassian Community! You don't actually need a variable for this, although using one can make testing easier. The main thing I would change is the regex. From your sample description SIEM created investigation CrowdStrike Falcon - A process attempted to delete a Volume Shadow Snapshot on…

Dear @Amitava Chattopadhyay, Happy to help you! Let us know if you have any further questions regarding that implementation. Also, if the answer was helpful, kindly ask you to accept it, as other community members have found it as resolved. Regards, Gor

Hi @Gianluca Carlini, Welcome to the Atlassian Community! Raising it with Atlassian Support was the right next step. I also checked the public JAC tracker and couldn't find an existing ticket specifically for Label old/new values disappearing from the History tab, so your Support ticket may help Atlassian identify and…

Hi @Amitava Chattopadhyay, Welcome to the Community! I would separate these into two requirements, because Original Estimate and Time Tracking are two different things in Jira. If you want Original Estimate to be mandatory when work is assigned, the cleanest approach is a workflow validator on the relevant transition(s).…

Hi @Brian RICHARDSON, Welcome to the Atlassian Community! As the work item itself and the filter both show correct data, I would first look at the Great Gadgets configuration. Check the gadget's working-time settings and see exactly which estimate field the gadget is configured to display. A different hours-per-day…

Hi @Thierry Dubau, Welcome to the Atlassian Community! You can export the last modified date directly Jira's system, Updated field contains that value. Add Updated as a column in the work item search and export the results to CSV. However, Jira does not have a standard “Last modified by” field that you can simply add as a…

Hi @Elena Damaschin, Welcome to the Atlassian Community! What exact error are you getting? Could you provide more detailed information? Try in incognito mode or clear your browser cache. Nobody in the community can access to your site. You can contact your Jira Admins to check it or contact to Atlassian Support. Regards,…

Hi @Allen Hirsch, Welcome to the Atlassian Community! If you want to control which work types a custom field applies to, go to: Settings → Work items → Custom fields → find the field → More actions → Contexts and default value There you can configure the field context for specific spaces and work types. Then, to make the…

Hi @rumceisz, Welcome to the Atlassian Community! Before giving you an exact solution, could you confirm your Jira Data Center version and whether you need time in the current status only, or a report showing time spent in every previous status as well?

Hi @Cey Dimpre, Welcome to the Atlassian Community! For a closed work item, the recommended approach is still to handle Resolution through workflow transitions, rather than making the Resolution field directly editable. If you need to change Done to Won't Do, you can create a Closed —> Closed transition and use the Set…

Hi @flaimo, I agree; this is a valid concern with the new step-based Automation usage model. A bulk edit can generate events for many work items, and rules listening to those events may execute for each affected item. At the moment, I'm not aware of a native “Do not trigger automation rules” option for Jira Cloud bulk edit…

Hi @RoarByte(Attacker), Arkadiusz makes an important distinction here. If your goal is to grant/remove access when someone is added to a specific Jira project, I would use Project Roles rather than Jira groups. Groups are organization-level membership, while roles are project-specific. You can configure your permission…