Just remove the button!  Or at the very least; make it configurable, default OFF!

Why clutter the interface with unused buttons?

Every issue has two "Actions" buttons:

One of which has all the Actions I need and is "hidden" away behind a 3-dot symbol, the other one is very visible next to the Issue state and it is absolutely useless if you don't have any automations set up.

Hiding this second Actions button would reduce confusion, as I keep catching myself and others press this button and disappointingly realize that it doesn't contain the Action we are looking for. It would be even better if the actions were consolidated into the same menu, and the Automation actions would just be a sub category.

I believe that having 2 buttons labeled "Actions" with different purposes is a bad design choice, and something must be changed to create a more understandable and intuitive UI. 

this would be awesome! sometimes actions should only show during a specific state. so this would be great to be able to make things show up as conditions change

It would be very helpfull to have the availability to hide this button when empty.

I would like to be able to hide this button. We don't want our users to create automations that might conflict with how our system is intended to run.

We are migrating from server to cloud, and the layout is already confusing enough for our users without having an additional button that I have to train them all to not use!

We really need a way to hide this from users.

Spending much time and effort on building out very detailed automation rules then users having the ability to add rules that could effect any rules already in place is frustrating.

It would be good if we could disable it globally or even per project.

89403358cf11, checking in on this one. The ability to filter a manual trigger to just certain issue types was added (woohoo!)... wondering if there is work being done for the other bullet points that I mentioned in my October comment?

Most specifically, it would be great to go back to having the Actions dropdown only show if there are multiple actions in it that can be executed and if there is only a single action, show the name of that action (this is how it functioned previously before automation rules were aggregated into the actions dropdown... it was really helpful that way and still would remain helpful if manual triggers behaved like looping workflow transitions did in that previous state). Or if we just had more configuration choices for what shows in transitions vs actions and overall if actions should even show.

To reiterate what that state was previously and what would be more helpful than the current state:

• No Actions available on a given issue for a given user: nothing showed next to the workflow transition dropdown (perfect)
• Single Action available: name of the action (looping workflow transition at the time) shows on the button and it took a single click to execute
• Multiple Actions available: "Actions" dropdown showed and all were listed within it (similar to current functionality, but no need to have create/manage/audit log links there)

please add this!!!

As others have mentioned, it definitely seems like there are multiple asks (all valid and helpful) between this and https://jira.atlassian.com/browse/AUTO-114 (and others that were closed in favor of these 2).

Maybe the below points summarize what would be very helpful for everyone?

• Allow a per project/issue configuration that can completely disable the Actions dropdown all together.  In these cases, any applicable looping transitions can be aggregated back into the Transitions dropdown and manual triggers could live in the Automations glance or be blocked (might be good to let us choose between 4 options for the Actions button/dropdown: Off, Just Automation, Just Loops, Both)
• When the Actions dropdown is toggled on for a particular project/issue type, still allow more configuring/permissioning on the manual triggers
  • Allow it to be limited to only certain issue types so it will not show for irrelevant issues in the project (labeling helps with this, but still shouldn't bloat your issue view everywhere)
  • Allow the manual rules to be limited to only certain project roles along with its current limiting of groups
• If there is a single Action available, show its label on the button for a single click instead of a dropdown (previously functioned this way with looping transitions)
• Remove link to manage automation from the bottom of that dropdown when it is toggled on (Project Admins that need to know, already know where to configure this)... we try not to have many Project Admins in our use-cases, but I see why this is valid
• When a user does not have the ability to execute a manual trigger, nor looping transition, do not show the Actions dropdown at all (previously functioned this way with looping transitions)... essentially, do not show the Actions dropdown when there are no actions to be taken

Delivering any one of the above will be better than the current state, but I was suggesting that this last point would be most helpful to start.  Making that happen will enable us to turn off manual triggers and/or limit them to certain very limited groups and limit the looping transitions to certain groups/roles and the button is then gone on a per workflow level and helps with the rest of the needs (unfortunately, it wouldn't help limit the scope of needed automation per issue, but maybe we can use groups creatively to make that happen for the time being).

Suggestion: Reopen and implement AUTO-671 "Allow hiding the automation Actions button". Period.

Keep the request simple; allow hiding the Actions button for all users; regardless of role, permissions, issue type, status, workflow, etc.

Kept simple, there is a chance the specific request, AUTO-671, will be implemented.