Bill Sheboy Expert

Hi @Mykhailo Goncharov -- Welcome to the Atlassian Community! Without seeing your complete rule or calculation for context... You could try using a list iterator, with conditional logic, wrapped in a math expression. For example, assuming a default value of 0 is okay for the sum: {{#=}} 0 {{#issue.customfield_2345.value}}…

Hi @Michelle Gronwold First thing: this is a very old thread, and so I recommend creating a new question. That will ensure the maximum number of people see it and offer suggestions. When you post your question, remember to include: * your Jira version (e.g., Cloud, Server, or Data Center) * what type of project it is…

That field appears to be a Jira Work Management (JWM), "dropdown" field type, which seems unsupported for format rules and different from a single-selection option field type: https://support.atlassian.com/jira-software-cloud/docs/create-a-format-rule/#Supported-fields-for-format-rules However, I also found other listed…

Thanks for the information, @Cedric Devaux Just to confirm, did this solve the question you originally asked?

Hi @Hend Salem -- Welcome to the Atlassian Community! As this is a very old thread, I recommend creating a new question, and perhaps adding a link to this one. This will ensure the maximum number of people see your question to offer ideas. And also, that error indicates what is says: the person trying to access the…

Hi @Erfan Afthab and @Hans Polder The answer depends upon the field type and markdown used. For example, if your email format is HTML, try that syntax for list items. Kind regards, Bill

I am glad to learn that helped! Also, smart value expressions can be nested / used as parameters in many cases. But in the expression you tried, the issue.summary was contained within a quoted expression and had no tokens to offset it from the literal text. Thus, another way to do this would be to define the initial text…

Hi @Cedric Devaux Have you instead tried using the field change, deleted values, smart values to do this: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--fieldChange-- And, if possible, I recommend making a single call to your REST API endpoint rather than looping to call for each one. Kind…

Hi @lorenzo.betto As automation rules use issue (and other object) events and the REST API to perform actions, I hypothesize there is no way to detect the warnings for an advanced roadmap plan within a rule. (There is no public REST API for advanced roadmap that I could find as an alternative to rule triggers.) To confirm…

Hi @mohit jangid For a question like this, context is important for the community to help. Please post the following: * 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…

Hi @George Remus -- Welcome to the Atlassian Community! For Jira Cloud, use this one: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issues/#api-rest-api-3-issue-createmeta-projectidorkey-issuetypes-issuetypeid-get For Jira Data Center, use this one:…

Hi @Zuri Suwru This approach will not send one email per assignee with their issues. The reason is there is no Advanced Branch in Jira Data Center automation yet, preventing the iteration over the distinct assignees. The workaround I noted in my other post is to use a recursive rule to solve this. Kind regards, Bill

Hi @matt hodgson -- Welcome to the Atlassian Community! For Jira Data Center, there are a couple of ways to do this: Create a saved filter which returns the issues where they will be due in the next 7 days for the current user, and ask your team members to subscribe to it on the desired cadence. Using two automation rules,…

Thanks for the tips, @Dan Breyen I also recommend some additional ideas for automation-related questions here: https://community.atlassian.com/t5/Automation-articles/Automation-concepts-How-to-ask-a-community-question-or-not/ba-p/2683827 Kind regards, Bill

Hi @Chris Carpenter I have observed evaluation-order problems with JSON in the advanced edit for rules, where some smart values are not fully evaluated before the JSON is captured for usage. If you have confirmed that expression works using an audit log write, I recommend pre-building the JSON in a created variable and…

Perhaps try this: { "fields" : { {{#if(not(exists(lookupIssues.first.customfield_10640)))}} "customfield_10640" : null {{/}} {{#if(exists(lookupIssues.first.customfield_10640))}} "customfield_10640" : "{{lookupIssues.first.customfield_10640}}" {{/}} } } You may need to experiment a bit, based on your specific field type:…

Glad to help, and...if you run into challenges creating the expression, please post what you used so the community can help.

Hi @Gaurav Parab -- Welcome to the Atlassian Community! Please try using the Create Variable action to build that replacement expression first, and then use that in the function. * create variable* name: varReplacementText * smart value: <tr><td><p>{{issue.summary}}</p></td><p>Issue URL</p><td><p>Other…

Hi @Katie With built-in features, the only way to do that is to not include the Sprint field in the output. As long as you know the issues are in the current, open sprint, there may be no need to have the column. As a spreadsheet workaround, you could parse the data for each row to copy the last column with a non-empty…

Hi @Dave Stillwell You could try using the text functions remove() or replace() to get rid of the comma before it used: https://confluence.atlassian.com/automation/jira-smart-values-text-fields-993924863.html For example, perhaps try this: {{#=}}{{lookupAsset.attributes.cost.remove(",")}} * {{issue.Number of Units}}{{/}}…

Hi @Tiffany Miller -- Welcome to the Atlassian Community! First thing, I recommend ignoring any bot-generated ideas for a non-trivial scenario like this. Next, I believe this is the scenario you are describing: GIVEN a Confluence page exists with text on it WHEN I select some text on the page AND I select create issue from…

Hi @Andrea Robbins Did you try using an if / else condition, so the comment is only added when the time entry is missing and otherwise the issue transitions as expected? Kind regards, Bill

Hi @Anette Noll To combine those assignment rules, please use an if / else block to select the path needed: * trigger: issue created * action: re-fetch issue (I recommend always adding this after the issue created trigger to prevent timing problems.) * if / else condition* JQL condition: if matches stuff for the first user…

Hi @tkavSQSP -- Welcome to the Atlassian Community! Agreeing with Trudy's suggestion, and... The error you see in the rule editor means the condition / action does not have any issue data to act upon. This is caused when the Scheduled Trigger does not have any JQL to supply issues to the rule. Using that JQL to find the…

Hi @Aslam Mohammed As you describe a Short Text field, which uses plain text, have you tried this expression: "customfield_11605": "New Code not mapping" Kind regards, Bill

Hi @Sean Still -- Welcome to the Atlassian Community! If you start typing the field name in the field, does it filter the list and then appear for selection? Kind regards, Bill

Hi @Jeffrey Crime First thing, for your scenario you are using data from an issue in one project to edit an issue in another project. And so your rule will need to have multiple-project or global scope. Please work with your Jira Site Admin to make that setting change for the rules. Next, as the fields are different types…

Well done, researching and experimenting to find an answer!

Hi @Paulo Amaral Since you posted your original question, it appears the text function now converts account id values to the display name for users, eliminating the need for the chained replace() functions. {{issue.comments.last.body.text}} One side-effect is this will also remove other formatting in the comment body. Kind…

I am glad to learn that is working, and... Data Center automation rules do not support the Advanced Branch over smart values yet and so this technique is not possible: https://jira.atlassian.com/browse/JIRAAUTOSERVER-749 A more complicated approach for Data Center would be to use two rules: the scheduled trigger one and a…