Bill Sheboy Expert

Hi @Lukáš Meitner That error message seems to indicate the field/location in the {{webhookData}} is empty. Have you tried to remove the JQL search on the trigger (switching to the "No issues from the webhook" option), and just write the webhookData to the audit log? That may confirm if the information has what you expect.…

Hi @David You may try the text functions to split out the just the number part of the {{issue.key}} if that is what you want: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ For example: {{issue.key.substringAfter("-")}} for just the number or replace the hyphen with a space to break the…

Hi @Matthew Pears Have you checked if your custom field's types are text or numeric? If text, you may need to convert them to numbers in order to make a mathematical function work, such as: {{issue.myCustomField.asNumber}} Kind regards, Bill

Hi @Tina Park I am a bit unclear on your use case...when a sprint is created it has no issues assigned to it, so the Sprint Created trigger could not be used as you note. Perhaps an alternative would be a rule triggered on Sprint Started...as sprint planning has probably occurred by that point and so the issues could be…

Hi @[deleted] -- Welcome to the Atlassian Community! For a question like this, please consider posting images of your rule and the audit log details. That may provide more context for the community to offer suggestions. Thanks! Until then...I cannot discern if you are creating the new issues from an email handler or from…

The {{issue.subtasks}} smart value only contains some of the fields from the subtasks. To get all of the issues fields please try using Lookup Issues with JQL to get the subtasks as I noted above.

Hi @Frank Liang -- Welcome to the Atlassian Community! You can perform the date diff on business days to exclude weekends: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ However, that will not account for removing any holidays (non-working days) you have defined; only weekends. Kind…

Peter, I tried your original expression with Jira Cloud and it worked for me. The results in the advanced branch were to return the accountId automagically...as that appears to be the default attribute when used this way. Please confirm your smart value capitalization as smart values are case-sensitive. Note that my lookup…

Hi @Hela Szubert Yes, and...to what Fabio suggests: Here is the documentation on that one and other advanced JQL functions to help: https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-updatedByupdatedBy-- Kind regards, Bill

You are welcome; glad to help. :^)

Hi @Pauline Hild Thanks for that information! A few follow-up questions: Is this rule in a specific project, or is it a global/multi-project scope rule? Is this rule acting on a company-managed or team-managed project? There appears to be an edit of the trigger issue (e.g. LAB-520) happening. What is being changed? You…

Hi @[deleted] -- Welcome to the Atlassian Community! Yes, that is possible. Try to split the description on the newline character first, producing a list of lines. That will simplify your search using a regular expression with the match() function. For example: {{issue.description.split("\n").match("Paint:(.*)").trim()}}…

Hi @joemallion Please try this, adjusting for the markup you want to use: subtask information: {{#issue.subtasks}} * {{key}} {{status.name}} {{/}} If you instead want more control over the content and order, please try the Lookup Issues action with JQL to get the issues, such as: parent = {{triggerIssue.parent}} ORDER BY…

That is curious...just to confirm the conditions, would please post images of: * your current rule that does not work as expected, * the rule details section showing the settings, and * the audit log details for the execution? And, are you using Jira Cloud or Jira Server/Data Center version? Thanks!

Hi @Larissa Akemi I recall seeing a similar Jira question a while ago indicating this was not possible yet due to limitations on the MS Teams side. Perhaps check on the MS support area for Teams to see if someone has solved this. To do the similar thing with Slack, you need to capture and store the Slack user id…

Hi @Tim Foster That error message seems to be coming from another location in the rule than the image you posted. You can confirm that as the JQL in your branch is much simpler than what the error indicates. Please post an image of your complete rule, and provide details of other areas in the rule which use JQL to gather…

Hi @Tomasz Sarzyński -- Welcome to the Atlassian Community! You may do that with a scheduled trigger and JQL to find the issues to transition. I recommend writing and testing your JQL first to confirm your results. For example, schedule the trigger for once a day with JQL for the issues project = myProjectName AND status…

Hi @Maria Ostaszewska-Cichocka -- Welcome to the Atlassian Community! And here is the suggestion on accessibility compliance, added in 2004: https://jira.atlassian.com/browse/JRACLOUD-5574 There is a related suggestion for Jira Server/Data Center version which appears to be "in progress". Kind regards, Bill

That error is because the trigger is for a sprint, and you are trying to edit an issue (story), so the rule doesn't know what the "current" issue is. Please try to set the sprint field when you create the story. That will do this in one step. The other way to solve this error is to add a branch on the most recently created…

Hi, Vladimir. Would you please clarify a bit to help consider solution approaches: Are you using a global/multi-project scope automation rule, or in just one project? Are you using Jira Cloud or Server/Data Center version? If this is Jira Cloud, what type of project(s) are you using, Team-managed or Company-Managed? You…

Hi, Carolina. Please try entering that smart value for the Sprint field when creating the issue. The value will appear below the field, so you need to select it for the smart value to be used.

Hi @Pauline Hild There are known timing issues with the Issue Created trigger such that all of the information may not be available when the rule fires. To know if this is the cause of what you are seeing...A work-around is to add a Re-fetch action immediately after your trigger. That will slow down the rule by reloading…

Hi @Martin Yes, and...to what Melo suggests: Please try the way the math operations are described in the documentation. Some other things to try if that does not work are: * Check your field types, and if the field is text, you may need to convert with asNumber in order to perform math operations. For example:…

Hi @Jyotiranjan Rout You may find all of those things using JQL and the WAS operator. The results may then be displayed on a dashboard with one of the issue filter gadgets. Please look here for more information about advanced…

Hi @Alexander Wayne Just to confirm...is the originally triggering issue a subtask...leading to a change of the parent and all sibling subtasks? If so, have you considered using a JQL branch for the issues with the same parent? For example: * trigger: value changes for Provider ID field * condition: issueType is your…

Hi @Lisa Besteni Yes, and...to what Josh suggests: Perhaps do not resize; that makes permanent a work-around for the symptoms and does not help with the underlying causes. Instead consider a retrospective every couple of weeks and review the completed items to learn what was different/special for items that did not match…

Hi @Vladimir Dabic -- Welcome to the Atlassian Community! Looking at the piece of your rule you have included, you appear to be putting the webhook data values in the "Values to add" field for the field edit. If that is correct that would explain why values are added and never replaced. You have at least two options to…

Hi @Carolina SILVA Please try setting the sprint to the one that triggered the rule using {{sprint.id}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--Sprint-- Kind regards, Bill

On that page, please take a look at the example for the exists() function to do what you ask: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/#exists That function checks if a field has a value, and then uses it when present.

Hi @David Quiram Yes, and...to what Jack suggests: * If one is *always* null, just put them side-by-side and one will disappear, without the extra delimiter: {{issue.summary}} - {{issue.firstDate}}{{issue.secondDate}} * Otherwise, you could use the conditional logic to do this in-line or use if/else components for extra…