Evaluate Changelogic without registration!
  

Managing Project

What is a project? A project in Changelogic corresponds to one application that is being managed. It's not a project on it's traditional meaning, when some people even call big requirement a project.

A project can also be defined as codebase or VCS repository, being the item with longest lifecycle among software artefacts.


A project is further divided into development cycles.

Project's details view (project -> details) gives quick overview of projects data, security options, modules, users and their roles and functionality stages this project has. To change project's data, you need to have project administrator's role.


Project actually may or may not correspond to real project in VCS server – if you want to use Changelogic only for task management, then it never needs to know anything about VCS. Although, this approach does not make use of Changelogic's main value propositions in form of quality control procedures like code review and acceptance nor the branching model.


Here is an example of project's detail form:



Project options:

  • VCS server – VCS server refers to the VCS server where the source code is stored, see VCS servers for more
  • Repository – repository refers to the top level VCS direcory where the source code of your project resides
  • Developer may review – if this option is checked, developer may review his/her own change
  • Developer may integrate – if this option is checked, developer may integrate his/her own change
  • Reviewer may integrate – if this option is checked, reviewer may integrate the change he/she reviewed
  • Task resolver may verify – if this option is checked, task resolver can verify the task he/she resolved
  • Allow microchanges – if this option is checked, changes may contain changes itself

We suggest leaving the options for allowing the same people to handle different states of change unchecked except for very small projects where there are not enough people. The aim is to have the change seen by many pairs of eyes and built in several environments. Also, reviewing by developer imposes a conflict of interests – it's quite pointless to have developer of a change review his own code, as he assured the conformance of code to any quality target by ending development already.