The object used to represent the reason for the change. Change requests are created and managed by the Change Tracking system. Some users of the SCM system, especially testers and release managers, will more naturally converse in terms of change requests rather than tasks. The object used to group a set of tasks. Also, a folder can contain change requests, which is an easy way to get all of the tasks associated with a particular change request.
Folders can also contain other folders.
Implicit Tasks - Tasks that are not specified explicitly, but are implied because of other tasks that depend on them. You can consider a discussion the evolution of a comment on a file version. Rather than a single flat comment that records information about the change, a discussion captures the reasoning that led to the change, as well as the conclusions. Workflow - The workflow of a task or change request refers to its movement through the organization. For example, a task might start out with one or more developers who make the software changes, then pass to the release manager to be built, and then pass to the quality assurance team for testing.