Bill Sheboy Expert

Hi @ngaidakov -- Welcome to the Atlassian Community! 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…

Hi @Shruti Shrivastava For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, and an image of the audit log details showing the rule execution. Those will provide context for the community to offer ideas. Thanks! Until we see those... What…

Thanks for that information, Cody. There are some untested assumptions in your rule, that we assume are valid (or could test for): * Start date and Due date are not empty * Start date is before the Due date * Quick status should not be changed if it is already in the correct value How are you using the Quick Status field:…

Thanks for clarifying, Steven! What you describe for step #3 is possible with a global or multiple-project scope rule. Your Jira Site Admin will need to create a rule at that scope. I wonder...from your original question it seems the problem you are trying to solve is: Our team sometimes discovers work in our backlog that…

Awesome; I am glad to learn that helped. For that JQL, I suspect the challenge is still the direction of links. That complexity is abstracted away when using the Related Issues Condition, without the need to specifically check inward vs. outward and type of links.

Well done! I was using the dropdown field to set the project and did not try using the JSON edit for fields already shown in the Create Issue action, such as project and type. I suspect this technique would also support creating with the one-off issue types and status values in team-managed projects.

Hi @A B -- Welcome to the Atlassian Community! When you discussed this scenario with your team, what did they think was the better approach to try? Why did they think that approach was better? What other approaches did they consider? Having that conversation will help the team decide how to proceed, and give them…

Hi @keerthi For your scenario you describe: * a multiple-select custom field called Customer(s) contains customer names * a text field called Customer ID, intended to hold a CSV list of customer id values for the selected customers in the Customer(s) field The only way to perform that translation (name to id) to then load…

Sorry, I should have tested first: this only works if the list in the variable is the project id values. I will update my earlier post :^)

Hi @Pavani Chintakrindi There should only be one set of double-curly brackets around the smart values in an expression. And it appears in your Manual Trigger's user inputs that you entered a variable name of: {{SystemNamenumber}} When naming a variable, do not include the double-curly brackets. Instead use just the name:…

Please see Trudy's answer, as I suspect it is the sum total of notifications which is exceeding the limit. With just a handful of users it is quite easy to get over 100 notifications: rules, issue update, mentions, account changes, etc.

Hi @Steven Theodoor Bosman-Romein -- Welcome to the Atlassian Community! First, let's align on some terminology to help understand your scenario... * Jira projects contain issues, such as Story, Epic, etc. * A project can contain boards, which are a view to issues in the project based on a saved JQL filter. But the issues…

Hi @Nils Medina Adding to Hana's answer... Smart values are name, spacing, and case-sensitive. And often the smart value does not match the displayed field name on the issue views. To identify the correct smart value (and custom field id) for any supported fields for automation rules. The essential steps are: * identify an…

Hi @Rees, Ian Would you please post an image of the audit log details, showing an example where the rule is "looping" and repeatedly triggering? From what you described, I would hypothesize the rule triggers only twice: * when the triggering text of "update version driver" is entered into the version's Description * when…

Thanks for that information! I suspect your rule is using a scheduled trigger with JQL, or a scheduled trigger with a branch on JQL. In either case, sending automated emails with a free license could quickly add up if they are sent individually (and not in a batch). For example, was the rule tested when being built,…

Hi @doolotaliev1962 -- Welcome to the Atlassian Community! Xporter is a marketplace addon and is not part of the built-in Jira features. Please review the vendor's documentation or contact their support team for assistance with the tool.…

Hi @Cal Leve FYI: I use a Free license site for testing and got some random "you have exceeded your automation limits..." when trying to run rules, with no emails, over the last few days. For your question, the 100 emails / 24 hours is a Free license limit for automation rules. That is different from the packaging limits…

Agreed: there is an opportunity to improve the language of that branch's name / description. What I believe it actually means is "branch to any issues assigned to the version released (for the trigger) based upon the Fix Versions field". It has nothing to do with resolution or if the issue was actually completed. The…

Hi @rob.jeal Short answer: no, that is not fully possible with automation rules, although it can be worked around with additional rules Longer answer: For a scenario that sums a field from child issues to an epic, there are multiple conditions which could lead to a need to sum again... * field value changes in a child…

Hi @Alexey Byzov Please try using the date / time difference function to do that, using the units of measure of businessDays, and perhaps then multiplied by the 8h per day using the function multiply() https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/#Date-difference---…

Have you tried using the Related Issues condition, rather than using all of the extra rule steps? That condition could check for linked issues, of a specific type, and which meet certain criteria, such as "all match specified JQL". And that JQL could check for issues which are completed.

Hi @Chris Timms There was no branching or issue fetching in my suggestion. Did you perhaps post in the incorrect thread? Kind regards, Bill

I understood "what" you were asking, and I did not understand "why" you want to do that. What problem does that solve? What value is provided by copying the comment?

Hi @Cody Brown -- Welcome to the Atlassian Community! Context is important for automation rules... Please post an image of your entire rule (ideally in one image) and an image of the audit log details showing the rule execution. If there are multiple rule executions not working as you expect. please post each log and…

Hi @[deleted] The steps for my test rule are exactly what I listed, although I used a scheduled trigger to exercise a specific JPD idea with JQL. The key is making this a global (or multiple-project) scope rule; that allow the link to succeed, thus updating both issues. Kind regards, Bill

Hi @Jeff Post Regarding item # 1, my hypothesis is: because that dialog box has a cancel button, and "releasing" the version doesn't happen until the assigned issues are confirmed, thus once the rule is triggered the issues moved to another release are not included. I just tested that and confirmed: issued are updated /…

Not two rules: I was suggesting to try to add the linking in the same rule, although it may require doing this with advanced edit using JSON rather than with issue linking. UPDATE: I just tested this and it worked with a multiple-project rule, including the JPD project and the Jira Software one. No need for the JSON edit.…

Hi @Gavin Steele First thing, I have not tried what you ask and my suggestion is based on what I know about automation rules. With that out of the way... I suspect your scenario is possible. When an issue is created in a rule, the {{createdIssue}} smart value refers to that issue and {{createdIssue.key}} (or most recently…

Hi @Uzmii This seems to be a duplicate of your other question: https://community.atlassian.com/t5/Jira-Software-questions/Unable-to-see-the-Release-BurnDown-Chart/qaq-p/2600319 Kind regards, Bill

Hmm...I wonder if it was either posted in the wrong thread or demonstrating candor in regards to resolution focus for the new year ;^)