How to describe a project with this structure...

As I seen another use of this could be the following:

1) use the milestones as controllers
2) use ticket categories as modules
3) use tickets as controller's actions
4) use tasks in tickets as tasks for the actions of the current controller.

For example lets say we have the module Users which have the login controller which contains the authentication action on which we want to give to the current session a name of the user who successfully authenticated.

1) We use a ticket category called Users that will correspond with the module
2) We use a milestone as a controller called Login
3) We use a ticket as an action which called Authentication (or Auth)
4) We create tasks in the ticket that says what should be done for the current action.

It would produce a better looking organized content. The only thing is that I don't like the idea of using objects in a different way but as there isn't any other way (i guess) I will roll with that way...

Thanks for the reply Ilija, I don't really think that it would be like programming it would be more like completely describing the application so having modules/controllers/actions separated would be very nice as you can have things clear and work on them better.

Currently I'm using the concept like this:

1) I describe my modules on pages (discussions could be used too but I prefer pages)

2) I add the module name into ticket name

3) I create milestones for each module/controller for example for default module I have Default_IndexController Default_DemoController and etc for the users model I have Users_IndexController Users_DemoController and etc

4) I create tickets that are the actions for each controller

5) and then I create tasks for each tickets that are the tasks that have to be done for each action. Tasks includes both bugs that have to be fixed and features that have to be added and ideas for the future, I keep bugs as high priority features to be added as medium priority and ideas for the future as low priority

With this way I actually managed to get exactly what I was needed, and discussions are untouched for maybe later use.

Version tracking is a bit and issue I created a category called change-log there I create change logs on every new version release and also I'm using Files for versions but with files you cannot have 0.1, 1.1 and etc

Timepost helps a lot because I track the time that took me for each item (this is helpful to set a logic price latter on)

Checklists for now are not used but I think that discussions and checklists would be used on client level, but I guess I will keep this project private for internal purposes only.

I'm not use Sources yet because unfortunately I'm not very familiar on how to create a repository, I have my own servers with Debian 5 but I really never tried to create a repository before.

Sorry that I was go a bit off-topic at the end but I would appreciate it if you or anyone could help me on the repository thing, any tutorial or something would be great, I really would like to create a repository for the current project :)

Thanks in advance

Hello, Ilija, sorry for getting off-topic again but I tried a repository from beanstalkapp.com with a free account I added it to AC but when I pressed "Browse Repository" I got a fatal error:

Fatal error: Call to a member function getRevision() on a non-object in /home/admin/domains/example.com/public_html/projects/activecollab/application/modules/source/controllers/RepositoryController.class.php on line 340