Bill Sheboy Expert

Sorry, I am out of ideas to suggest for this one. You could wait to see if another community member has suggestions or work with your Site Admin to submit a ticket to Atlassian Support to ask them: https://support.atlassian.com/contact/#/

Per your comment / question: Is it possible there is strange async behavior that is causing the automation to not get the latest value of a non-list issue.item? I would assume that issue.item should be the latest value of that item following the change that triggered the automation? Yes, there is both the known defect with…

Hi @JEROME DREW -- Welcome to the Atlassian Community! First thing, I recommend not trying to change the type of a work item (formerly called "issue") with an automation rule. Jira has a specific UX feature to "Move" to a new type, and that supports interaction with the person to ask / answer any necessary questions. There…

Hi @Moshood -- Welcome to the Atlassian Community! There are at least two causes of that symptom: 1) The Issue Created trigger can fire so quickly that some data may not be stable / available when the rule starts. The fix for this is to always add the Re-fetch Issue action immediately after that trigger. This will slow the…

Hi @Juan Jimenez -- Welcome to the Atlassian Community! This is a very old thread, and so please create a new question using the "Ask a question" button at the top of the page. This will ensure the maximum number of people see your question to offer suggestions. Thanks! Kind regards, Bill

Hi @Sakshi Kale Jira Cloud does not use the plural {{issues}} smart value. That is used for bulk-handling issues for Jira Server and Data Center only. Jira Cloud uses the Lookup Issues action for such needs. And, neither of those techniques requires a separate rule per Assignee for the scenario the original-poster asked…

Hi @nagendra Another approach is after the issue is created, add a branch to most recently created issue and assign from within the branch. Repeat that for each issue created. That approach only works when the rule is not already inside of a branch and the rule is short enough to allow adding the extra steps. A better…

Again, I am guessing here... If you expand the branch area in the audit log to look at the issue keys, is the one you show with that standalone AQL query the same for the specific Affected User field: VEND-14390? Or did it not match for the specific issue the rule branched over?

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!

For some fields, a smart value expression may be entered directly into the field (rather than using a dropdown of values. This is not always obvious from the UX, and the steps are: * type the smart value expression into the field * when the expression appears below the field, select it for use * test your rule Other fields…

Hi @Eric Dyer -- Welcome to the Atlassian Community! The Sprint field is a list of values, including the current and all prior values. And so your JSON expression is trying to use zero-to-many dates in the field update. And, the changelog smart values often do not work correctly for the Sprint field updates, and so those…

Hi @Stefan Musch -- Welcome to the Atlassian Community! First thing, I would not recommend using any bot to answer Jira questions (perhaps even the Atlassian-supplied ones). Each Jira version, site, project, issue type, etc. has its own configuration for your site and such tools do not have access to that information in…

Hi @Jodie Parsons Your question is about a marketplace addon / app, and so I recommend checking the vendor's documentation or contacting their support team from their marketplace page. This appears to be the page for that app:…

Hi @Guy First thing, I have never used that internal, custom field before. With that out of the way... Based on what you show, and a quick experiment, I hypothesize you could use spreadsheet formulas (or macro code) to: * split the values on the colon : delimiters * use a lookup table to map the Status Name to their Status…

Hi @Lisa Thanks for this information, and I have a few questions about this feature: * For which project and board types will this work: company-managed, team-managed, JPD, etc. and Scrum vs. Kanban? I see the feature for company-managed projects but not for others. * Your screen image apparently shows three chart types…

Hi @Loretta Brunette Thanks for this great info! Quick question: will pubic forms be available for all license levels of Jira, including Free license? Kind regards, Bill

If there is required information for the transition, that must be supplied with the rule action attempting to perform the transition.

Hi @Daniel Bermudez Starting with your JQL filter idea, have you tried adding the "Remaining Estimate" or "Σ Remaining Estimate" fields to the result columns? https://support.atlassian.com/jira-software-cloud/docs/jql-fields/#Remaining-estimate Kind regards, Bill

Hi @Rees, Ian For an automation-based approach, rules cannot nest-branches at this time. And so possible approaches would be: * Branch over the epics, and add 30 clone issue actions (one per project), as you described * Branch over the epics, and call the REST API bulk create issue endpoint using the Send Web Request…

Hi @Andy Thelen -- Welcome to the Atlassian Community! Disclaimer: I am not currently using Assets or AQL, and so cannot test my suggestions. With that out of the way... I believe there should be parentheses surrounding the values when using the IN operator: {{#debug}}objectType = "Vendors" AND "Current Status" IN…

Hi @Charles Liss For automation-related questions, I find knowing the full context for a rule helps to know what is / is not relevant to the symptoms being observed. Team-managed projects (TMP) each have their own configurations for issue types, etc. With automation rules, people may assume the behaviors they were…

Thanks for that information, and... For your PMS project, is there a "OK" status? If so, for the workflow for the issue type of PMS-6810, is there a transition from its current status to the status "OK"? If so, are there and conditions / validations on that transition which would prevent it from happening? For example,…

Okay; then please try what I suggested with the partial matches and the conditions.

That looks correct. Does your testing confirm all the cases you want to handle?

I suspect your rule would need to test only on the part of the Summary which does not change (e.g., "Test Issue 1") to find them first and then use rule conditions to check if the remainder in a format you expect. Once identified, they may be linked to a specific issue, such as the trigger. Backing up a bit: what problem…

Thank you for that information, and...I just recreated the symptom you are seeing with a test rule for this scenario: GIVEN a Jira project AND a global / company-managed custom labels field is added to the project scope AND there is an automation rule with a Field Value Changed trigger for that custom field WHEN a label…

Thanks for trying that, and it appears you are using Jira Server or Data Center, thus that specific field change smart value will not work. As an alternative, you may use the {{changelog}} smart values with two conditions, one after the other: * advanced compare condition:* first…

Hi @Teal Nissley Do you mean Atlas / Home goals? If so, I do not believe those are supported by automation rules yet as there are no public REST API endpoints to access them. Here are the suggestions to add that capability: * https://jira.atlassian.com/browse/JRACLOUD-93486 * https://jira.atlassian.com/browse/ATLAS-172…

Hi @philip_song -- Welcome to the Atlassian Community! I am not completely following all of the steps in your scenario, and... You could combine your tests using smart value, conditional logic with a Smart Values Condition to test them…

Hi @Ofir Oxenberg -- Welcome to the Atlassian Community! After the changes to the Slack interface Jira automation uses, it is no longer possible to send a direct message to a Slack user. (There is a workaround, but it requires creating a separate channel for each user...although I have not tried that.) What is possible is…