Bill Sheboy Expert

Hi @Mauricio Heberle Are you using a form in Jira Service Management? That new form's smart value only applies for those types of projects / forms. Although forms have recently been added for Jira Software Projects, I have seen posts from Atlassian team members that the smart values do not work for those forms yet. Kind…

Ah, your rule is acting on multiple projects...What is the scope of the rule: single-project, multiple-project, or global? A single-project scope rule may create / clone issues in other projects, but it cannot access them otherwise. When that is attempted the permission error you see can appear. To fix that symptom, the…

Hi @Levi Palmer First thing: as this is an older thread, I recommend creating a new question and perhaps linking back to this one. That will ensure the maximum number of people see it to offer suggestions. Back to your question... If you read through the other posts in this thread, you will find this symptom can happen…

Hi @Darryl Lee ! Maybe, and... I recall already seeing community posts with scoping / logic errors due to nested if / else blocks in rules where neither I nor the original poster could discern the behavior was working as expected. We ended up sending them to Atlassian Support to figure out if there was a defect in this new…

Within a rule...it is theoretically possible to use the issue history to check such scenarios, however as the history (i.e., change log) could have many entries, repeated paging of REST API calls with the Send Web Request could be needed. That gets messy very quickly. It may be better to use a custom field or entity…

Hi @florian.reichl_lovebyte.codes -- Welcome to the Atlassian Community! No, you did not miss anything: there are no custom triggers or actions, and still no REST API for automation rule management. The closest things to custom triggers and actions might be: * using the incoming webhook trigger to catch Jira Site, outgoing…

That symptom is likely a scoping issue, and can be solved by first creating the variable before the first condition. Then when it is re-created inside, the value will be replaced and available later in the rule. For example: * trigger: some trigger * action: create variable, to set a default value and anchor scoping* name:…

Hi @Rafael Garcia Tamarit JQL queries return issues. They do not return other Jira entities, such as versions. Please look here to learn more: https://confluence.atlassian.com/jirasoftwareserver/searching-for-issues-939938681.html To get a list of releases only, you could call the REST API endpoint to list the releases.…

Hi @Baba Gadji -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule, * images of any relevant actions / conditions /…

Hi @Andy Johnston Many fields are not available yet in the list views, and there are many open suggestions to add more. Here is one, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JWMCLOUD-578 Kind regards, Bill

Hi @Itsel Vazquez Adding to Trudy's suggestions: Are you including the units of measure when you set the Original Estimate field, such as with h for hours? If not, I believe it will default to minutes. To do this with hours, please use this with an h at the end: {{issue.startDate.diff(issue.duedate).days.multiply(8)}}h…

Hi @Emily Johnson -- Welcome to the Atlassian Community! Do you mean fields like the built-in Effort, with the scoring of one-to-five dots? I believe you may leave the field empty for the import to do that. For ideas already imported, you may select the current scoring (e.g., 2 dots) to clear it to empty. To search for…

Hi @Pejman Farahi -- Welcome to the Atlassian Community! By default, when you make edits to an issue in an automation rule, it does not automatically reload the data. Instead, the issue contains the values at the time the rule triggered. When you want the data to refresh, add the Re-fetch Issue action after that Assign…

You could get the issue (and its fields) with a JQL branch, but then you could not use the field in the edit action to change the trigger issue. This is why I described the approach of using the REST API with JQL to get the data and then use the web response in the edit.

Thanks for clarifying, and I believe rules cannot use the Parent Link when referring to an issue as the "parent" for plans in those actions. As you want to copy the Label values, let's first see if they are available directly: add a write to the audit log with this expression and then re-test your rule: parent labels:…

The status of the linked issues may be found using JQL to gather the issues (and then use conditions) or with smart value, list filtering on the {{issue.issuelinks}} smart value. If you decide to recreate your rule, please try those and then post the rule and audit log so the community can offer suggestions. Thanks!

@Ratom there is no indicator for "in the backlog" for team-managed projects that can be used with JQL expressions. Let's assume your team is using Scrum and you want to find the issues not assigned to any sprints yet. That would be this: project = yourProjectName AND statusCategory != Done AND sprint IS EMPTY ORDER BY Rank…

Hi @Marc -Devoteam- As others have noted: yes, that is the limit. The rule engine uses the REST API endpoints and those mostly have a 100 record limit. Kind regards, Bill

Hi @Krisztina TEGLASI Adding to the suggestions from @Hans Polder ... If you have not yet started your rule, I recommend trying to do so. This will help you learn and better ensure the rule meets your needs. To get you started on creating your rule, please refer to these documentation and example sources: *…

Hi @홍신영 -- Welcome to the Atlassian Community! Adding to Mikael's suggestion: Here is a how-to article for calling a REST API endpoint from an automation rule using the Send Web Request action: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 Kind…

Hi @Rémy Hilbert -- Welcome to the Atlassian Community! I recommend not using a new issue type named "Idea" as that one is already used by Jira Product Discovery (JPD): https://www.atlassian.com/software/jira/product-discovery And if your teams decide to add that product, having a duplicate issue type name will certainly…

Hi @Alex One way I have seen to do that unfortunately requires adding a "sort key" custom field to all of the issues, allowing the parent (e.g., Epic) to appear before their child issues. That custom field would be set by another automation rule prior to the need for reporting. Gather the issues with Lookup Issues with JQL…

Hi @John Funk Thanks for the information, and to your discussion prompt, I would invert that to this: I would like declarative referential integrity on field naming to prevent creation of fields with the same name in possible shared contexts to avoid confusing JQL, dashboard gadgets, and automation rules between locked and…

Hi @Anuja Ariyaratne -- Welcome to the Atlassian Community! What type of project are you using: company-managed or team-managed? You may find that information at the bottom-left of the page expanding area or in the list of all projects. At this time, only company-managed projects may change the card fields on the board to…

Hi @Mervyn Dogeno -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this when the linked issues are already shown in a list in the issue? That is, "why do this"? Knowing that may help the community to offer additional ideas. Until we know that... Please consider that links may be added /…

Hi @Thomas -- Welcome to the Atlassian Community! By default, automation rules may only access issues in a single project. The exception is to create / clone issues in another project. When you want your rule to access issues in another project, change the scope in the details at the top of the rule to multiple-project or…

Hi @Nataliia Sosnovshchenko This question is getting asked more and more lately, as such UX experiments are tried without an apparent impact assessment or way for customers to "opt out". (sigh) Here are two things to try: * One person at a time...disable all Jira Lab features in your personal settings* At the top-right of…

Hi @Yurii Serebriakov -- Welcome to the Atlassian Community! For a question like this, please post an image showing the audit log details for the rule execution. That will provide context to determine what happened when the rule ran. Also, I recommend posting the complete rule in a single image, perhaps using a capture…

Hi @Vikrant Yadav That is not possible with the built-in features of JQL as it cannot compare issues fields; it can only compare fields to a specific (or relative) value. Possible workarounds include: * hardcode the Due Date values in your JQL to perform such queries; this will potentially require many queries or query…

Hi @Giorgio Rivolta -- Welcome to the Atlassian Community! What have you tried thus far to solve this need? If you have an automation rule which is not working as expected, please provide the following so the community can offer better suggestions: * what type of project is this (e.g., company-managed, team-managed, etc.),…