Confluence vs Azure DevOps Server (formerly TMS)

• Organizing content so that people can find what they are looking for.
• Putting restrictions on certain pages so that it can be seen/edited by appropriate employees
• Letting people collaborate on documents simultaneously
• notifying when a page has been updated
• combining content with tasks so that things get done

Read full review

• The consolidation of issues is extremely useful for us. Having one place where all bugs are entered has helped our business process immensely.
• Being able to query data regarding user stories, bugs and code is extremely helpful. As well, using the visual tools built into the system can help with messaging regarding the status of a project.
• Being able to monitor code deployments is extremely helpful. Since we are managing multiple environments, this tool makes it easy to see what is happening where.

Read full review

• Atlassian is not intuitive for the user. Several of our staff who have not received training on the platform find that it is not user-friendly.
• Posting on Atlassian can also take more time than expected due to the plethora of options available.
• Atlassian Confluence does not always look the same in different internet browsers. In talking with a co-worker, he told me it works best on Chrome. My computer has IE and Chrome, so I have to be sure I am using Chrome when I log into Confluence.

Read full review

• The older versions of TFS are more lacking in the web version-- if you aren't updated to 2015 or above I believe, a lot of the web features are not available (like bulk update). You really have to keep up to date with TFS for the best features, and it's no simple task to migrate your entire instance of TFS from an older version to a newer version.
• VSTS is supposed to be a virtual version of TFS that we've been looking into, but it severely limits customization options for ticket templates and workflows. It would be nice for VSTS to eventually carry that customization over so we could feel more comfortable switching to "the cloud" so to speak.
• Queries are a very powerful tool, but normal business users struggle to understand how they can best utilize this tool to analyze tickets. Because of the permissions structure in all companies I have been a part of, I've never been able to save my custom queries to a public folder in TFS for business/project users. Instead, I have to take time to train these users and give them guidance on how to best create queries for their needs. This is admittedly a business process issue, but it could potentially also be resolved with some good training/guidance around queries provided by TFS themselves.

Read full review

• At a previous company, Confluence made creation and resolution of support tickets across a large and distributed organization very manageable. This was a major positive impact in that it allowed efficient management of many different customer deployments in a responsive manner.
• At my current company, Confluence would have had a negative impact do to the slowness of the product, adding a significant overhead for our small team to get things done.

Read full review

• Time to completion for projects has significantly gone down by 15% and that number changes as more people are trained and are comfortable with TFS.
• Change Management and Approvals are easier to access.
• More projects are implementing SCRUM methodologies for applications

Read full review