We recently talked to some of our busiest customers, and we found that many of them had never configured their spaces. Their team members were landing on empty pages and clicking around, instead of landing right where they wanted to be.
It's amazing what you can do with Assembla configurations. However, we know you are busy and its not your job to figure out every detail. If you want, WE will do the configuration for you.
Go to this form, and sign up. Our support experts will swoop in to configure your space.
Here is the TOP SECRET checklist that we use to get spaces tuned up.
- Landing tab on each space - select the right place to start.
- Remove or add tool tabs
- Add custom tabs to show a unified view of all tools and systems used in the project
- Add custom banners to build branding and team spirit
- Ticket landing tab (list, cardwall, planner)
- Set ticket status columns and tags to match your workflow
- Ticket list filters. Default list in each view.
- Current milestone
- Default cardwall settings
- Email alert defaults
- Permissions - Owners and watchers. Tab visibility restrictions. IP restrictions.
- SVN and Git repository names
- Git protected branches - enforce a code review workflow
- Git and SVN server-side hooks
- Do you want any Webhooks to go to a chat system?
- Do you want to connect to Bigplans.io for a real-time chat and planning system?
- Build hooks - FTP, Webhook, SSH tools to automatically build and post changes
- Configure other tasks in the SSH tool
Assembla is designed to (hopefully) start simple, and then accept more configurations as your process gets more sophisticated. If you do it long enough, you can end up with a lot of special configurations. For an example, here is a picture of the Assembla space where we build the Assembla.com application.
At the top you can see a custom banner showing some key performance indicators - trials, subscriptions, and users. I have opened the "More" menu list so that you can see some of the custom tabs that we added to give our team access to their development and monitoring tools. You can see Jenkins, which does our builds and is posting status to tickets and stream, and NewRelic, a terrific tool for monitoring our production servers. The list is longer than what you see here, including all of the developer forks of the master git repository. We have also configured child spaces where each team can see their own cardwall. Each tool is configured so that we quickly get the information that we want. Using this system we can move dozens of changes per day from the ticket cardwall, to code review, to build and test, to release.
Go here to request help from a configuration expert: https://www.assembla.com/content/help-request.php
