Bill Sheboy Expert

After some testing... The conditional expression may be used directly in the field for text and number fields, but I was unable to find an expression that formatted correctly for a date or date / time field. Instead it showed the error: ...must be of the format "yyyy-MM-dd". The same expression works for advanced edit with…

Hi Caleb, You appear to be using Jira Data Center, correct? If so, please try the Lookup Issues action with JQL to find the needed epic, and then use the result when setting the epic link to: {{lookupIssues.first.key}} You can build the JQL to find your needed epic with the date / time…

Hi @Janany Satkunam Are you using Jira Cloud? And if so, are you using a company-managed or a team-managed project? You may find that information and the bottom-left of the screen expanding area on the page. Company-managed projects use the "Story points" field and team-managed projects use the "Story point estimate"…

Hi @Shaun No, that is not possible. Although for the example you show, could you combine the criteria to perform a single check, as there is no rule action / edit between the two conditions? If you really want to do what you asked, you could instead: * use a Lookup Issues action with JQL to gather the first set of issues *…

Hi @Dennis Rünzler In my opinion, working on one thing at a time until done is great for managing WIP, reducing team stress, and to improve value delivery flow. Yet, using an automation rule to manage that may create unintended consequences of people hiding work, or no longer tracking work in Jira. Additionally, this rule…

Hi @Enache_ Bogdan _Allianz Services_ As your table row is generating inside of the lookup issues iterator, this should work (depending upon the field type): {{customfield_38901.value}} However...what version of Jira are you using: Cloud, Server, or Data Center? If you are using Server or Data Center, the lookup issues…

Hi @Trudy P Claspill That is the short-form version of the conditional logic expression (although there is a typo in shown rule for the location of the parentheses): https://support.atlassian.com/cloud-automation/docs/jira-smart-values-conditional-logic/ However...many field types do not work with the isEmpty() function,…

Hi @Andreas Safar Would you please explain how that works? There is no Lookup Issues action in your rule, and so {{lookupIssues}} is null, and so the entire expression is null...meaning it cannot remove any watchers. Thanks, and kind regards, Bill

Hi @Admin OKZT What problem are you trying to solve by doing this? That is, "why do this?" Knowing that may help to reveal solution options. Until we know that...there is nothing built in to provide a single field for the number of days since the issue was created. Some workarounds are: * Use the built-in control chart to…

Hi @Dąbrowski Damian Are you trying to send the message for the newly created issue? If so, please add a branch to the rule. Otherwise the rule cannot "see" the issue. * trigger: scheduled * action: create the task * branch: to most recently created issue* action: send the Teams message Kind regards, Bill

Hi @koutarou ishibashi Yes, and...to John's suggestions: When summing / counting issues in a parent for child issues, I recommend completely recalculating the value spanning the child issues rather than just doing an increment / decrement. That will ensure there are fewer errors due to timing / rule engine problems in rule…

Hi @Kristine Lurane Just to confirm, would you post an image of your entire Clone Issue action, perhaps using a scrolling browser, image capture? Until we see that...this symptom could be reported when: * The edit issue action is trying to set the field twice, once with the dropdown list and once in the JSON. From what you…

Hi @Mark Lendrum -- Welcome to the Atlassian Community! This scenario and solution approach has changed several times in community posts. Please try this one: {{issue.comment.last.body.split(" ").match("\[~accountid:(.*)\]").distinct}} That will produce a list of unique user account id values that were mentioned. Kind…

Yes, and...the Current Issue {{issue}} changes based on scope within the rule. The Trigger Issue {{triggerIssue}} is constant throughout the rule (other than when changing for a scheduled trigger with JQL iteration). For example: * trigger: ... Trigger Issue, Issue, and Current Issue are the same * condition: ... Trigger…

First thing, the Epic Link field was sunset last year, and so I recommend specifically trying to test on the parent field. The parent field is now used for all parent / child relationships. Epic Link may still work, but it is better to use parent in the event Atlassian removes the old field in the future. Given your…

Thanks for the additional information. What do you think of leaving the labels until the sprint starts, and using the Sprint Started trigger to then remove the labels? That will confirm it is the active sprint. A second rule could use the issue field changed for Sprint to detect, with a JQL condition, if an issue was added…

Both of those conditions cannot be tested at one time for a rule trigger. Two different rules could be used, with the different triggers, and added conditions. However, it will be challenging to detect the status transition later when the trigger is on the sprint field. Let's back up a bit: * What problem are you trying to…

To clarify a bit, what does "duplicate" mean for the scenario: * another issue exists with specific text in the Summary field * something else? If it is the Summary check, perhaps try this: * trigger: value changes for Components * branch: to current issue* condition: component contains "X" * related issues condition, with…

Hi @Campbell, Scott -- Welcome to the Atlassian Community! That appears to be a difference between the versions, and here is a suggestion to add the feature for Jira Cloud. You may vote for / watch it to see progress. https://jira.atlassian.com/browse/JRACLOUD-82533 Kind regards, Bill

Hi @Josh H_ I have not tried to do that, and I wonder if you could call a REST API function to create the meeting using the rule's Send Web Request action. Perhaps try an internet search to find any supporting REST API to do so. One additional challenge may be finding the data for the attendees to include in the request.…

Hi @Deepika This is similar to the use case to update a Parent issue to the child and grandchild issues, and can be done with one rule. However for your scenario, there is a risk of duplication between links and exceeding the branching limit of 100 issues. If you still want to try this approach, it could be like this: *…

Hi @Bryan Kim 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 @Sia (Nastassia) Sharasheuskaya -- Welcome to the Atlassian Community! It appears there is a required field for your Bug issue type that is not set. Please check what may be missing and include that when the issue is created. Hi @John Funk I believe the "current issue" is the trigger issue for the rule shown, and not…

Hi @BenWade The rule seems to do what you ask (i.e., remove a specific label), triggered when you want it to run (i.e., when the sprint field changes). What type of improvement are you considering? Do you need to check for assignment to a specific sprint? Kind regards, Bill

Hi @roberto_sc You could do this using conditional logic (to return the value for the fields) or use lookup tables to translate the fields into their numeric values. Then, perform the calculation with a math expression. Kind regards, Bill

Hi @Rita Arellano You could first check if the issues exist before creating them... * When using multiple rules, one for each component value, you could first check if the issue already exists (using JQL or Lookup Issues and checking the found issues), and only created it when it does not exist. * When using one rule, with…

Hi @Brandon Fish For your step 5.2 if the userID is the assignee of the task, then add the country as a label, to which issue are you adding the label: * the trigger issue * something else If it is to the trigger issue, I suspect you could collapse the logic to one branch, always updating the trigger issue with either no…

Hi @Jaina Mistry 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.…

I have not tried this webhook trigger approach, and... I wonder if it is covered by the looping limit (i.e., maximum of 10 loops) and so could halt the rule, or if because the trigger is a webhook, it "breaks" the detection chain and so is not detectable that way, allowing for many more than 10 issues to be created.

I am glad to learn you have something that worked. The three possible reasons it did not with the other syntax are: the extra / incorrect quotation marks, the extra spaces in the expression, or for the Object it did not resolve inside the function. One way to check stuff like this is to write it, piece by piece, to the…