Bill Sheboy Expert

What is your field type? I wonder if you need to convert first with asNumber before the test if the fields are text type...Conditional checks do not work with text fields, I believe. For example you could try: {{#if(issue.totalIssuesForTHmvpAssignee.asNumber.gt(0))}}Is greater than zero{{/}} Please note that you use the…

Hi @kevin Muñoz -- Welcome to the Atlassian Community! You may do that with an automation rule. For example: * trigger: issue transitioned to QA status * action: assign to the team member To learn more about automation rules and see examples, please look here:…

Hi @[deleted] When you note "it only does not work for tickets created automatically from another tool", what is the other tool which is creating the issues? For example, is it an addon or application your team/company has created? If instead it is another automation rule, there is an option in the rule details for "Allow…

Hi, Matthew. Please try using match() with a regular expression, and then check that the result is not empty to then add the relevant labels.

Hi @Mathilde Courtat In the rule image you posted, the Send Email action is outside of the branch...and so the email will always send regardless of the count. To make it conditional, move the Send Email action inside the branch and after the Condition test. Kind regards, Bill

Hi @alexanderlanden -- Welcome to the Atlassian Community! Yes, that should be possible using the conditional logic functions for smart values. Just test if your value is not zero to proceed...or use a greater than test and check that for "true". Please look here for more information on conditional logic:…

Hi @Pramodh M Just an FYI... I also recommend adding the Re-fetch Action after the Issue Created trigger when such symptoms occur...and I would not characterize it as a "best practice". It is a work-around for a defect in the automation engine and/or REST API, whereby the event is firing before the event has completed…

Hi, Simon. I think the field's smart value is either "timeoriginalestimate" or "Original estimate", and to get just the sum for the lookup issues is: {{lookupIssues.Original estimate.sum}} You should not need the loop/iterator to do that. By the way...when you need to confirm a field's smart value you can use this how-to…

Hi @Jeremy Deremer This appears to be the defect you are noting, and you may vote for/watch it to see progress: https://jira.atlassian.com/browse/JWMCLOUD-166 Kind regards, Bill

Hi @Paul Jentzsch For a question like this on automation rules, please consider posting images of your complete rule and the audit log, with details. That will provide context for the community to offer suggestions. Thanks! Next, I recommend putting the group name in another field, such as either a component or a label…

Hi @Niccolo Ossude When you are inside of the lookup issues iterator, just refer to the field name's smart value and not {{issue...}} Then you would just need {{parent.summary}} inside the lookup loop. Kind regards, Bill

Hi @Celina Kim Would you please expand the details in your audit log for an execution that didn't work as expected and post that image? That will show the specific issues (subtasks) found and which ones the rule attempted to transition to "closed". And, try to find an example issue which did not move all of the subtasks to…

Hi @Sergi Ortega Are you asking about calendar time in status or something else...such as the time tracking fields? If you mean calendar time... You noted trying the built-in reports in Jira. Did you try using Atlassian's interpretation of a control chart, and selecting just your fields of interest and timeframe? Please…

Hi @Shakthi Oke How do you intend to use this information and how frequently do you need it? The answers may help you decide solution approaches. For example, you could create a filter to find issues created today and which are due in less-than-or-equal-to 7 days, save the filter, and then subscribe to it for a daily…

Hi @Aleksandra Lysenko -- Welcome to the Atlassian Community! Would you please check on your releases (versions page) to see if the version is archived? I recall seeing a defect that once a version is archived it could not be saved in the fixVersion field...and...it does not show that condition as an error. Kind regards,…

Hi @Simon Huprich The work-around of using story points to hold the original estimate values is no longer necessary when using Jira Cloud...Lookup Issues now supports all of the issues fields, and so you should be able to sum on that field directly from a lookup. Kind regards, Bill

Hi @Esteban Ramirez -- Welcome to the Atlassian Community! I have not found a way to size the table columns with the markup Atlassian is providing. The closest I got was to use additional characters in the heading for more width. And when the fields draw on the page, they dynamically adjust based upon the field width. Kind…

Hi @Sachin Manjaiah Would you please post images of your rule and the audit log details? That may provide context for what is happening. Thanks! Until then, I suspect that the condition in your rule is testing against the field alone...which would return the ID for the selected value. But the dropdown field's value has…

Hi @Nicolle Diniz If you look at the error messages below the field, it is showing the unknown field "Custom Field Name" in the JSON. Perhaps clear that information from Additional Fields and get your edit to work first, then try any additional edits. For your edit of the "Ticket - Total" field, please remove the extra…

Hi @Lex Kovalenko _Appfire_ As you appear to be a vendor of a competitor product from Spartez Software, please consider immediately disclosing that in your posts about recommendations. That would be aligned with the Atlassian Community online guidelines for Marketplace and Solution Partners. Please look here for more…

Hi @Paul Campbell Mentioning a group is not possible yet, and here is the suggestion to add that feature: https://jira.atlassian.com/browse/JRACLOUD-75999 Two possible work-arounds, one more brittle and one slower: * hard-code the list of values (either in the rule or an entity property) and iterate over it to create the…

Hi @BrentBot You mentioned me for input on this question, so...In my opinion: * Jira could do a better job managing and measuring team's workflow; * This is why there are so many vendor addon products to enhance this area; * I suspect that as Jira does not appear to manage workflow change in histories, built-in or addons…

Well done!

Hi, Justin! Please try dropping the parentheses and just use the accountId values and commas, like this. Remember to use the actual accountId values and not the names. userId1,userId2,userId3 Then in your advanced branch, split them like this, substituting your variable name for myVariableName:…

Hi @Ed St. Louis First thing, I do not have advanced roadmaps so this information is from the documentation... It appears they have removed the ability to set that information from the UX, according to this…

Thanks for that information. If I understand your case correctly, you want to automatically add an issue when the sprint is created. Using the trigger of sprint created, you should not need to perform any additional tests as the sprint will be empty if just created. Perhaps try this: * trigger: sprint created * action:…

Hi @Raakhee Nagaonkar -- Welcome to the Atlassian Community! Your board image indicates this is a team-managed project. To show the subtasks on that type of board you select the Group By > Subtask option at the right side of the board. Kind regards, Bill

Hi @Karoline Rezende Ramos Yes, you may do that based on the values changing for a subtask, and then update the parent based on the min/max in the other subtasks. Please review the Lookup Issues action to help you gather the subtasks and then find the min/max for the…

Hi @Ferran Salcedo -- Welcome to the Atlassian Community! Yes, you can do that. Please take a look at the match() and other text parsing functions to see what helps: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/ Of note: I have found the regular expression parsing in automation rules…

Hi @Mark Segall For my Jira Cloud instance, that feature only shows the last 8 rule executions run against an issue. Are you seeing something different? Thanks, Bill