Lighthouse Best Practices

Question

I recently started using Lighthouse to manage a couple of development projects and would like to know what some of the seasoned users consider to be their best practices for maximizing this applications usefulness. Perhaps there are certain tags that make it simpler to track aspects of projects, or more advanced ways to setup milestones than the obvious.

Answer 1

Here are some of the things we do for our projects:

1. Add tags to everything. Lighthouse has a useful tag suggester. Once a ticket has tags you can quickly see all things that have been done and have yet to be done related to an overall goal.

2. Separate milestones by intended completion date. If you have an agile development process, don't be afraid to have concurrent milestones.

3. Create a 'storage' milestone with no completion date. Open it up to many people in your organization if you'd like. As it comes time to determine what needs to be done next, have a product meeting and use the storage milestone as a guide. You can pull tickets directly out of it, edit them appropriately, and place them into milestones with completion dates.

4. Don't set tickets to have no milestone. It's too easy to lose them since they don't show up easily in searches.

I'm looking forward to seeing other suggestions.