Written on top of Subversion and delivered as a plugin to the Developer Portal, the Mendix Team Server is designed to make the life of a Mendix developer easier. The Mendix Modeler is tightly integrated with the Team Server and actions like creating a new project (including a versioned model repository), updating, committing changes, and merging model versions are all available from within the Mendix Modeler as a single click action.
The Team Server is delivered as a plugin of Developer Portal for a reason: it enables you to manage Team Server access from the Developer Portal, and it enables Mendix to provide you with a revolutionary way to combine requirements, implementation, and feedback! When you commit application model changes to the Team Server from within the Modeler, you can select the user stories (reflecting requirements) that you have been working on. The Team Server will automatically create links between these user stories and the model changes you made, providing you with a way to navigate from commits to the associated requirements. Furthermore, with these links, Mendix creates a link from a user story to a changeset, which can include a link to a form (if you changed a form in the changeset). While feedback also refers to a form, Mendix can create links between feedback, forms, changesets, and user stories.
The Team Server also connects the capture-and-develop phase of the agile application lifecycle. When you start working on the next version of your application, you just open the Modeler to see the user stories planned for the current sprint and start working on them. If a user story is based on user feedback, you can directly jump to the form mentioned in the metadata of the feedback and start implementing the requested change.