Roots Discourse

Off Topic: Github Projects? Trello? What do you use?

Hey, y’all!
My team and I are trying to find a better way to capture action items on client projects. I’m testing out both Trello and Github Projects and looking for any feedback from anyone who’s used one or both of these. You all do agency work, so I thought you might have useful input.

Github Projects seems like a great solution. Cards can be created from Issues, referenced throughout the Git process, and it’s already a tool I use every day. The downsides are 1) that the designers and projects managers don’t use Github every day, and 2) that items like “Add About page” isn’t really a code-related task. It’s definitely something we need to deliver, but it doesn’t fit with anything else we’re tracking on Github.

Trello is almost exactly the opposite: It handles the arbitrary items like “Add About page” better from a conceptual point of view, but it doesn’t integrate with Github Issues, which seems like a neat thing.

So what have you used? Does one of these fit your work better? Why?

Thanks and I hope this off-topic post isn’t too much of a pain!

1 Like

I haven’t used it yet, but Bitbucket has Trello integration: We’ve been using Bitbucket at work for years, I just haven’t tried out the Trello integration.

At my old gig we were using Asana for PM stuff. I used this service called Unito to connect Asana to Github issues.

This was cool because PM’s and everyone else was able to use Asana as usual, but developers were able to work in GitHub and keep issues with the codebase.

Features I liked were that comments were synced, tags synced (with some setup), and ticket numbers would sync from GitHub back to Asana.

Also, because comments synced back and forth we didn’t have to add outside developers to our Asana as I could give them access to the repo they were working on and they could communicate with PM’s directly through the issue tracker.

I used bugherd in the past and I thought it was pretty good but the problem was the client in my case( they started spamming us with hundreds of issues so we had to close down the whole thing cause it just became unbearable!). The platform itself is good though, hope it helps :slight_smile:

We use Github and / or Bitbucket with Trello and sometimes Jira, all connected via slack.

In this approach, each project gets an internal slack channel. In a normal project with reasonably technical clients, we make a Trello board with a load of lists and give the client access. On the board we create an ‘incoming’ list. This is where we and the client drop in new issues and questions.

We also create a list for each person working on the project like “For Fred”, “For Jill” and “For Tom”.

The team then moves the cards to the relevant list, depending on who is best suited to fix the issue. It’s fine if the client feels like dropping cards to a particular person directly if they want.

We also have a list called “Doing” where cards are placed when the work is in progress, another list “For Testing” and finally another list called “Done”. This works well because the client can see what’s happening and can even chip in and move cards if needs be.

If the issue is trivial, then the team member will just do it, and pass the card to either “For Testing” or “Done.”

If the issue is indeed an issue in the software development sense of the word, the team member creates an issue in either Github or Bitbucket.

This all works like a dream because every action across all of these platforms causes a notification to drop into the relevant slack channel. The Trello slack integration is particularly flexible and allows you to configure exactly what triggers a message to the channel.

It also means that incoming issues get filtered before actual issues get created on the code repository. Slack also provides a great place for private internal discussions around the commits, card moves, issues, etc.

We’ve been running like this for years, and thanks to the mobile version of slack, I can be anywhere on the planet that has an internet connection and I can see exactly what is happening across all of our projects.

Jira only comes in to play when you have less technical clients who just want to send an email to support. You have to pay for the Jira slack integration but it works a treat too.
When using Jira as the client facing help desk, we still run a Trello board internally. It’s dead simple to create a card and drop it into incoming. (Edit: Atlassian bought Trello so this is going to get easier!)

Also, We find that using Trello is a great way to get a beta site polished up before launch. Testers will go through the site with a fine toothed comb and drop cards into “Incoming”. These then get shared out by the team in the normal way. I thinks it’s better than using the issues system on the code repo because a lot of these things are not really issues, more like small tweaks and changes. Trello also makes it simpler to get less technical people working productively on the team. The slack integration handles keeping everyone up to date with exactly what’s happening at all times.

There are a ton of other useful tools that integrate with slack. The good news is that to recreate the system as described above, you can use the free versions of everything except Jira.

Hope that makes sense!

1 Like

Projects looks cool but I’d stick with Trello because it’s more broad. Can add non-coding related tasks to it.

The dev team I’m currently working with uses Asana. I’ve always wanted to like it, but for some reason I’ve never fully adopted it. I just like Trello’s simplicity.

I think my ideal setup would be Trello and Github, integrated with Timely and Slack.

If you’re into time tracking, Timely is where it’s at. They have many integrations including Trello and Github. It will automatically track what you spent your time on during the day and correspond those to particular Trello tasks or Github commits. Just waiting for a Timely/Slack integration to come along– then Slack can be the hub for everything.