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

I have two separate workspaces that appear connected

Beau Cook I'm New Here Aug 02, 2022

I have two workspaces and run multiple commands in both. Both have 5 boards with commands operating across all 5 boards. A command on Board 1 might trigger something on Board B.

Board A in Workspace 1 has run a command that created a card on Board B in Workspace 2. It should all run on Workspace 1. The workspaces should have no inter connectivity. The boards have the same names and I am an admin for both. 

What have I done?

1 answer

0 votes
Nathan Smith Atlassian Team Aug 08, 2022

Hey @Beau Cook 

Nathan here from Trello Support.

Just to confirm what's going on here, you've got Board A and Board B in workspace 1 and Board A and Board B in workspace 2. You've got a command that's triggered on board A in workspace 1 and is then supposed to create a card on Board B in the same workspace but is creating the card on Board B in workspace 2 instead?

Can you try changing the names of one of the boards, or adding a symbol to the end of one of the names, to see if you still get the same issue or not? Butler looks for boards based off their name so this may be what's causing this to happen.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events