Bill Sheboy Expert

You can also try doing this as sometimes the structure below works, assuming the {{issue}} is a subtask}} {{issue.parent.parent.labels}} I recommend experimentation; this syntax does not work for everything. If it did, a rule would need to potentially pull in every issue in a project/site!

Hi @Ryan Jones For your scenario you note: Because they don't move to done until a coupe of days in the next sprint I am struggling to measure an accurate cycle time, throughput and velocity. Those measures are often described as... * Cycle time: the duration from start of a specific status to a different specific status.…

Hi @Amir Malka -- Welcome to the Atlassian Community! As others have noted, that is not possible with JQL. What problem are you trying to solve by getting the sprint start date in a query? Knowing that may help the community to offer you suggestions to help. Kind regards, Bill

Hi @Replaceable -- Welcome to the Atlassian Community! For automation rule questions, please post images of your complete rule and the audit log details showing the execution. That will provide context for the community to offer suggestions. Thanks! Without seeing your rule, I suspect this is either a branching or a timing…

Hi @n0179576 -- Welcome to the Atlassian Community! You are correct that the AND operators are processed before the OR ones. Two ways to solve this are to group the ORs together or to use the IN operator: created >= "-3d" AND "Customer Request Type" = "Test" AND ( assignee = Tester1 OR assignee = Tester2 OR assignee =…

Hi @Thinesh -- Welcome to the Atlassian Community! Would you please post images of both of your rules and of the audit log details showing the rule executions? That will provide context for the community to offer suggestions. And please describe the problem you are trying to solve? The what and why (business need), not the…

Hi @Dason There currently is no REST API to manage automation rules. Here is the suggestion to add that capability: https://jira.atlassian.com/browse/JIRAAUTOSERVER-229 If you meant something else, please clarify your question. Kind regards, Bill

Hi @Nicky Mano -- Welcome to the Atlassian Community! What problem are you trying to solve by doing this? Removing the prior sprint values is trying to change the history of what happened, and so lose valuable information the team can use to learn about when/why issues did not finish when expected, and then consider how to…

Hi @John Wignall When the source issue type varies like this, two solution approaches to copy data from the "parent" are to use two rules to limit scope (e.g. a rule for epic to story, and a rule for story to subtask), or to use if/else conditions in one rule. For the second approach, that would look like this: * trigger:…

Hi @Durell Demartini Your rule is stopping processing because of the way the if-conditions are noted. When you want processing to continue, please try using if/else conditions or branches. Such as: * trigger: your selected trigger * if/else* condition: if contains the Storage value* action: create the sub-task desired *…

Hi @pete gormley Here is one of the suggestions to add that ability to hide/toggle the history items from automation rules. You may vote for/watch it to see progress. https://jira.atlassian.com/browse/JRACLOUD-80137 Kind regards, Bill

Hi @Herbert Kevin Yes, and...to Nic's answer: I believe you also asked this question in another post, which describes some work-arounds when you have limited usage scenarios. Otherwise a marketplace addon to enhance JQL features is needed.…

Hi @Dardan Parduzi -- Welcome to the Atlassian Community! In general, when you have an automation rule using the Issue Created trigger and it doesn't seem to do what you expect, add the Re-fetch action immediately after the trigger and repeat your testing. This trigger can fire very quickly, often before the data is…

Hi @Cchristophersonn Galvez -- Welcome to the Atlassian Community! You could add a condition to test if the Reporter is in a list of users to test this. I believe a JQL or user condition would work. Kind regards, Bill

Hi @Herbert Kevin Please see the earlier, noted work-arounds, suggesting exporting the issues for analysis in a spreadsheet (or other tool)...when you need this infrequently. If you need this often, you will need one of the marketplace addons for JQL to help. Kind regards, Bill

The function name is plural and is named openSprints() https://support.atlassian.com/jira-software-cloud/docs/advanced-search-reference-jql-functions/#Advancedsearchingfunctionsreference-openSprintsopenSprints-- Sprint NOT IN openSprints() 

You do not need to add it; it is already present in the backlog when you use a sprint board and have a sprint created. This indicator is not visible for the remainder of the backlog as it would provide no value: by definition, the things in the backlog are not typically in progress or done.

Hi! Please see Yumi's answer about using teams to do this for mentions when editing an issue. Remember to take a look at the reference they provided, as there are multiple things in Jira named "teams" and using the correct one is needed.

Hi @Carlos Massiah That indicator of story points is a feature of the backlog view for Sprints. It is not a feature of the board view. Instead there is are several things like this under the Insights indicator at the right side of the board view. Kind regards, Bill

Hi @Ivan Andrieiev Yes, and...to Jimmy's answer: To get you started on creating your rule, please review this documentation and examples: * https://www.atlassian.com/software/jira/guides/expand-jira/automation * https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/ *…

Hi @Kemal Keskin -- Welcome to the Atlassian Community! Adding on to what Tom and Robert suggested...there is no built-in undo with most Cloud actions for Jira. Instead please consider... * Consider disabling the delete permission, except for site admins * Add a Boolean custom field, named Abandoned * When you would have…

Hi @Facu Cabanne -- Welcome to the Atlassian Community! Jira features out-of-the-box do not send messages to Slack. Your site admin (or project admins) have implemented something to do so: marketplace addon app, automation rule, webhook, homemade addon, etc. Please investigate whatever was added to determine how to adjust…

Hi @Prateeksha Kalyani -- Welcome to the Atlassian Community! Are you using Jira Cloud or Server/Data Center version? Would you please post images of both the Sprint Report from the current and prior sprint, and of the Velocity Report? Those may provide some context to explain what is happening. Kind regards, Bill

I am glad to learn that helped. That issue created trigger can definitely cause timing issues for conditions in rules...here's hoping that gets fixed one day. :^)

Yes, there is...I recommend writing things to the audit log as the rule progresses to see progress. I just did some quick tests and see no problems with rule triggering, for team-managed projects, creating in either the backlog or current sprint. (case # 2, above) Would you please post images of your current rule and of…

Thanks for those details, Martin. I believe you would need several automation rules to cover the different scenarios, including at least these: * when a sprint is started (trigger), check if all of the issues in the sprint have the next unreleased version assigned, and if not, add it * when an issue is created (trigger),…

Hi @Martin Arana -- Welcome to the Atlassian Community! I do not believe the scenario you describe can be done with a single automation rule. However... Would you please describe the problem you are trying to solve? (what and why) Knowing that may help the community to suggest solutions to help. Thanks! Kind regards, Bill

HI @IT-Studentenwerk Goettingen The way your rule is currently built, it will only process until the first condition fails. Instead please try using the if/else condition to handle both cases after issue create. Note the nesting of logic as this will confirm if you have the rule defined correctly. * trigger: issue created…

Thanks, for clarifying! The rule Alex described will help, and the scope of the rule needs to be global/multiple-project rather than in a single project. This means your site admin would need to create the rule, and... You appear to be using the Standard license level for Jira Cloud; is that correct? If so, you have a…

Hi @Suzane Fernandes Cazonato -- Welcome to the Atlassian Community! Adding to Alex's answer... A Jira board is a view of issues in a project. Would you please answer some questions to help clarify your scenario: * Are you saying your boards are in one project or in two different projects? * What types of projects are…