Bill Sheboy Expert

Thank you for the additional information! I completely understand the challenges of more-regulated environments and tool support. As an aside: Argh! I am not a fan of the "improved" audit log format as it makes it much more difficult to diagnose rule problems quickly. Definitely a step backwards in usability. (sigh) Back…

Hi @Nathalie Kaspers -- Welcome to the Atlassian Community! As this is a very old thread, I recommend creating a new question. That will ensure the maximum number of people see it to offer suggestions. And when you create you new question, please include: * an image of your complete rule * images of any relevant trigger,…

Yes, and...from the documentation: If you move an issue to a column where it's previously been, the indicator provides the cumulative number of days that the issue has been in that column. For example, you move an issue to the In progress column, and it stays there for two days. You then move the issue to the Code review…

Hmmm...I clearly did not ponder other scenarios when considering the removal of "discussions" for product areas :^) For example, I want to gather ideas / feedback about a recent change to automation rules, perhaps to add a new suggestion for Atlassian. Yet my only options are a "question" (which this is not as there is no…

Hi @Aline Veyradier Adding to the suggestions from Marc... Please note an issue's Sprint field is a list of values. Thus when an issue "carries over" as incomplete from a prior sprint, the field now contains at least 2 sprints. Thus it will help to know when you want to set the Start Date and Due Date values, and what they…

Hi @Aaron Pavez _ServiceRocket_ The custom field appears to contain a list of links, with a comma delimiter. Is that correct? If so you could use the list and text functions to help parse the data: * use the split() function to separate the values * use inline iteration to walk over each one * extract the ID values with…

Hi @Inderaj Chem -- Welcome to the Atlassian Community! What you are describing is the Jira Move operation: moving an issue from one project to another. https://confluence.atlassian.com/jirasoftwarecloud/change-an-issue-s-project-or-issue-type-using-the-move-feature-1283493350.html Different projects have distinct…

Hi @Ann Rumenapp Adding to Jack's suggestions... I do not see any errors in your rule's audit log; instead it shows conditions were not met and a transition did not occur (which could happen for various reasons). And does that message "Unable to run this component" appear in the log or in the rule editor? Please post an…

Hi @Emmanuel Please check with your Jira Site Admin and the app vendor to learn the cause: https://marketplace.atlassian.com/apps/1230970/airsaas-ppm-flash-report-tool-for-jira?hosting=cloud&tab=support Kind regards, Bill

Hi @Michael Farid -- Welcome to the Atlassian Community! I do not believe restricting work logging as you describe is possible with built-in features, including the use of the REST API and automation rules. Please note automation rules trigger after an event has occurred, and so could only undo rather than prevent actions.…

Hi @Ron Aisen As written, your rule is assigning the trigger issue. To assign the new Sub-task, add a Branch to Most Recently Created Issue after the create and before the assign action. Kind regards, Bill

Hi @Sabiha Micallef -- Welcome to the Atlassian Community! There is no built-in dashboard gadget with that name: "Number of tickets per filter". Here are the current built-in gadgets: https://support.atlassian.com/jira-cloud-administration/docs/use-dashboard-gadgets/ Kind regards, Bill

Hi @Narsha Bachoo For automation questions, please also post an image of the audit log details showing the rule execution. That will provide context for which steps processed and the issues impacted. Until we see that... Please post the text you are using for that JSON expression, and not just an image of it. And, are you…

Awesome; I am glad to learn it is working! Please consider marking this question as "answered" to help others with a similar need find solutions faster. Thanks!

Hi @Alex Burka I recall there are several open suggestions about configuring issue event, notifications based on rule changes. Until one of those is implemented... The fix for this is not unassigning the issue, and instead replicate the team-identification logic: * In your rule triggered on Issue Assigned, uncheck the…

Hi @Tom Scoggin Checking for empty (or blank) fields within rules is challenging and depends upon both the field type...and for some fields whether or not they ever had a value (and were later cleared). For a list field such as {{issue.issuelinks}} please try using the size function with a condition on the math function…

Hi @Chetan Krishna -- Welcome to the Atlassian Community! First thing, you describe "removes all the stories...". If you mean deleting the stories, I recommend not doing that as there is no automatic backup or "undo" operation to correct issue deletion. Instead, I recommend disabling the delete issue permission for all…

Hi @gordon.varney Out of the box, Jira unfortunately has two fields depending upon the project type: * Company-managed projects use the "Story points" field, with a smart value of {{issue.Story points}} * Team-managed projects use the "Story point estimate" field, with a smart value of {{issue.Story point estimate}} If you…

Thanks for that information. What I was describing using the {{initiator}} smart value could be used as a comment, or could be used in rule conditions to control the actions, etc. If you encounter more challenges with the rule, please post an image of the complete rule, the audit log details, and explain what is not…

Please re-read the article and post I offered as the time tracking fields are not available with the Lookup Issues action with Jira Data Center's version of automation rules. The REST API must be used to access and sum the fields. Additionally, the syntax you are using is incorrect for the smart values. When you review the…

Thanks for the additional information! The log shows the Jira issues linked are in two different projects. What is the scope of the rule noted in the details at the top: single-project, multiple-project, or global? Scope is important for such rules as links have "direction" and so when an issue is linked from one project's…

Hi @Vivian Albrech -- Welcome to the Atlassian Community! The list view settings are for each individual user, and not sharable between other people with access to the project. Here is a suggestion to add the capability you describe, and you may vote for / watch it to see…

Hi @Emmanuel What have you tried thus far to solve this need? If you have a rule which is not working as expected, please post images of the rule, its actions / conditions, the audit log details, and describe what is not working as expected. Those will provide context for the community to offer suggestions. If you have not…

Hi @Naveen Chauhan -- Welcome to the Atlassian Community! Your rule could use the Smart Values Condition with a regular expression to test for the different values: https://support.atlassian.com/cloud-automation/docs/jira-automation-conditions/#--smart-values---condition Also: what value should be set in the "Action" field…

Hi @Matěj Hájek -- Welcome to the Atlassian Community! A rule branch will not work to sum the values of the issues found by the JQL: such branches execute in parallel and asynchronously, and so the variables (and any issue updates) will be repeated created / destroyed with each pass through the loop. Instead please try…

Hi @Hana Kučerová That is interesting news, and I am curious how that might work regarding the current model of Creator permissions (and licensing costs). Likely there are many challenges / differences to address... JPD seems built upon team-managed projects (TMP), essentially allowing someone with at least project admin…

Hi @Amanda Wong -- Welcome to the Atlassian Community! Why are you using the generic Issue Updated trigger? When using the trigger Field Value Changed specifically for the Labels field, the various {{fieldChange}} smart values may be used to detect what you…

Hi @Harrison Ponce To add multiple Label values based on smart value, please use a JSON edit rather than the Labels field from the dropdown list in the Edit Issue action: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Labels To do that, an iterator may be used over the values in the…

Are you using Jira Cloud or Jira Data Center? I would not expect that custom field to work with Data Center...unless they have released an update.

Please use the smart value to pass the ID. Assuming the rule trigger is Version Released, and with this endpoint, that would be this: jirahost.com/rest/api/2/version/{{version.id}} If that does not work, please post images of: * your complete rule, * the Send Web Request action (hiding any site details), and * of the audit…