Bill Sheboy Expert

Hi @Juan Meza Have you looked at the math functions yet, like multiply() : https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/ With that you could use: {{issue.timeestimate.multiply(0.1)}} Kind regards, Bill

Hi @Dylan Moore and @Darryl Lee If I am understanding your scenario, what you are trying to do is create a running project work activity report log, using automation rules as follows: * Epics have a custom field named Status Update. Assumption: this is a text field. * A project lead person enters text to summarize progress…

Hi @Brian Noble The components smart value is a list as it can have zero-to-many values, and the smart value is: {{issue.components}} https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/#--issue.components-- And, I believe if you search in the community you will find examples of creating HTML table…

FYI, I am just another customer trying to offer suggestions and share what I know about the behavior of rule syntax, not the design decisions the Atlassian team made. And one reason to test regular expressions (in automation rules) using logging with and without an iterator wrapper is isolation to determine symptom causes.…

This might be a date format difference for the Start Date and Due Date fields. Perhaps try forcing the value with asDate or formatting as jiraDate, and write that value to the audit log to see if it contains the values you expect. Once you have that correct it could be used in the edit.

Hi @Jagmohan That does not appear to be possible yet with the REST API. You may want to follow this post in the developer community to see if there are updates: https://community.developer.atlassian.com/t/page-owner-apis/71284 Kind regards, Bill

Please look at my earlier post in this thread as you still appear to have your conditions incorrectly set up: https://community.atlassian.com/t5/Jira-Software-questions/Re-Re-Automatically-assigning-the-assignee-as-per-epic/qaq-p/2464401/comment-id/287140#M287140

Hi, Emilia. Did the example I provided help to solve this for you?

Hi! Yes, and...when posting a new/related question to older threads only the people following it will see it. Creating a new question gets to a larger audience for idea input. Kind regards, Bill

I am glad to learn the support team offered an idea...and I believe the only reason that will work is Lookup Table's implementation of the get() function can take a parameter, unlike most of the other automation rule functions.

Please try using the Log action, not the Log Work action. The "Log action" will write a value to the rule's audit log, and that can be viewed after the rule runs. You also asked: is there a way to get all issues in an epic in a done state? One way to do that is with the issue search function with the REST API using JQL,…

Once you are inside of an iterator, it can only "see" that scope (and lower). Thus the issue is no longer visible in the example from your earlier post. Your custom field is a list of zero-to-many values, and so using match() alone may not work. Let's try merging the values into a single text string first and then search:…

Hi, and sorry for the delay in responding. It looks like you got it figured out. For the CSV part, I was suggesting using an iterator to add the values to build the JQL. Something like this: labels IN ( {{#userInputs.keyList}}"{{.}}"{{^last}}, {{/}}{{/}} ) That would iterate over the input values, wrapping each one in…

Thanks for that information. Reviewing that other suggested rule in the post, here is what I believe is happening: * In your rule for the Add Comment action, you have selected the option to "Prevent duplicates by only adding this comment once to a particular issue" * And...some of the original, source comments are similar…

The rules you are showing do not match what you originally asked: how to set the Due Date when the Start Date changes, adding on the Original Estimate. Instead the rule you posted seems to be updating the Start and Due Date of linked issues, when the Due Date changes, and setting the Due Date based on some other field.…

Hi @David Leal A couple of things... * There appears to be a typo in the smart value for userInputs in that JQL * Are there multiple values in that input, or just one value? If multiple you may need to parse that into a list to work: CSV with quotation marks around each value. Kind regards, Bill

Nope, looks like my mistake as I left off the quotation marks around the field name on the left-side of the JSON. (I will update that earlier post.) Sorry about that, and I am glad to learn it is working now. If it is all working, please consider marking this one as "answered" so others can find solutions to related needs.…

Hi @Tom Goode Context is important for automation rules... Would you please post images of your complete automation rule, including details of the actions, and of the audit log showing the rule run? Those may help to explain what you are observing and which smart value expression will help. Until we see those... In some…

Hi @Patrick Grech -- Welcome to the Atlassian Community! Adding to this answer... When an automation rule needs to edit issues in multiple projects, the rule must have global scope (rather than for a single project). There are limits on the number of global rules that can be executed each month, based on Jira license…

Hi @Swetha R Please review this documentation page, looking at the diff() function to learn how to do that: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-date-and-time/ Kind regards, Bill

Once the rule is editing a field with JSON, you only reference the field name. Please try this: { "fields": { "customfield_10101" : "1080" } } You noted the value "1080" earlier, so if I have that incorrectly noted, please replace it. 

As I noted, I recommend looking at the developer community and the documentation pages for the REST API. Those both often show simpler examples. However you are unlikely to find a tutorial/guide for "how do I create my own UX to replace the one provided by Jira". Rather if Atlassian tools are not meeting your needs…

There is a rule action named Log which allows writing anything to the audit log. This is helpful to diagnose what is happening / show progress of a rule. https://support.atlassian.com/cloud-automation/docs/jira-automation-actions/#Log-action

Would you please post an image of your current version of the rule? I suspect one or more of your actions is an incorrect type now. And...if possible try to post the entire rule in one image; that will help confirm the rule matches what you are posting. You can capture the entire rule either using a browser addon for…

Hi @sacha_rouzkhosh Please post images of your complete automation rule, including images of the details of each action, and of the audit log details. Those will provide context to help identify what is happening. Thanks!

I am glad to learn that helped! Please consider marking this question as "answered" as that will help others looking for similar solutions. Thanks! For your next question...although I hypothesize labels have attributes behind the curtain, the only things we can see in rules (or the REST API) are the values. When you want…

Hi @Giuseppe Giovinazzo -- Welcome to the Atlassian Community! As this thread is from several months ago, you may want to work with your site admin to contact proForma's support team to learn what they say. Kind regards, Bill

Hi @Boris Gaiman I believe its possible to create a JQL statement to return issues which are blocking (using link type), and so that could be used with the Lookup Issues action. Then you could test that the remaining blocking count is 0 with an advanced compare condition on: {{lookupIssues.size|0}} equals 0 Kind regards,…

Hi @Jay Keck I do not believe that is possible as there are no project-related triggers for Jira Server, automation rules: https://confluence.atlassian.com/automation/jira-automation-triggers-993924804.html Kind regards, Bill

Hi @Rafael Ibanhez First, what problem are you trying to solve by doing this? You note you want to "create an interface", but not why. Knowing that may help the community offer suggestions. Until we know that... Based on what you describe, I recommend you: * Contact your Jira Org Admin to let them know you are doing this.…