Bill Sheboy Expert

Hi @Sara V. Adding to Walter's answer...There is some free, online training from Atlassian on JQL, such as this class below: https://university.atlassian.com/student/path/849533-gain-project-insights-through-jql This one helps to learn how you might answer project questions using JQL. Kind regards, Bill

Hi @sarah.wight First thing, I am going to assume your fields are not actually named TYPE and DATE, as that could cause both confusion and potential problems for your site admin. If those are the names, consider changing the names to better match their meaning. I am also assuming that REGION and TYPE are single-select…

Here is one: Synch labels from epic to child issues, allowing the children to keep any additional labels they added. This uses the change log, created variables and JSON, dynamically built, to first remove the old labels and then to add the new ones. To learn about this method, please take a look at the linked…

Okay, I rebuilt my example rule for this :^) I recommend testing to confirm it works as you want. This uses the change log, created variables and JSON, dynamically built, to first remove the old labels and then to add the new ones. To learn about this method, please take a look at the linked documentation above. * trigger:…

Hi @Patrik Buchart Adding to Alex's answers... I notice in your screen image of the issue edit that you are trying to change the Summary twice: once with copy from current issue and later in the advanced edit with JSON. You can only set/update the field once in an edit, so decide which one to remove. Kind regards, Bill

In your screen images, the LogTime field is empty, and so I would not expect a value to be created for the diff(). Did you post the correct images? What is the type of your LogTime field: text, date/time, something else? Next, have you confirmed that "LogTime" is the correct smart value for that field name? To check on…

Thanks for that information. When you look at the issue change history for TES-214 what was the change that triggered the rule? I recall that some changes can trigger Issue Updated, but that they are not tracked in a manner which shows in the change history. And, some context setting questions: Are you using Jira Cloud or…

Nope...my example rule that I wrote last year has stopped working since then. Let me experiment using a JSON edit instead.

Hi @JEY ANNE NASIS -- Welcome to the Atlassian Community! I do not believe there are any built-in Jira features for planning poker. Please work with your Jira site admin to contact the marketplace vendor for the addon/app you are using for this error. Thanks! Kind regards, Bill

Hi @Tiago Machado -- Welcome to the Atlassian Community! Yes, that is one of the syntaxes to set a checkbox field, by either entering the drop-down text as the option values or the id values, as shown here: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Checkbox-custom-field So if…

Hi @Simon Owen -- Welcome to the Atlassian Community! If you are not seeing it, I suspect you are using a team-managed project, and working-day management is not a feature of that project type yet. Here is the suggestion to add that, which you may vote for/watch to see…

Thanks for that screen image; it shows you are using a company-managed (CMP), software project. I believe that team field is not supported with automation yet, based on this suggestion: https://jira.atlassian.com/browse/JSWCLOUD-21983 You can watch/vote for the item to see progress.

Hi! I suspect that may not work for a couple of reasons... 1) Smart values are name, spacing, and case sensitive. You defined the variables as {{VarResults}} {{VarWarnings}} and {{VarErrors}} but then sum them in lower case as {{varResults}} {{varWarnings}} and {{varErrors}} Please try changing one of them so they match…

Jira defines the "next" version is the one at the bottom of the list on the releases page. When you want a different version to be "next", you drag it to the bottom of the list. There is no other built-in way to select "next". If you have other criteria that defines "next release candidate" (e.g. a naming convention), you…

Hi @Jigesh Patel -- Welcome to the Atlassian Community! Are your teams using versions or epics to manage your work? If so, you could try the relevant burn charts to help see the remaining work. The use case noted for this thread was generic about summing the information, and so if you have other criteria (other than…

Hi @[deleted] Which "team" field are you trying to set from the rule? I believe there are several things with that name in Jira Cloud, and I recall at least one of them cannot be set by rules. You can often determine if a field can be set with a rule, and confirm its smart value, using this how-to…

Hi @Alex Magee -- Welcome to the Atlassian Community! I believe both your smart values and the time logging have some issues... * First thing: {{issue.worklog}} is a built in smart value! Have you really defined a custom field which is also named "WorkLog", with the only difference in capitalization? If so, that is…

This is the more complicated option, as you first must remove the previous labels the parent used, and then add the current values. Both of these use the {{changelog}} smart value. For example, this rule would be triggered on a parent epic's labels changing: * trigger: Value changes for Labels * condition: issue type is…

Hi @Sebastien Pierron -- Welcome to the Atlassian Community! Adding to Mark's answer with a question... Do you always have those values (and text values) in the Description field? For example: * What happens when one of the values is zero: the label text (errors warnings successes) are always present, or they are absent…

Hi @medjouti -- Welcome to the Atlassian Community! Adding to Nic's answer... When you are on a paid license, you must also be at least a site admin to submit a support ticket to Atlassian. If you have a lower level permission, please work with your site admin to submit the ticket. Thanks! Kind regards, Bill

Hi @Aleksey Sivaks -- Welcome to the Atlassian Community! No; the only grouping options for the built-in Created vs. Resolved gadget are Hourly, Daily, Weekly, Monthly, Quarterly, and Yearly. For more flexibility and other reporting options, please review what is available in the Atlassian Marketplace...or export your…

Hi @Gary Richardson For an automation question like this, please consider posting images of your complete rule, any action details, and of the audit log details showing the rule execution. Those will provide context for the community to offer suggestions to help solve the problem. Thanks! Kind regards, Bill

Hi @Mohammed Fayiz K M -- Welcome to the Atlassian Community! Please take a look at what is available from the REST API, such as described in some of these links: https://developer.atlassian.com/cloud/jira/software/rest/api-group-board/ https://docs.atlassian.com/software/jira/docs/api/REST/1000.824.0/ You can get all of…

Hi @Grudinina_ Galina _ INSD -- Welcome to the Atlassian Community! Without that connector, what is your plan for sending notifications to Slack: by calling the REST API directly, something else? If you have the paid version of Automation for Jira (A4J), you could do this with a web request to call the Slack REST API. The…

Hi @kirill_lapshin A lot about automation rules is experimentation, and so looking around in Jira to see what might work...For example, if you go to a company-managed project's release notes page, the URL would be: myCompanyUrl/projects/myProjectName/versions/myReleaseVersionId/tab/release-report-all-issues If you plug in…

Hi @Luke Towers This looks like the one...Ability to preserve and set default "order by" for issue under Epics: https://jira.atlassian.com/browse/JRACLOUD-79973 Kind regards, Bill

Thanks for that information... Am I understanding correctly that the problem is the linking is not working? If so, try changing the set of Epic Link to "Copy from Issue", as that will use the current issue you are branching to: the just created epic.

Thanks, Liz! I can understand the situation, and can see how re-assignment could cause unintended consequences...not just for reporting/history. For example, let's say you are tracking down a decision/problem from an item completed in the past...and you wonder, "hey, that's assigned to Bill so let's talk to him..." Bill…

Hi @Scott Roehrenbeck -- Welcome to the Atlassian Community! Adding to the answers...Here is a how-to article to set up and call a REST API method from an automation rule: https://community.atlassian.com/t5/Jira-articles/Automation-for-Jira-Send-web-request-using-Jira-REST-API/ba-p/1443828 Kind regards, Bill

Hi @louise.simmonds Yes, and...to Mark's answer: Please consider adding a couple of additional conditions on epic link (testing for not empty) before the edits. That will avoid attempts to link to an empty link and so reduce "noise" in the issue history. Kind regards, Bill