Bill Sheboy Expert

Hi, @alexanderlanden First, how/when is that field you are testing in the issue populated? Are you certain it contains a numeric value when tested? If you try writing it to the audit log, what does it show? Next, would you please post images of your complete rule and of the audit log details for when the rule doesn't work…

Hi, Dan. You may add the issueType check to your JQL when you use LookupIssues and so get only that sum. To do this for multiple issueTypes you would need multiple LookupIssues calls. The other alterative is to gather all the issues with one LookupIssues call, than use both smart list filtering and math operations to sum…

Hi, George. Welcome to the Atlassian Community! Essentially the steps are: * create a JQL filter for the issues you want, * save the filter for reuse, * export all fields to a CSV file, * open and resave that file as XLSX or XLS format * create a new MS Word document, * use the step by step wizard to help you create the…

Hi @Peter Assignee is an object in the smart values (with several attributes), so distinct may not work until you get to the level of a single attribute, like the accountId. Perhaps try {{lookupIssues.assignee.accountId.distinct}} and then split the results so they can be used in the advanced branch. Kind regards, Bill

Hi @Barend Vermaak Please create JQL to find the issues you want to communicate. Then use the JQL with LookupIssues to gather the issues, and select the fields you want to include in your channel. Look here for more information about…

Hi @Ray Albert Do you mean Automation for Jira? If so... For your item #3: this could be done with a separate rule, triggered on the approval ticket transition. That rule could identify the parent and add another one linked to it. For your item #4: you may set up that list of approvers as a group for assignment, hard-code…

Hi @Greg Williams Please take a look at this documentation from the vendor for an automation rule which seems to match your use case: https://herocoders.atlassian.net/wiki/spaces/IC/pages/2483519492/Apply+checklist+template+to+issue+on+issue+create+edit+or+transition Kind regards, Bill

Hi @Stanford Kamau The branch smart values are currently only available with the Branch Created trigger: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-development/ There are some suggestions to make them available with other triggers for the issues. A couple of possible work-arounds would be to: *…

Hi @[deleted] -- Welcome to the Atlassian Community! It is not possible to recover a deleted issue with out-of-the-box Jira Cloud features. If you have built a backup/restore process for your site instance (and the issue is older than the last backup) it could possibly be restored. The absence of "undo" for issue deletes…

Working as you note, this may be challenging. I have seen posts of people trying to work-around this with automation rules, etc. Yet you are trying to get Jira to have consistent behavior/reporting for different fields in different project types...and that may not work. As others have noted, there is a suggestion under…

Hi @Victoria T Yes, and...to what @Mykenna Cepek suggests... You could also look at the conditional logic and/or new smart value list filtering for more complex formatting: * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ *…

Hi @kevin.caldwell -- Welcome to the Atlassian Community! If I understand your question, you are asking about comparing something like this (ignoring the status category values for a minute): A) To-Do Developing Testing Releasing Done ===== ========== ======= ========= ==== B) To-Do Developing Dev-Complete Testing…

Hi @Lisa Besteni In my opinion, teams using Kanban practices will not find built-in Jira Cloud reports/dashboards that can help...other than for the edge case of a stable, trivial workflow such as to-do, doing, done. My recommendation is: * consider your cost, effort, and timeframe constraints; * consider the reporting you…

Hi @Antoine _Klee Group_ Please take a look at this documentation page: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-select-custom-field To add to a multi-select option field, you would want to use "update" and "add", rather than just the shortcut version with "fields".…

Hi @[deleted] From what you described, it is unclear what you are doing with those summed values: sending emails, adding comments, updating a field, etc. If you are updating a field, you may want to use JQL to find the linked issues by type to use the sum. I suggest that as I do not believe the smart value list filtering…

Hi @niks.berzins -- Welcome to the Atlassian Community! Trying to centralize the story point values between the different project types, Company-Managed and Team-Managed, may lead to some unintended consequences and Jira reporting problems. You noted this: "We're managing several projects in a single sprint." What do you…

The missing part is getting the issues with Lookup Issues (if you need a batch) or with a branch (to processing individually). Perhaps like this: * trigger: scheduled at 2 pm with no JQL * branch: on JQL to get the issues of interest* action: to extract the due date using string functions already mentioned * ...more…

Hi @Barend Vermaak -- Welcome to the Atlassian Community! One way to do that would be with an automation rule in Jira Cloud. With that you could use a scheduled rule to post an update to a channel. For examples of that, please look here: https://www.atlassian.com/software/jira/automation-template-library/slack-ms-teams And…

Hi @ldevore -- Welcome to the Atlassian Community! Your query is using the OR to combine the results to the left and right, and so returning more issues than you expect. (AND takes precedence before OR) In general, try to build up your queries piece by piece, testing as you go...like this: * note the things which apply to…

You could use {{now}} and the time zone functions, or just use endOfDay() from JQL, like this...substituting in your project name: project = myProjectName AND statusCategory != Done AND due <= endOfDay()

Well, I am stumped... Checking the public backlog I did not find this symptom listed for any open defects. If your are on a paid (not free) license, you may want to work with your site admin to submit a ticket to Atlassian Support to take a look: https://support.atlassian.com/contact/#/

Hello, all! Jumping in to help as Harish asked this same question via another thread... Harish, to do that consider creating a rule schedule triggered only on the time of 2pm (no JQL), and then use Lookup Issues with JQL to find any items which are due relative to {{now}}. Kind regards, Bill

Thanks for that link...As Darryl is actively helping to solve that with you, let's stick with that thread, and I'll post my thoughts there. Kind regards, Bill

Hi, Emilia! Did enabling that option solve the problem? I just wanted to confirm as I had not heard of company-created applications not triggering for Issue Created. Thanks!

Hi @Harish ShanmugamDhanasekar You can probably do that with the date time functions: resetting to start of day, adjusting the time with plusHours(), adjusting to your time zone, and the perform the check against {{now}} adjusted to your time zone.…

Hmmm...Have you tried typing in the start of their email addresses to see if they appear in the list rather than their names?

Hi @Tim Perrault If you look in this group you will find threads with ideas on answering from community leaders and others: https://community.atlassian.com/t5/Atlassian-Answerers/gh-p/Answerers For marketplace vendors, here is more…

Hi @Carlos Cordova Yes, and...to what Jack suggests: * they also need to have logged in at least once (I believe) and * check to confirm you have the correct id value. If they were added by email address the names you are searching for may not match what you expect until they update it in their profile. Kind regards, Bill

Hi @Benjamin Fernandez and @Jack Brickey I think this may be the suggestion you were looking for: Ability to customise the fields shown on cards in team-managed projects (backlog + board) https://jira.atlassian.com/browse/JSWCLOUD-17336 Kind regards, Bill

Hi, Mathilde. Your image does not match what I was describing. What I meant was based upon your initial rule image with the branch. Please note that I suggested moving the send email action into the branch nesting. * trigger: field value changes * branch: on current issue* condition: value is greater than 50 * action: send…