Bill Sheboy Expert

Hi @André The math functions like gt() only work on numbers (and supposedly dates / time numeric values). Have you confirmed "billable" is a number type rather than text representing a number? The function isNumeric() only tests if the value contains only numbers, but not that is is a number type. You could validate that…

Hi @Gile Empey Rules with a single-project scope may create (or clone) issues into other projects, but not otherwise access or update them. When a rule needs access to issues in multiple projects, it needs to be multiple-project or global in scope. To enable this, your Jira Site Admin will need to configure the rule in the…

As you have a defined structure needed, I believe you will need to hardcode it all or use inline conditions to selectively add the elements based on their presence / absence: https://confluence.atlassian.com/automation/jira-smart-values-conditional-logic-1081351607.html

For your specific questions: 1. Is there any possibility to have any running variable in a loop, that can be used even after the loop. Answer: Not with automation rules currently. As such rule branches run in parallel and asynchronously, they apparently do not share any storage that could be used for such a variable. Using…

Sorry, I should have tested that earlier post rather than just typing it in. It appears joining the fix versions adds square brackets for array notation, so I added a substringBetween("[", "]") call to remove them. Please see the adjustment I made to capture varCurrentFixVersions. Update: the above statement handled the…

Hi @Tacictus Anon -- Welcome to the Atlassian Community! When using Send Web Request in a rule to contain all supported fields in the issue, try sending the issue data in the web request body. That is one of the options in the action. To learn what smart values / fields are probably, currently supported, please use this…

If that is the board filter, you are using a company-managed project. Team-managed projects do not support configuring the filter manually. Also...your filter does not have an ORDER BY clause at the end. The drag-and-drop feature to re-order issues on the board and backlog only works when the board filter ends with ORDER…

When I try that same smart value expression with two date fields it works and returns 12 months. Let's try this to help diagnose what is happening: * Using the Log Action, write the following to the audit log before you create the variable. Please note I am using the exact same smart values you noted. start date:…

This confirms the initial parsing to get the date in the variable is incorrect. Please show an example of, and write to the audit log, the Summary for the trigger issue as that will help confirm how to adjust the parsing. That will also help when the rule fails in the future as... This is a risky rule / solution approach.…

Hi @lila This is similar to the other scenarios, and the link direction is just reversed: Epic --- implements ---> Idea Because a rule like this is updating both issues, it will need to be multiple-project in scope. Your Jira Site Admin will need to help configure such a rule. Your rule could look like this (plus the…

Smart values are name, spacing, and case-sensitive, and they may not exactly match the displayed name on the issue pages. When an incorrect smart value is used, it returns null and so often fails silently in rules. To find the correct smart value (or its custom field id) please use this how-to…

When inside a set of double-curly brackets, another set is not needed. Please try this: {{now.plusDays(endDate.asNumber)}} If that also does not help... Please post an image of your complete automation rule and an image of the audit log details showing your rule execution. Those will provide context and may help explain…

Please review the solution I suggested, as it appears you have the Re-fetch Issue action in the incorrect location: https://community.atlassian.com/t5/Jira-questions/Re-Automation-Rule-Add-a-Cloned-Epic-parent-to-its-Story/qaq-p/2756322/comment-id/1034373#M1034373 For your second scenario where the Story's Parent changes…

Hi @Louise Baker When a rule edits a field, it is based on the issue's data at the current time, usually the time was rule triggered. The edited data is saved in the cloud, but not updated in the stored values within the running rule. (This helps with some use scenarios and yet can confuse rule writers.) And so when you…

Thanks for that additional information. For an example of what I meant by the Re-fetch Issue actions... * trigger: some trigger with an issue * action: edit issue for some field * action: edit issue for another field In this example, the edit in step #3 is based on the issue and data conditions at the trigger timeframe,…

First thing: if the version update with Edit Issue is taking so long it requires multiple Re-fetch Issue actions to succeed, you may want to use another method (i.e., the REST API call). One of those re-fetches should have been enough for this type of update. Moving on with what you have started already... In this case,…

Hi @André -- Welcome to the Atlassian Community! Without seeing your entire rule, or understanding the problem you are trying to solve (i.e., why do this), I note three things in what you show: * The rule makes edits to the issue, one after another* When an edit occurs, it uses the issue state at the time the rule…

Hi @Leanna Bremenkamp To help provide context for the symptom you are seeing, please post images of the following: * your complete automation rule * the Lookup Issues action where you gather the issues * the Send Email action where you use the lookup results * the audit log details showing the rule execution Kind regards,…

Hi @ishanu.chatterjee -- Welcome to the Atlassian Community! There is nothing built-in which can do that. For some workarounds, depending upon the number of rules you have, the output format you want the output, and the technical skills of your team: * Navigate to the global rule list, set the count limit to 200, and use a…

Thank you, and I suspect you may be limited to 5 minute granularity for automation rule triggering. Perhaps the custom field values could be constrained to 5 minute granularity when they are set, or ignore the specific values and just test when value is less than {{now}}.

Hi @jeff.kehler Yes, and...to Jack's suggestions... Once you have learned about making the updates with JSON to "add" a Fix Version, there are several ways to identify the earliest unreleased version to add it: * assuming there are other issues already assigned to that version, you could use Lookup Issues to find an…

Hi @Durgesh Masurkar What problem are you trying to solve by having that level of precision in the rule triggering to transition an issue? That is, "why do this?" Knowing that may help the community to offer additional suggestions. Kind regards, Bill

Hi @Malene Vikkelsø As your rule is triggered from the subtask, you could ignore the specifics of the pre-defined subtasks and instead find all sibling subtasks which have the same parent: project = yourProjectName AND issueType = Sub-task AND parent = {{triggerIssue.parent.key}} That could be used with a related issues…

Hi @Jamien Price First thing, I am not currently using JSM and so I cannot test my suggestion. With that out of the way... I recommend checking if the Attach Forms action can take a smart value to select the form. If that does work, you could try: * using the Create Lookup Table action, add rows for each form, where the…

Hi @MrAldimensch -- Welcome to the Atlassian Community! What is the scope of your rule, listed in the details: single-project, multiple-project, or global? I suspect it is single-project. Rules with single-project scope may create (or clone) issues in other projects, but they may not access or edit them otherwise. Please…

Hi @Sherwin Soriano Although you could use Jira permissions to manage this, what do you want to happen if the project admin is unavailable when a sprint is being planned? The symptom you describe may have additional root causes leading team members to alter sprint scope without the participation of the entire Scrum team.…

Hi @Jeremy Jedlicka Your expression to perform the date difference is missing the closing double-curly brackets }} {{#=}}ROUND({{triggerIssue.Target start.toDate("yyyy-MM-dd").diff(triggerIssue.Target end.toDate("yyyy-MM-dd")).days}}*0.1,0){{/}} When writing expressions like this, you may want to create them in a text…

Hi @Dailet Yes, and...to Trudy's suggestions... You describe this scenario: GIVEN Issue A --blocks-->Issue B with issue linking AND Issue B is in the Blocked status WHEN Issue A transitions to Done THEN transition Issue B to To Do Can Issue B be blocked by more than one issue, such as: Issue A --blocks--> Issue B Issue C…

Hi @Bhumi Yadav -- Welcome to the Atlassian Community! The smart value {{issue.comments}} is a list of values, each one with structure including the body, author, etc. of all the comments: https://confluence.atlassian.com/automation/jira-smart-values-issues-993924860.html#Jirasmartvaluesissues-issue.commentsissue.comments…

Hi @Nena Kruljac 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.…