Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.

2 answers

0 votes
Katrin Anger Community Leader 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.

Katrin Anger Community Leader 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 Travis Austin likes 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!

0 votes
Iain Dooley Community Leader 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

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Trello

📹 Favorite Trello templates

Hello Community!  My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. In this video, I'll share my favorite Trello templates. Templates mentioned in ...

1,296 views 12 31
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you