Gor Greyan Expert

Hi @Thushara Amaranayaka, It loads on my side. I suggest clearing the browser cache or trying incognito mode or a different browser. Regards, Gor

Hi @Carrie Rutherford Welcome to the Atlassian Community! I would recommend contacting Atlassian Support directly. They can verify your organization's ownership and help update or recover the Billing Admin access. Trying to recover or bypass the former employee's 2FA would not be the appropriate route. You can raise the…

Hi @Dayna Portillo @Trudy P Claspill has already provided the correct Atlassian documentation. To clarify your specific question, Atlassian counts the Automation component that executes, not each individual criterion inside that component. So, if one condition contains multiple criteria connected with AND/OR, it is still…

Hi @Zuzanna Patocka_Deviniti_ What a long wait news😊 We have wait for it after our migration, it is already a year)) Thanks for the information.

Congrats @Sridhar Gandla Wishing you good luck)

Hi @Troth_ Stefanie On Tuesday, 1 September, {{now.lastOfTheMonth(1)}} calculates the last Monday of September, while the Monday you actually want to check is 31 August. A safer approach I think is to evaluate yesterday and check whether yesterday was the second or last Monday of its own month. Tuesday after second Monday…

Hi @Jasmeet Kaur Can you provide more information about the issue that you face? It is Atlassian Community, you can ask and get answers regarding the questions to the Atlassian Products, like Jira, Confluence, Bitbucket and etc. Regards, Gor

Hi @Tyler Watts Sorry for the miscommunication, i didn't note, that the question is about Data Center. For Data Center, Railsware's documented approach is to use Jira Automation + Send web request to the Smart Checklist REST API. You can still use your Scheduled trigger with JQL for the existing Stories. Then the rule…

Hi @Troth_ Stefanie Thanks for the clarification. In that case, keeping the rule scheduled for Tuesday is correct. You should not change (2,1) to (2,2). Instead, check whether today is one day after the required Monday. Tuesday after the second Monday is the following --> {{now.jiraDate}} equals…

Hi @Troth_ Stefanie Your scheduled trigger is currently configured to run on Tuesday, but your conditions are checking whether {{now}} is the second or last Monday. When the rule executes on Tuesday, those comparisons will always be false. I would simplify the rule and schedule it to run daily. Then use the two conditions…

Hi @Mahanth Prudhvi P Happy to help! If the answer was helpful, kindly ask you also accept the answer, as other community members find it as solved. Regards, Gor

Hey @Tyler Watts Here is the step-by-step setup I’d use for a one-time bulk import of an existing Smart Checklist template into existing Stories. Go to Project settings --> Automation --> Create rule. Choose Scheduled as the trigger. Enable the option to run a JQL search and execute actions for each matching work item. Add…

Hi @Mahanth Prudhvi P Welcome to the Atlassian Community! Some of this is normal. A Jira Sandbox is best treated as a safe validation environment, rather than an exact, continuously synchronized copy of Production. The production data copy is usually where you notice the most waiting. After that, configuration changes made…

Hi @Troth_ Stefanie Welcome to the Atlassian Community! I’d handle this with one Scheduled Automation rule instead of maintaining multiple cron expressions. Configure the trigger to run every day at your preferred time, then use date conditions to decide whether today is one of the required dates. Jira Automation date…

Hi @nagata shumpei Happy to help you!

Hi @Tyler Watts Yes, exactly, this is a Jira Automation rule. Smart Checklist adds the Import Checklist Template action to Jira Automation. If you only need to apply it once to the existing Stories, you don't need to keep a recurring schedule. You can create a Scheduled trigger with JQL, configure it to run against the…

Hi @nagata shumpei What you're hitting appears to be an Automation service limit, not your Premium monthly execution allowance. Those are separate limits, so having less than 1% monthly usage doesn't prevent a rule from being throttled. Creating ~400 parent work items and immediately triggering four different rules to…

Hi @Dieter Lauwers Gabriela is correct, the error occurs because once {{webResponse.body}} is stored in xrayTests, Automation renders it into a string representation such as {data={...}}, which is not valid JSON, so jsonStringToObject() cannot parse it back. The clean solution is therefore to skip the intermediate variable…

Hi @Raghavendra Udutha Welcome to the Atlassian Community! It is a general error message. Do any other colleagues face that error, or only you? I checked the Atlassian Status Page; no ongoing incidents are available for now. I suggest clearing the browser cache or trying via incognit/another browser. If the issue still…

Hi @Dieter Lauwers Welcome to the Atlassian Community! The issue is likely that xrayTests contains {{webResponse.body}} as a string, so Automation can't navigate it as a JSON object. I would branch directly over the response instead. {{webResponse.body.data.getTestExecutions.results.first.tests.results}} Set the Advanced…

Hi @Spencer Hudson Welcome to the Atlassian Community! Since this is affecting only one user and they can still create the work item, I agree it doesn’t look like a permissions problem. The screen in your screenshot is Jira Cloud’s newer Quick Create experience, but losing the Description text isn’t expected behavior. I’d…

Hi @Tyler Watts If you are using the following app: Then there is an Automation action in Jira Automation: Import Checklist Template, via which you can import to you needed Stories, via the Scheduled Automation. My provided documentation is Create Automation: Trigger -- Scheduled trigger with JQL Action -- Import Checklist…

Hi @Sylvain GROUSELLE If one of these answers was helpful for you, kindly ask you to accept it. Regards, Gor

Hi @Tyler Watts Sorry, I misunderstood your original question and assumed you were referring to the Smart Checklist app. For Jira's native Action Items/checklist, there isn't currently a native reusable checklist template feature that you can select and bulk-apply to existing Stories. If you need to apply the same native…

Hi @Tyler Watts Create an automation rule with a Scheduled trigger, select Run a JQL search and execute actions for each work item in the query, and use JQL to identify the existing Stories you want to update. Then add the Import Checklist Template action provided by Smart Checklist and enter/select the ID of your existing…

Hi @Sylvain GROUSELLE Welcome to the Atlassian Community! It depends on what you mean by child elements. If you mean subtasks, there is no need to block the archive operation until they are archived first. Jira doesn't allow subtasks to be archived independently; when you archive the parent work item, its subtasks are…

Hi @Baptistan HIOT Welcome to the Atlassian Community! Being a Jira site admin doesn't necessarily permit you to manage the hierarchy of every Atlassian team. Team hierarchy is managed from the team profile, and the ability to add a parent team depends on the team's management settings and permissions. I would first check…

@Benjamin Zhou Understood. If you don't want to modify the workflow or add another transition, then native Jira Cloud doesn't provide this capability. Jira doesn't have field-level permissions that allow you to say: when the status is Closed, only User A or members of Group B can edit these two fields. If you have…

Hi @Tim Hoare-Ward Welcome to the Atlassian Community! Your overall setup sounds good. I’d focus on the security level configuration rather than the board itself. Having Browse Spaces permission is only the first layer. If a work item has a security level set, the user must also be included in that specific security level;…

Hi @Benjamin Zhou Sebastian’s approach is the one I would use as well. Jira Cloud doesn't have native field-level permissions that make a field editable only for a particular user/group based on status. A practical solution is to keep these fields read-only during normal work and expose them on a dedicated transition…