Bill Sheboy Expert

Awesome; I am glad to learn that helped! Two more things: 1) Are the fields required or could they be empty? And if empty, what should happen? For example, you could add default values of zero by adding a |0 default value after each get() call. 2) The division in the formula will produce a floating point number. If you…

Short answer: maybe. For some scenarios, rules using the Issue Linked trigger with no link-types selected will use conditions and branching to handle different link directions. It always depends on the scenario steps done by the person doing the linking. * If your rule is triggering as expected with the "Contains"…

The first is probably null because the leading character is a delimiter (i.e., pipe). And, newlines can be problematic for scenarios like this, more so when using match(). If they are causing trouble, perhaps replace them with another known / ignored delimiter. I often use a double-tilde such as ~~ to get them out of the…

You may want to work with your Jira Site Admin to check with the Atlassian Support team to learn what they suggest: https://support.atlassian.com/contact/#/

Thank you for that information. Without that function in the custom formulas, I believe an automation rule is the only workaround.

If both issues are in the same project, you are correct that single-project scope will work. As the field you are trying to update is multiple-option select, you may need to use JSON to update it if the field types are different...even if the values are the same:…

No worries, and here are more details: After calling the REST API to get the metadata, use dot-notation and a conditional expression, or the match() function with regex, on the web response body to determine if the specific field is present, and if the desired operations are present. Please try doing this incrementally,…

Thanks for those rule images, and... When using the Issue Created trigger, I recommend always adding the Re-fetch Issue action immediately after it. That trigger can fire so quickly that some data may not be available to the rule yet, causing weird symptoms and rule errors. The re-fetch will slow the rule down a bit,…

Hi @Cindy Chan -- Welcome to the Atlassian Community! What license level of Jira Cloud are you using? Your question seems to indicate "Standard", but project archiving is only available for Premium and Enterprise levels: https://support.atlassian.com/jira-cloud-administration/docs/archive-a-project/ If you are on one of…

Hi @Ponce de Leon, Eduardo -- Welcome to the Atlassian Community! Adding to Marc's suggestion, there is even a knowledgebase article for Jira Cloud (based on an even older community answer): https://confluence.atlassian.com/jirakb/automation-to-send-email-only-once-per-assignee-1310985609.html Kind regards, Bill

Hi @Brian Taylor Adding to the suggestion from @Manon Soubies-Camy ... I recommend using a Lookup Table for this scenario. There is even an example in the documentation which nearly matches what you need for a date increment based upon a selection value.…

Hi @ray.geroski Short answer: maybe this is possible, depending upon how you determine from an issue which version is needed. Surprisingly, within an automation rule's access to an issue, all of the project versions are available in the smart value: {{issue.project.versions}} This is independent of the Fix Versions and…

Hi @dania jawad -- Welcome to the Atlassian Community! Adding to the suggestions from @Tomislav Tobijas and @Cristian0791 ... Even with a marketplace app to track changes, some may not be easily visible. The reason is some addons (also from the marketplace) do not make entries in the issue history and instead record…

Hi @Fatima AlZarooni -- Welcome to the Atlassian Community! For Jira's Scrum boards, an issue is considered completed for the sprint when it is in a status mapped to the last / rightmost column of the board. The resolution, status category, etc. have no impact. If your "done" status is not mapped to the last / rightmost…

Hi @Yash Pradhan From what you describe, this is a very specific scenario, even though it is unclear what you mean by "automate the comment sections of tickets..." Thus it may be better for you to work with your own team members to solve this. My recommendations are: * Clearly identify the problem you are trying to solve.…

Hi @Nur Fatin I see you solved your question by simplifying the expression; well done! For future reference, please note the reason your JSON failed is including single rather than double-quotation marks. When you want to use functions such as format() within a rule's JSON, add the asJsonString function at the end to add…

Hi @Shena Goorawa Inside of the branch you show, the "Current Issue" is the one branched-to and not the trigger issue. Thus your rule is copying the value back to itself. Please change the Edit Issue action to copy from the trigger issue. Kind regards, Bill

Hi @BiancaE How is the team doing on fixing the issue with personal email addresses to register? I just checked again and the same error is raised. Thanks, and kind regards, Bill

Hi @kazu okamoto -- Welcome to the Atlassian Community! First, I recommend using a Lookup Table for this type of field mapping: https://community.atlassian.com/t5/Automation-articles/Update-Create-lookup-table-action-improvements/ba-p/2427798 This would allow getting the number in one step:…

Hi @Steve Tedeschi For accessing list elements in a rule, use the 0-based get() function: {{issue.description.match(".*(|).*").get(0)}} or use the first function to get the 0th one: {{issue.description.match(".*(|).*").first}} Wouldn't both of those just return the pipe character?

Thanks for those updates and additional testing. That shows when the Story was created, it did not have a Team value, and...when the Epic was created, it did not have any children yet (which makes sense). Let's review the possible cases and which thus which rules may be needed. I am assuming you are only using Epics and…

Hi @Robin Van Noorwege -- Welcome to the Atlassian Community! For a question like this, context is important for the community to help. Please post the following: * what type of project is this (e.g., company-managed, team-managed, etc.), * an image of your complete automation rule in a single image for continuity, *…

Hi @Jira Billing By default, the actions performed by one rule (e.g., transitioning an issue) do not trigger other rules. This is to prevent errors and run-away looping. When you intentionally want this to happen, in the "downstream rule", enable the option "Allow Rule Trigger" in the details at the top of the rule:…

Thanks for those images, and let's focus on one rule at a time, starting with the Issue Created one. First, when using the Issue Created trigger, always add the Re-fetch Issue action immediately after the trigger. The reason is that trigger can fire so quickly that some of the issue data may not be available to the rule…

Hi @Kim Raham -- Welcome to the Atlassian Community! Short answer: any better / worse methods will depend upon how your product owners are evaluating issues' disposition. For example, if you decided anything requested more than X months ago for product Y is of suspect value, you could mark it as "won't do" using a JQL…

To do this without a custom field, a rule could... Save the value with an entity property instead, or Call the REST API with the Send Web Request action to read the issue history to find assignee. This would likely be a more complicated rule as it will need to test multiple conditions and potentially need to page through…

Hi @Claudia Please post an image of the audit log details, expanding all of the sections / dropdowns. That will help provide context for what is happening. Until we see that... You describe wanting to update the Child issues when the Parent's Team field changes. Then condition to test if the Parent exists is not needed…

Thanks for that information, @Vinícius Pereira as it will help to simplify the rule, reducing the steps significantly. * You have 3 radio button fields, and each one has 5 choices containing text * You are using if / else conditions to check the text values and map the selected value to a number, stored in another issue…

Please post an image of the audit log details showing the rule execution, expanding all of the sections to show the details, such as the issues involved.

At this point, I recommend working with your Jira Site Admin to submit a ticket to Atlassian Support here: https://support.atlassian.com/contact/#/ They may see something we are missing, perhaps in their internal logging. When you hear back from them, please post what you learn. Thanks!