Bill Sheboy Expert

Hi @yousefq Adding to Trudy's suggestions... And then change your advanced branch to use the lookup issues as its input, iterating over the distinct values. * trigger: scheduled, with no JQL * action: lookup issues, with the JQL you originally had in the trigger * advanced branch: over the values in…

Hmmm...If you had the Epics assigned to the team with the custom field, the basic filter should have worked: project = "my project" AND cf[12000] = "Team A" ORDER BY Rank ASC If you run that filter standalone from the top navigation Filters > View All Issues do you see what you expect? After you updated the filter, did you…

Thanks for confirming that! Please try adding the additional condition inside the branch...ensuring you exclude the one you want to move if it is the only one. (e.g., Issue B) If the remaining count is zero, the transition can happen.

Hi @Michael Haywood The sprint field in issues is a list field, containing 0-to-many values. Please try getting the specific entry you need. If your current sprint has the latest date, you may find the difference for an example issue in the lookup issues result with this:…

I believe the link syntax for Slack messages is this: <the URL|the link label> And so you could link to the key and summary like this: {{#lookupIssues}} * <{{url}}|{{key}} - {{summary}}> - {{duedate.jiraDate}} - {{assignee.displayName}} {{/}}

Hi @marianne_franco -- Welcome to the Atlassian Community! Do you want all of the epics to appear in the backlog's epic panel or do you only want the ones associated with each team's value in that custom field? If you want all of the epics to appear, perhaps change each filter to include epics or your team selection:…

Hi @frankie_medina -- Welcome to the Atlassian Community! You could add line breaks, and perhaps include the assignee's displayName values rather than their account id value like this: {{#lookupIssues}} * {{key}} - {{summary}} - {{duedate.jiraDate}} - {{assignee.displayName}} {{/}} If that does not help, please lookup the…

Yup; that symptom may be coincidental (i.e., a racetrack timing error) or a different default value in the REST API when the project is / is not specifically selected in the rule action. And so: * one of the loop passes creates and releases a version , * a later one tries to creates with the same name as an unreleased one…

Hi @Kauê -- Welcome to the Atlassian Community! Yes, that is possible with automation rules. As you describe just starting out with automation, I recommend reviewing this overview first: https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation Next, your rule could use the Sprint Started…

Hi @Nacho Cortes When supporting multiple teams using Scrum, it may be better to eliminate dependencies rather than try to manage them, procedurally or with Jira tooling. Otherwise each team does not own their own sprint plan and ability to meet their sprint goal...potentially blocking multiple teams in a chain and slowing…

Hi @Venkata Unnam -- Welcome to the Atlassian Community! The sprint date boundaries (start and end) are included in the range, and those dates you show do span 11 days. Kind regards, Bill

Hi @Thomas A If your rule detects an Epic transition and then transitions child issues (e.g., Story, Task, etc.) and grandchild (e.g. Subtasks) to match, why have any child or grandchild issues? It would seem they are not used to track work items / progress. Often this type of scenario is inverted: when the first child (or…

Hi @Tharaka_Hettiarachchi Using the option to allow rule trigger may not be a good approach for this scenario. The reason is a self-triggering rule for three levels of issue hierarchy could quickly trigger more than 10 times and halt rule execution due to service limits for loop…

Hi @siri k -- Welcome to the Atlassian Community! Based on that audit log entry, it appears your site / project has multiple fields named "Description". You may check that by examining one of the Create Subtask (or Create Issue) actions in the rule and checking the fields in the dropdown list. If that is not the case, has…

Using the changelog / fieldChange smart values to detect the added fix version value, you may then create a JQL statement to find the release management issue in the other project. Use that JQL with the Lookup Issues action to get the release management issue's key. Then use that issue key to create a JSON statement to…

Well done! For your test cases 4-6, and to avoid errors from attempts to add duplicate versions in the JSON, you could add .distinct after the split(",") as that will remove the duplicates. Regarding the typo {{issues... versus {{issue... thanks for seeing that! It was a coincidence it worked as the smart value {{issues}}…

Hi @suha_shakaa -- Welcome to the Atlassian Community! As this is an older thread, I recommend creating a new question and perhaps add a link back to this one. That will ensure the maximum number of people see it to offer suggestions. When you post your new question, please include: * what problem are you trying to solve;…

Thanks for that additional example to help clarify the need: you want to count the months difference including the end points (rather than just the difference in month values for the dates). One solution approach is to change the end date to the endOfMonth first and then increment by one day. That will handle differences…

Hi @Sarah Isaacs There is rule no action to directly trigger one automation rule from another by-name-of-the-rule. I have seen some workarounds for trying this type of rule flow, but none are the same as calling a sub-routine to do something and then return to the caller. A few of them are: * The starting rule edits an…

Greetings! In my experience, another possible cause for knowledge silos is misaligned reward systems. This is a subset of the organizational goals / priorities challenge noted by @Pramodh M and is a org culture and leadership issue rather than a tooling one. With misaligned reward systems, organizations may choose to not…

Hi @Sibi Alby -- Welcome to the Atlassian Community! First thing, which version of Jira are you using: Cloud, Server, or Data Center? You have tagged your question for Jira Cloud, but your rule image appears to be for Server or Data Center. Next, which marketplace app are you using to manage tests and test results? This is…

Hi @James Spicher -- Welcome to the Atlassian Community! That does not appear to be possible. Here is the suggestion to add the feature, which you may watch / vote for to see progress: https://jira.atlassian.com/browse/JWMCLOUD-35 Kind regards, Bill

Hi @Adelyn Zamora -- Welcome to the Atlassian Community! The project admins for a JPD project can modify the custom fields, including any colors which appear for different values. As a result, multiple different colors can show for each idea / row in a view / list. To learn which fields are currently showing the colors,…

Hi @Paulo Sebastião -- Welcome to the Atlassian Community! What observations lead you to believe the if / else block is not running sequentially? My understanding is if / else blocks process sequentially. Based on the rule you show, perhaps one or more of those many Send Web Request actions have not selected the option to…

Hi @Hamilton Lisa -- Welcome to the Atlassian Community! Yes, and...to Trudy's suggestion: Once you have the accountId values for the team members, a second call to the REST API could pass the values and return their user data, including the email addresses. Here is the user, bulk search one:…

Hi @Natalia Bakos Your trigger has selected the option, "Issues provided in the webhook HTTP POST body." And so I believe the rule loops to run the steps over each issue, including repeatedly creating the version and trying to release it. Based on timing, that may or may not fail when it collides on the version create /…

Hi @Kim_ Byeonghwa _SSS_ You appear to be using Jira Server (or Data Center), and have enabled the issue bulk-handling option for the rule's scheduled trigger: https://confluence.atlassian.com/automation/run-a-rule-against-issues-in-bulk-993924653.html And the rule is not using the Lookup Issues action. The fix may be to…

Hi @Alfred Tan On the documentation for this report: https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-version-report/ It describes: 10% of the estimated work for the version will need to be complete before the predictions can be calculated. Kind regards, Bill

Hi @lila Smart values are name, spacing, and case-sensitive, and they may not exactly match the displayed name on the issue pages. When an incorrect smart value is used, it returns null and so often fails silently in rules. To find the correct smart value (or its custom field id) please use this how-to…

Hi @Kathy Wahler Adding to Trudy's suggestions: Your rule trigger also has the bulk handling option selected. That option is used with the plural {{issues}} smart value when one wants to send a single email, or sum a field in the…