Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Make a butler button visible on selected lists?

Hi there,
Does anyone know if it's possible to only show a butler button in some lists on a board? Based on which list a card is located different buttons are relevant for us. Without this feature, we'll get way too many irrelevant buttons.

3 answers

Hi dear support team, 

I support this request for change as well.
I see ticketing workflows as finite state automata. The combination of list+label would be states, and the possible movements between lists and the changes in labeling are the transitions.

There are initial states (eg open/to do/ backlog) and final states (eg fix deployed in production). 
If it makes sense to have some universal transitions, for example some "Pause" or "Need for Clarification" buttons. having all transitions available at every step is allowing too many unacceptable possible paths for a card.
When only a few possible transitions are allowed, it is the opposite of error proof to display 30 irrelevant buttons .

0 votes
Iain Dooley
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Mar 26, 2019

@Brian Petersen If I had this problem I would do the following:

1) use other rules as triggers. For example you might be able to trigger on card move to cover some of the functionality  or use due dates 

2) use labels instead of buttons. Labels don't show up all the time and you can filter them so choosing what label to add in order to trigger an action might be a friendlier interface. You could use labels to trigger some actions and buttons for others

3) combining those 2 ideas you might find that you can obviate the need for some buttons by taking different actions when a card is moved or due based on what labels are present on the card

0 votes
Katrin Anger
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 26, 2019

@Brian Petersen 

Hi Brian, 

Butler only offers buttons for cards or for boards, no lists.

As a workaround, you could set up board buttons that apply only to these lists and run actions on these lists, like "IN PROGRESS"-button, "DONE"-button, etc. - Could this be an option?

You can also contact me to discuss your workflow. I am certain I could give you some hints how to make things work for you.

@Katrin Anger Thanks for getting back to me. We are going to create a lot of different buttons, so I don't think your work around would be an option.
Do you know if the feature is in the pipeline? I can't be the only one who finds this very useful.

Like # people like this
Katrin Anger
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 26, 2019

@Brian Petersen 

I never heard anyone requesting list buttons before, so I can't really say this.

You can certainly set up a feature request for a list button with Butler and let them know why you need it this way and why no workaround applies to how you work.

@Katrin Anger 

Sorry about reviving a dead post but my team would also find this function extremely useful! We have some team members on the board that aren't super tech-savvy so only having the buttons that are relevant to the list they are on would be great at giving less clutter and less things to think about. 

The workarounds do technically work but it is not as agile as it could be. For example, cards in "TO DO" should only have the button "IN PROGRESS" to move it. "IN PROGRESS" should only have the button "READY FOR PROOF" or "PRE-PROOF". It should not have the buttons for "APPROVED" and "DONE" as no one has checked it yet. "READY FOR PROOF" cards should only have "ALTERATIONS REQUIRED" or "APPROVED" not "DONE" which for us is an extra step. Each one of our buttons sends automatic emails and assigns certain people to them. When they are clicked by mistake it creates a lot of incorrect backlog and communication issues. By removing the human error likeliness it would help dramatically. We have created our own PDF flowcharts to try and counteract things being put in incorrect places but I believe having buttons assigned to certain lists would really help. 

Like # people like this

I'm with @alesha.honnor here! This would be super beneficial, where Card buttons would only show on cards that are in a certain list, or even only show a button on the card if it has a specified Label. I see so many applications for this and would be super competitive compared to other Kanban chart programs. Taking the workaround with the label making, then having to add a label that corresponds to a list, remove the previous label from the previous list, it's just very cumbersome for something that should be already integrated (from how I see it at least!) 


Appreciate the work all the devs are doing! Great job on the overhaul update recently, the future's looking bright!

Like t_jagusz likes this

I'd like to ask for this feature as well.

The use case is very simple in my case:

tasks go to "MANUAL TESTING" list, then testes do manual testing, when they approve the work they must do a couple of things in trello. I'd like to do all of them using a single button, but I want to show that button only on tasks that are in a specific list.

I'd like to support this feature as well! There should be an option to select what lists a button should be available on :)

I would also like this feature to be added.

Having buttons that can only show up when a card is in a specific list would be great.

I'd also like to request this feature. Every few months I have a new use case for it and search for whether it's possible or if anyone's figured out a good workaround yet.

Like Vivian Yamamoto likes this

One more who would like this feature

I'll throw in my support for this as well.  I could see a somewhat complicated but useful implementation:  allow Rules to create or remove buttons for cards with "In list" (and other) filters.

Another supporter - this feature would be great for our team.

We also need this exact feature to support our workflow. Without it, buttons are much less of an attractive feature than doing everything ourselves, as missing something generates less errors than clicking the wrong button and messing up the process of a card.

Needing this feature is how I ended up here. I have different lists for Site Survery, Need to Quote, Quote Accepted, Deposit Received, etc...

For example, I need a button that moves a card from Quote Accepted to Deposit Received, but I wouldn't want that button showing up in my Site Survey list.

I'd like technicians to be able to click on Completed button on cards in a list called Service Calls, but I don't want that button to show up on cards in the Need to Return list.

Like Philip Miller likes this

Do we have a feature request for this, so I can leave my "voice up" there?

I'll throw another request for this feature onto the pile. Would help to smooth out specific automated actions without cluttering unrelated cards.

+1 on this.


Use cases:

- Only cards in the "Support request triage" column needs a "Move to department Y triage instead" button

- Only cards that are not in the Done column need a "Move to done" button (this suggests a "not in column(s)" condition could be useful)

I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Jan 27, 2023


I really think it is obvious to have such feature.


Nobody wants to have a button that moves a card from BACKLOG to FINISHED.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events