Very positive on Assembla. We have used Assembla for 5+ years. The new enhancements are great. Really appreciate how Assembla listens to their clients feedback and takes action(s) on their recommendations.

We like Assembla for it's collaboration amongst our team members spread all over the world. It provides real time metrics for our developers. We have had several other firms attempt to lure us away from Assembla.

The development team likes the ability to set up quick Sprints, allocate team members to specific tasks, and have all documents contained in one centralized system.

Overall our experience with Assembla has been positive and it is indispensable to our workflow. While it would be possible to replace it with another product, it would not be without the pain of changing how we work to accommodate the tool.

Ticketing is critical to our process for managing software project. Assembla has a great list view that allow us to have custom fields for each project. This allows us to create views into projects that sort and filter tickets by criteria meaningful to our stakeholders. Additionally tickets have good support for relationships and some hierarchy. This is in contrast to GitHub or GitLab issues, which offer limited support for sorting and filtering and require a tedious management of tags for everything not provided by default (which isn't much) A project with any serious complexity should consider using Assembla for ticket management.

The wiki syntax for tickets is non-standard and clunky. Developers use Markdown for every other tool that requires them to write prose. The lack of support for Markdown seems like a fairly large oversight. This becomes especially egregious when developers refuse to learn yet another syntax and just paste markdown into tickets despite the lack of support. Who can blame them. A more minor point is that the various features lack a coherent design language and level of quality. The UI/UX can be fairly different between modules, almost like they were written by different teams or at different eras of web development history. Also the level of quality varies wildly. You will find that some modules are rife with bugs and interface quirks while others operate bug free using modern interface idioms. Overall this makes the product seem lower quality than something more polished like GitHub, despite having a solid core of features needed for real project management.

Way too many bugs and missing features. It is like a counterfeit of successful products - it looks like there's everything you need, but you have to bend your workflow to make it work. If you are used to quality, you won't find it here. The customer support is quick to respond via chat, but reported issues take weeks to fix and if it is something critical for you, you are just out of luck! It looks like this product does not innovate and if yes, it's in the most basic/cosmetic way.

Well it does the job, somehow. The integration of all tools under one roof is a good idea.

Merge requests are useless, since you don't have proper code highlighting. Also, cross-referencing tickets from code is not working well. The ticket management is very poor. The cardwall is difficult to filter and navigate through. User management is sometimes buggy (you invite user and it sends invitation to wrong address, etc.). External tool integration is limited and does not work very well. Exporting data from Assembla is mostly impossible, so you are locked in until you are really fed up with it :).

Kanban board is one of the most advanced features from the market, it's quite clear and nicely designed. Sometimes drag n drop were rigged but lately i think it got fixed. Github integration should be in price not in higher tier as it's quite used. Wiki pages could be extendend.

I don't like that there is no emergency line as it should be in Kanban theory. I can't customise priorities Whole board view is horizontal driven i can't do a tree structure and see it from top down. Which is difficult if we need to monitor and organize more then 1 milestone or topics on one board. I can't have a view with 3-4 boards on its , we have 3 or 4 boards per project in a team, and as a team we should have a view which merges all 3-4 boards and allows to plan and organize tasks with the 4 different projects. Excel / google sheets export could be nice - sometimes for overall planning the cards are too heavy and there is too much colors, excel is quite tabular, and with my client we are often using excel beacuse its better for fast and simple view - this could be major enhancemnt to prepare simple view, which would give overall ticket status in form of table with columns

It's a solution that has it all but I would welcome an overhaul of UI and backend optimization for speed. It feels like there's a lot of ancient code in there.

It's a one-hub solution. Everything I need is within reach. Task management and planning in the card-wall of tickets are indispensable.

Slow: Opening a page or a ticket can sometimes take seconds of looking at a blank page. When used in meeting this is really annoying. Clutter: It lacks options to clean-up. Since I work with it for 10 years I have 150 projects in my view and no way to hide old projects. New projects appear at the bottom of that list, so scrolling galore! Yes, I could go to the project-owner and ask him to archive, but you know how that goes in large companies and I don't have rights to archive so I'm stuck with over 10 years of old projects. GIT: It could use some more optimizations, specially Merge-request handling / canceling, retaining comments etc.

It has deep integration of source control system with their project management tool so you can track commits using the same view/page that you use for tracking ticket comments.

Assembla was acquired by some other company and the first thing they did is to raise the price. In short time, from one of the cheapest products, they become one of the most expensive products. And that change was very fast and ugly; I remember that we needed to add just one additional member to the team and they said to us that we are on legacy plan, and that we need to move to their standard plan, and pay something like 5-10X more for the same service. Instead of paying more, we moved to Jira :-)

