Bill Sheboy Expert

Sorry if I confused the situation as I was using myProject as a placeholder for you to enter your project's name. I should have been more clear. __Bill

How many of these "canary" issues do you expect to exist at one time? If only one then: * trigger: issue created * condition: summary = "mail connector TEST issue" * action: delete issue I recommend using a longer and more unique summary to reduce the risks of problems. If you expect there to be multiple, and you want to…

Hi, and sorry I am catching up on the thread. :^) My understanding of {{createdIssue}} singular is that it *always* contains the information from the most recently created issue in the rule...With one exception: there is a by-design behavior that this can get "lost" when issues are created in a branch. (Branches of more…

Hi @Daniel DuBravec -- Welcome to the Atlassian Community! There is a suggestion in the backlog to add automatic/scheduled sync, and you may watch/vote for it here to see progress: https://jira.atlassian.com/browse/JPOSERVER-2861 Kind regards, Bill

Hi @laszlo.fischbein -- Welcome to the Atlassian Community! To view/add/alter issues in different projects with automation rules your rule needs to exist as a global or multi-project scope rule. Depending upon your version and license level this will consume execution counts up to your service limits. One work-around to do…

Hi @Neal Vora -- Welcome to the Atlassian Community! I do not believe that is possible with out-of-the-box JQL. There are suggestions to add search by mentions to JQL, which you may watch/vote for to see progress: * https://jira.atlassian.com/browse/JRASERVER-27594 * https://jira.atlassian.com/browse/JRACLOUD-27594 There…

Hi @Trena Norcia Yes, and...to what Alex suggests: * When reviewing your global rule needs, take a close look at the triggers, especially for scheduled rules* The execution count limits apply when a rule triggers, so if you can adjust things like scheduled rules to include more restrictive JQL conditions, that can reduce…

Hi @Douglas Oliveira Short version: I do not believe that is possible with out-of-the-box automation Longer version: * There are several open defects and suggestions related to ordering of sub-tasks, such as this one: https://jira.atlassian.com/browse/JRACLOUD-42231 * My understanding is that sub-task ordering within the…

Hi @Thomas Vink -- Welcome to the Atlassian Community! Adding to what Nic suggests, you would use a branch to iterate over the issues with that version. For example: * trigger: version released * branch: on JQL for issues with that version (or, just use branch on issues fixed in version)* if condition: issue is not already…

Hi @Chronis Kalfas -- Welcome to the Atlassian Community! Unfortunately due date is not one of the fields supported by the Lookup Issues action: https://support.atlassian.com/jira-software-cloud/docs/smart-values-general/#Smartvaluesgeneral---lookupIssues-- And it may not be added due to the possible performance…

Hi @Prabhu Chilukuri What problem are you trying to solve by charting the information about your custom field, QA Effort? It seems your team is trying to use the Scrum framework, as you note sprints. So wouldn't the work for "QA Effort" be part of delivering any story/task to completion for the sprint? Perhaps consider…

Hi @Ben Please consider posting an image of your rule as that my give the community more context to offer ideas. Thanks! And, you may want to investigate using the text functions to find those mentions in the comment and then replace (or add) the user display name before sending the email. Kind regards, Bill

Hi @mayank goyal Yes, and...to what Nic notes, here are the suggestions to add that capability. You may watch/vote for them to see progress: * https://jira.atlassian.com/browse/JIRAAUTOSERVER-229 * https://jira.atlassian.com/browse/JRACLOUD-77049 Kind regards, Bill

Hi @Evert Morren That is an interesting use case to check for availability. Well done! To find your issue to delete, consider how to make it unique-enough to find while being different from people-created issues. For example, perhaps put something in the summary you can test with a condition, such as "mail connector TEST…

Hi @Zaldy Parian The Atlassian team is working on that, and according to this item it is planned to release February 2022. Please vote for/watch the item to see updates. https://jira.atlassian.com/browse/JRACLOUD-74155 Kind regards, Bill

As the non-working wildcard seems to match just a project check, would the following work? You could limit this with additional filtering on dates (e.g. created, updated, etc.) project = myProject ORDER BY key

When you note "business hours" do you mean a fixed window you want or the range of hours defined in Jira? If you are defining the range you could select that yourself in the expression. If you need something with holiday handling, you may want to build that into the rule. And, I find the CRON in the scheduled trigger a bit…

Hi @Nathan Cunningham If you are still seeing the issue they probably didn't map the field. I haven't tried this for team-managed projects: a work-around you can try if you have the accountId of the user in that field is to call the REST API from the rule to get their email address. Here are a couple of documentation links…

You seemed to be adjusting task dates with a value stored in the task: Visit Task Offset. Is that correct? If so, you could reverse that value in order to find the Epic's date. For example when a story triggers a rule to update their sub-tasks... Epic's date = {{issue.duedate.plusBusinessDays(issue.Visit task offset)}}…

Hi @David Meadow Thanks for the information and suggestions! Yes, and... Regarding "Notify user on failure" we could ask for a "Break" action. This would punch out of a scope/rule and so an if/else condition with an email would satisfy your notification need and allow the rule to still terminate. This would also help with…

Hi @Gavin I do not believe you can alter the Jira behavior, but I wonder if you could instead select an appropriate time-delta and use advanced compare to the second triggering event to {{now}}. That is, when the difference between resolved and {{now}} is above the threshold, reopen the issue. That would require you to…

Hi @Mykenna Cepek and @Julia I think that when you add the task, you can just set the "Epic Link" to {{createdIssue.key}} without the created variable, as that will contain the last created one in the rule...as long as it wasn't inside of a branch. Kind regards, Bill

Hmmm...I see Knowledge Bases (KBs) as more of a library, with the complete list of ideas/issues/features, and taggable/searchable. The idea @Sedera Randria is suggesting seems more like what I have seen from communities of practices (CoP), where the most-recent and of-interest topics percolate to the top automagically to…

Hi, Sue. There are definitely field differences between company-managed and team-managed projects, and changes in how issues are linked. Please take a look at this article to learn some of those differences before trying to move/copy issues:…

Hi @Christine P. Dela Rosa My question is: * Why would one use any "scaled" method before a product/project team has confirmed with evidence that they need something not provided by applying Scrum, Kanban, or Lean ideas? Kind regards, Bill

Well done, James! I misunderstood and thought you generically were accessing the comments and not at the point of Issue Commented. Kind regards, Bill

Hi, Rick. I'm going to try to answer the questions you note, so let me know if I miss something or misunderstand your use case. a) Where to put the create variable: You note the intended trigger issue is an epic, so I suggest adding a condition right after the trigger to check that. Next, as the rule is triggered for an…

Hi, Dennis. Regarding people forgetting to add something, automation rules can help mitigate that. But...let's pause a bit as you seem to be adding new things to your use case, such as oldest/newest epic, etc. What problem are you trying to solve? Knowing that may help focus ideas the community suggests. Thanks!

Hi @louise.simmonds -- Welcome to the Atlassian Community! Team-managed projects use the "Story point estimate" field and Company-managed projects use the "Story Points" field. Kind regards, Bill

Hi @dennis.werner I am a bit confused by what you are asking versus what you are showing as your example. Would you please clarify? You are correct that wildcards for issue keys are not possible, however the ranging you show is possible. For example: project = myProject AND key >= "myProject-1000" AND key <=…