Bill Sheboy Expert

Looking at the documentation and this post in the developer community: https://community.developer.atlassian.com/t/how-to-add-an-option-to-a-select-list-using-rest-api-in-python/70734 * optionId is used for cascading fields; use id for simple select fields * the id values are included only when updating the value of…

How to pretty print a time measure into business days, hours, minutes There are built-in date time functions to perform difference calculations and format the result. They can even "pretty print" into people-friendly time units. For example, the time difference between issue created and updated:…

As you want to count issues, from the initiative and downward, I believe you on the correct path with the lookup issues usage. And creating each piece incrementally in variables is a good way to validate what you are doing. It is possible to perform this calculation in a single step, using list filtering, but that is…

Ah...the issues are in different projects. I hypothesize you created this rule in a single project, and so it has a single-project scope. Rules in one project can create (or clone) issues into other projects, but they cannot see or edit them otherwise, and linking is an edit (i.e., both issues in the linking change). As…

Awesome; I am glad to learn that helped!

Notice that the closing {{/}} is outside the scope of the table row </tr> and thus impacts the table. Try moving {{/}} to immediately after </tr> and re-test. Regarding the missing issues, I wonder if there is a built-in constraint on the JQL branch to exclude the trigger issue (by automatically adding to the JQL). I know…

Hi @Chance Douglass -- Welcome to the Atlassian Community! I have not tried that one, but I wonder what your request's body options look like. The example in the documentation seems to be an update to add more options. And the existing options are also passed, including their current id values. Kind regards, Bill

Hi @Kelly Hansen 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.…

Thanks for that information. As you are using Data Center version, you do have the Lookup Issues action. After looking at your rule, I realize you may not need it for this case. Instead you can try list filtering on the link type to get the…

This uncertainty is why I asked for an audit logging of each individual created variable: {{KMTotalCount}} {{KMDoneCount}} etc. That would first confirm the counts (and thus the lookups and JQL) worked as you expected, before using them in math operations.

Hi @Ward Schwillens_ Schwillie For the first question, you may try the format() function with a mask to get that 19.58: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-math-expressions/#format-input- Another approach would be to use math and the floor or ceil functions. The second question for pretty…

Hi @Rachana Kandlagunta I am not using the Proforma marketplace addon, and so could offer no suggestions. Instead consider referring to the vendor's documentation for how to automate access to the form fields. If you have rule questions unrelated to that addon... Please post an image of your complete automation rule,…

Thanks for that information. Did you try writing each created variable to the audit log to confirm their values?

Please show the details of the actions to set the values of the variables. Please post an image of the audit log showing the rule execution. That will indicate if there were problems with any of the rule steps. Does your rule trigger include any JQL? For this type of rule, I would not expect it to have any. Have you tried…

Hi @Marcel Varsa 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 @Ramon Mengarda I note in your Send Web Request action, you appear to be trying to use the result of a Lookup Issues action in the URL. But the rule has not used that action first. If you need that, please write JQL to find the relevant issue(s), add the Lookup Issues action to find them, add a condition to confirm…

Hi @John McConnell If you have the account ID for the user, you may mention them arbitrarily, without any field references. However to get their display name, they would either need to be set to a field (and so creating a user object reference) or call the REST API functions with the Send Web Request action to get their…

Hi @Andrew Frayling First thing, I am using Jira Cloud and not the Server version. With that out of the way... There are known problems with the changelog and list-like fields such as Fix Version. Here are a couple of defects for that symptom, which also impacts automation rules due to the symptom:…

Hi @Andrea_Lawrence There are lots of limitations to the built-in gadgets, and many have not changed behaviors in a very long time. And many of the suggestions in that backlog for dashboards are decades old! If how you need to visualize information is not available with built-in gadgets, your options are: * export /…

Hi @salome gogolauri -- Welcome to the Atlassian Community! In addition to the other ideas suggested...in my experience, a good reason to disable the delete permission for all users except org / site admins is to save time, reduce chaos, and protect enterprise assets. Large amounts of time can be wasted debating with users…

Hi @Linda Milne_Togetha Group_ There is definitely a learning curve for the new rule editor UX, and I have noted some glitches / changes in behavior in the last few days... To make a change to an action, one usually must select the Next at the bottom of the action for the changes to persist. And to add to existing…

Hi @Martina Isn't this question a subset of your other one, which has already been resolved: https://community.atlassian.com/t5/Jira-Software-questions/Trigger-tasks-whenever-a-subtask-s-status-is-changed/qaq-p/2607873 Thanks! Kind regards, Bill

Hi @Flavio De Souza I suspect the answer is "no". The manually triggered automation rules appear to be started by Jira code, not a URL. Perhaps consider what problem the manually triggered rule was trying to solve, why it is believed a link in a comment would be more likely to help, and then evaluate if changes to issue…

That is odd, if you are using one of the built-in cascade select lists. Would you please confirm the following: * What type of project are you using: company-managed or team-managed? You may find this at the lower-left side of the page's expanding area. * What is the exact type of that field? For company-managed, you may…

Hi @Ward Schwillens_ Schwillie First thing, as this is an older thread I recommend creating a new question and perhaps adding a link back to this one. Otherwise only the people following this one will see it to offer suggestions. When you create your new question, please include images of your complete rule, the action…

A very simple example could be: * trigger: field updated for Start Date or Due Date * branch: over the linked issues of any blocking types you want to check* condition: check if the issue has an assignee value * action: send email to the assignee, notifying them of the change to the trigger issue You may use the…

In your original rule, you iterated over the lookup with this: {{#lookupIssues}} using the data for the table, such as {{key}} and {{summary}} {{/}} Now using bulk-handling for issues, it would be this: {{#issues}} using the data for the table, such as {{key}} and {{summary}} {{/}}

I am glad you got something to work! Although it is curious adding that expression to the JQL branch did not work, showing "field 'parent' is invalid." It would have been valuable to see both the actual branch and the audit log for that case, as I tested it before I posted the suggestion.

For the branch, please try adding this: AND parent = {{triggerIssue.parent}}

First, if this rule should only process for subtasks, please add a condition after the trigger (or add to your JQL condition) for issuetype = subtask. Next, do you want to find the one which has the same parent issue? If so, please add that to the JQL for your branch.