Bill Sheboy Expert

For a PMO request like that, it is unclear if any implementation will / will not solve their actual need. Anyways... With built in functions, that could be done brute-force with the updatedBy() function for JQL: https://support.atlassian.com/jira-software-cloud/docs/jql-functions/#updatedBy-- Unfortunately that would…

Hi @Adam LaCoste What have you tried thus far to solve this need? If you have started an automation rule, 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.…

Hi @Michael Aglas Agreeing with other posters that this is a missing feature, given the criticality of automation rules. You can search the community for the various work-arounds tried for backup, version control, documentation, etc. of rules. The missing piece to support backups is the REST API functions, and you may vote…

Hi @Brendan Sheppard Those Atlassian-provided instructions will lead to an encoded value for the browser URL, and the rule will not take that. Instead please try this: * using an issue search, such as with View All Issues * use this JQL: assignee = type-in-the-user-name * when you enter that, the value will be replaced…

Hi @Rana Naveed -- Welcome to the Atlassian Community! 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…

I wish Atlassian would disable that button when rules are disabled :^)

Hi @Norton Lam Looking at your image, it appears there are also validators for that transition. Have you checked those? Kind regards, Bill

Hi @Cash Coyne Information about the details of smart values, and their structure in the issues, is mostly not in the automation documentation. Instead try using the how-to for finding smart values, as that will show the full structure and how to get to the smart values:…

The audit log shows the cause of the symptom: Your trigger is using JQL, and you have selected the option to not include issues which have not changed since the last run execution. And so there are no issues to process. I recommend considering what you want to do: leave the rule as-is, or remove that option from the…

Thank you, and that confirms the cause is using conditions and not if/else conditions AND that the most-recently-created issue from earlier is not visible later. Please consider how this rule may be either split up, or use if/else structures so the processing does not stop.

Then why does it not appear in the audit log for this rule?

Yup, that technique was needed earlier with automation rules...until those options were added for setting the Fix Version field. Of note for using this approach: I recommend running a basic query before using this to look for any "orphaned issues" which are assigned a released versions and not resolved. Those could be…

Brandi, your rule could be something like below. Please compare it to what you have to help identify the cause of the errors. * trigger: scheduled, but with no JQL * action: lookup issues with JQL to find issues meeting your criteria * advanced compare condition: check if there are issues to process, testing is…

Are the steps you note separate rules, or all one rule? If they are in one rule, it can help to show these in one image for context. That can be done using a screen capture tool or browser addon for scrolling, page capture. For your Fifth Step, it seems that should be a separate rule, as it has a different condition than…

I do not see the rule run shown. Did you select "Run rule" from the editor to force it to run now, rather than waiting for the schedule?

Please post an image of the audit log details showing where you ran the rule. And, if you run that JQL stand-alone, in View All Issues search, does it return anything?

I just tried this for Jira Cloud and it worked for me. For your dashboard gadget, have you checked if it is updating? For example, edit the dashboard and gadget and check the data is refreshing.

When you note "that did not work either", what did you observe happening? And please post your current, complete rule so we can compare your changes to what I suggested.

Would you please show your full, current rule and the audit log details showing the execution? Regarding that smart value expression: {{pullRequest.title.toLowerCase().indexOf("draft").gt(0)}} That is doing this... * for the PR smart value from the trigger * get the title * convert it to lower case * look for the position…

Please post an image of your complete rule (in one image), images of each action / condition / branch, and an image of the audit log details showing the rule execution. Those may provide context to explain what is happening. Again regarding my first post: I tried that and it provided a URL which may be used to trigger a…

In that post example, the Description "template" is added after the issue is created using an automation rule. And so the flow is probably: create an issue without a Description, wait a second or two, and then immediately edit the issue with the updated template. Team-managed projects allow setting a default value for a…

Hi @Mohanraj Thangamuthu The "trick" to make what you describe work is the feature to enable the epic panel also controls that slider at the bottom of the epic drop-down from the backlog. The feature to enable the epic panel is now located at: ... menu > Board settings > Columns and Status > Epics on your board > Enable…

The smart values you note are in a different location in the issue data. Please see my other response for the values, and... You may use this how-to article to confirm the smart values, their structure for issues, and if they are supported by automation rules:…

I suspect this is related to the lookup issues being recently added for Jira Data Center: When lookup issues was first added for Jira Cloud, it only supported a subset of the issue fields. Later, all of the other fields were added. The same may be true for Data Center's automation action. That can immediately be confirmed…

Regarding the audit log showing no errors: in many cases when a smart value expression evaluates to null, there is no error. I am guessing in that Issue Create action, you are trying to add a link to the same issue which is being created. If so, that is not possible because it has not yet been created and so the…

Hi @Steve Tedeschi Without seeing your automation rule, I suspect you are correct and trying to reference the smart value {{createdIssue}} before any issues have been created. The smart value to use depends upon your rule structure, and if you have only created one issue thus far in the rule, the value would be…

That explanation seems to indicate you already have the Dev Estimate field. Are you trying to find some other value?

According to the audit log you showed, the lookup issues is getting issues back. If you use the JQL for the lookup issues, and the example issue when the rule triggered, please try to run that JQL stand-alone with an issue search. Then check if any of those issues have an original estimate. I suspect the problem may be the…

Thanks, @Mark Segall I like that approach better than mine finding the issues first. Wouldn't the edit just use "next unreleased version" rather than a smart value? I believe the {{version}} smart value would only be available with a version-related trigger. Kind regards, Bill

Hi @Adam Betz 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.…