Even with its flaws it's a good option over git and svn, it has a nice webapp to help you keep track of the project and source files.

It seems very secure, and I love the fact that you can see which files others have checked out, that's huge thing when working with a big team.

It's super slow when you need to revert files or when you added 2k files to a submit queue and you decide not to move forward with the submit. That will take a lot of time and it's really annoying. One last thing is that is a pain in the ass for new users especially for artists to setup perforce, perforce should have automated tools to setup your workspace, like a wizard to ask you about the basics. Having to open the command to type manual commands is not intuitive.

I can get information about my task, my priority, sprint, estimated, change, acceptance criteria

It provides what needed functionalities for collaboration. Like mentioning, notification, workflow, repositories, recent activities. Especially the recent activities, that was the first to go when I opened Assembla. I could find who mentioned me, what card I was following, etc.

This tool is great for a big team that needs everything in one package. Although it comes with reasonable price, it is still expensive, not my choice for small / starter team.

This is a good tool for smaller teams, but I would like if they didn't raise their prices so much.

I like how you get all your tasks and your code repo in one place. Also, Assemble makes it easy to communicate with your team members with in-built mentions and there ability to reference other tasks or code commits. I also really like preview option before you post your comment.

I don't like that they've changed their pricing model. We needed to add 1 additional team member, and we needed to switch to much more expensive model.

As an engineer I am satisfied with Assembla reporting capabilities and task tracing. It is helpful to revert/find certain activities for reference.

For people who work with computer on a daily basis (not programmers) it is good tool to report work and tasks progress. It has nice integration with Slack communicator. There are also other tricks and integrations that IT people can benefit from.

People who work less on a office-based routine it is harder to report and follow tasks in Assembla (non programmers). While exporting pdfs and attached images are too big files, output file is not clear. It is tricky or impossible to create subspace/subtickets for part-time subcontractors without giving them access to all other tickets in the space/company. You need to spend some time on reporting directly in Assembla (15min minimum) - cos of having things properly reported.

The team at Yard Freaks have had a great experience with using Assembla as a project management tool. We are able to view and keep track of our current and past projects. Share our process and keep in communication with each other. Plus having the wiki section and being able to download them as a PDF is a nice touch.

The team can easily view their trackable tickets. The card wall is a nice drag and drops feature that makes it quick and easy to stay organized.

Having a desktop notification pop-up when you receive a new ticket/updated ticket would be an awesome feature to have.

It is important for us to track cardwall on each milestone that we aim. In that regard, viewing/drag&drop on the cardwall is the most used part in this product.

I miss the ticket templates in this product as I prefer to have the option to create a ticket template and don't have to write the same stuff over and over again. Our colleague sent a request I assume 2 years ago but still that feature is not there to use.

The website is easy to use.

I have lack of basic features that I have in all your competitives. Im working with git source code. I don't have: - Delete branch from manually from website. - Disable merge button if no reviewer accept the code. - Set number of minimum reviewers

I love assembla. It helps me keeps track of what tasks are more important. Lets me know what needs to be done and when it needs to be done at a moments glance.

I like that I can see everything that is going on from the stream view without having to spend too much time.

The only cons about assembla is when you have a ticket open and if someone updates it, it constantly flashes, can get distracting.

Code & Document management, version control. Ease of access . Maintenance of code

We've used Assembla for managing our code and document repository. The advantage of it being integrated with SVN and GIT makes it really easy to manage our repo. The ability of an a repository to integrate with other tools is an added advantage. Secure and cost effective.

Would like to see a tool primarily to support repository operations on IOS, that's one piece which is required.

The Best ticketing system that I have ever used. Sleek design, easy to understand. Assignments and priority are easy to adjust. Drag and drop cardwall

Awesome tool that helps me communicate with developers.

It works well and originally the price was great

The company raised the price on my account multiple times without ever communicating with me. At the end they were charging me 7 times the price of github. I can get the same features from tithing for over a year for the price of two months at Assembla. :(

I am not a technical person, but I am easily able to log issues and track them through to completion with our technical team.

I initially struggled with how to add custom fields and add to the dropdown values, but I was able to figure that out after spending some time looking.