Bill Sheboy Expert

The difference appears to be a mathematical difference (i.e., 12 - 6) and not an inclusive one, counting the end points.

The rule will need different / additional steps when testing for the linked issues. The previous change I described for issueType IN ( "Story", "Task" ) is not needed. Are you using Jira Server or Data Center version? The following will only work if you have the Lookup Issues action with Jira Data Center (or Jira Cloud). *…

To confirm: the Epic can have child issues which are Story or Task type, correct?

Hello again, How about a workaround for the absence of global, sprint-related trigger? Your Jira Site Admin will need to implement this one. The way this works is a site webhook sends a message whenever a sprint is started. That message triggers a global automation rule, and the sprint id value may be used to find the…

Hello, all! Yes, and...for the global, sprint-related trigger idea, here are the suggestions to add that feature for automation rules: https://jira.atlassian.com/browse/JRACLOUD-80707 https://jira.atlassian.com/browse/JIRAAUTOSERVER-68 Kind regards, Bill

Thanks, Trudy! I did not know that one.

Thanks for that additional information. For the JQL in the rules like this: issueType = "Story" Please change them to this so both issue types are included: issueType IN ("Story", "Task") You may learn more about writing JQL like this with this free training and documentation from Atlassian: *…

Hi @Andreas Sundvall Are these the same type of project: team-managed vs company-managed, software vs work management, etc.? I have seen weird symptoms with issue create and linking in rules. The REST API is documented as supporting adding zero-or-one link at the time of creation, and I hypothesize rules instead do that in…

Hi @Ken Young Not yet... Last time I checked this was 2 months ago, and changes to approver did not mark the version as "updated" or raise an event automation rules can see. I also did not find any open suggestions to add this in the public backlog. Kind regards, Bill

Hi @Madar, Andrew For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Esteban Pisera -- Welcome to the Atlassian Community! In your Create Issue action, I see you selected the option "Same project". That will try to use an issue from trigger to find the project, but there is no issue to use. And, I do not believe there is a way to supply the project as a smart value using the Issue…

Hi @Adrian Avalos For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected. Those will provide context for the community to offer ideas.…

Hi @Manav Shah As a short answer: I doubt the scenario you describe can be solved with the built-in automation rules of Jira. Perhaps consider other solution approaches outside of Jira to identify and create the issues. For more details... You describe gathering 10% of issues for each of over 300 users, placing them in…

Would you please clarify what worked and what remains to be done? It seems you are asking for the same things which were already suggested. Thanks!

Hi @Jason Rogers -- Welcome to the Atlassian Community! Please move the Re-fetch Issue action up to immediately after the trigger and re-test. The Create Issue trigger can fire so quickly some issue data may not yet be available to the rule. This can lead to failed conditions, and sometimes rule errors. The fix /…

Hi @BenWade Would you please confirm what you are observing: * when an issue is cloned, the Parent field is also copied to the clone * when an issue is cloned, the entire Parent issue is also cloned For the rule you show, the second one (clone the Parent issue) is not caused by that rule. Something else is causing the…

Hi @Mihai Mot Adding to John's suggestion, to get you started on creating your rule, please refer to these documentation and example sources: * https://www.atlassian.com/software/jira/guides/automation/overview#what-is-automation *…

Please re-read what I described earlier... For your first rule you show, triggered by the Epic, the Related Issues Condition is incorrect. I believe you want to use this: * related issues: Children * condition: None match specified JQL * matching JQL: issueType = "Story" AND summary ~ "Pre-Assessment" AND status != Done…

Hi @Matthias Rickheit -- Welcome to the Atlassian Community! Without seeing your entire rule, let's assume some things: * this is a date picker, custom field created in the global site settings * you are doing this with a company-managed project Any of these three methods will work for such fields with the Edit Issue…

Thanks for clarifying the scenario: GIVEN a list of Customer Case issues AND a Customer Case issue has links to other issues WHEN one or more of the linked issues is a Bug THEN return the Customer Case issue's data in a list of issues Doing this one-by-one with JQL in a rule is possible using the built-in issue linking and…

If this is a single-selection field, please see the example I noted. Your lookup table rows could be something like this: Key Value alice@domain.comSTC bob@domain.comCorp eve@domain.comMODEand so on... Please look here to see more examples for using Lookup…

Hi @Phil That is not possible when using a branch to loop over issues in the rule. Branches which could be on more-than-one-thing are processed in parallel and asynchronously. There is no guarantee when such a branch will finish, up until the last step of the rule. Please look here to learn…

Hi @Michael Tai Yes, and...to Kalyan's suggestions: I recall there can be differences in rules for some fields which were never set (i.e., null) versus set to a value and later cleared (i.e., now an empty string). Worse still, the behavior may be different for the same field when the issue is an element in a list versus a…

Hi @Tomas Franco -- Welcome to the Atlassian Community! Do you mean a Custom Formula field for a Jira Product Discovery (JPD) project? If so, I believe those field types are dynamically calculated and do not return values with issue searches or automation rules. I just did a quick test and the REST API issue functions…

Hi @Anele The smart value {{now}} is a date / time value, and I suspect your "Follow up date" field is only a date field. Perhaps use a format for the dates to ensure they compare accurately for those text comparisons. For example: {{Follow_up_date.jiraDate}} does not equal {{now.jiraDate}} Kind regards, Bill

Hi @Eelco Haeser -- Welcome to the Atlassian Community! From what you describe, I do not believe you need smart value, list filtering as you tried. Instead, modify your JQL to search for issueType matching what you need and then list all of the issues found by Lookup Issues. For example: project = yourProjectName AND…

Hi @kyle -- Welcome to the Atlassian Community! By default, the actions of one rule cannot trigger another. This prevents errors and runaway looping problems. When you intentionally want the actions of one rule (i.e., Rule 1) to trigger another (i.e., Rule 2), please look in the details at the top of Rule 2 and enable the…

Hi @Froukje van de Weg -- Welcome to the Atlassian Community! As the person who handled release notes earlier has left, please consider discussing with your team how it worked before. Specifically, you may want to learn: * where is historical release information located * where was information about newly / pending release…

Hi @Sidharth verma I have not used that approach, although I have seen community threads describing examples of it. The basic approach is: * Create a webhook triggered rule, with only a log action, and save it. This is the rule which will eventually loop.* Disable the rule. * Copy the webhook from that rule and save it…

Thanks for that information, and please stay with one thread when responding. That will help others in the future looking at this question to know if there are multiple solution approaches. You are using Jira Server or Data Center version of automation. The Lookup Issues action for those does not support the time tracking…