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

Trello for Construction/Maintenance Company

As above? We have up to 50 jobs on at any one time with various levels of work for each one.

Are we better off creating a board per job, or one board called operations and then 50 cards for the jobs. Each job will then have it's own lists or 'sub cards generated'

We will be using Planyway to assign the jobs to our staff

Thanks in advance


@Gareth Ricketts 

I don’t think there is a single right answer for you.

For example, I have client with a fleet of 20 vehicles that go through services to turnover the vehicles so that they can be ready for rental. They do repairs and maintenance of none rental vehicles. In that situation, they assign task and subtask using a customisable work order boards to their specialist in their own personal boards. Each task and subtask sits on a list and all work and reporting happens on the list rather that across a board. 

Yet another client has 2400 work orders per year and everything happens on one board. None-maintence work progression is triggered from Work iS triggered from an external management system.

Another client conducts business on separate boards eg Quotation and customer approvals, job tracking, completion and delivery, rework, purchase orders...etc

Flavien Gache Community Leader Apr 19, 2021

In my opinion, it could be useful to use one per job if jobs are independants from one another and if each job needs to work on its board. It could allow you to separate each job and detail everything without giving irrelevant information to other jobs.

If boards are going to be used by the same person, or same set of persons, you could be better off with only one board. It would mean less clicks and less back and forth for the person that will schedule plannings.

However, I think going with Planyway is the right move : its features are really interesting for those who don't want to deal with the complexity of Jira. Butler would be a great addition to automate repeating tasks.


Log in or Sign up to comment
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 ...

2,125 views 17 49
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