Project

General

Profile

Forums » Help »

Issue status (specified, coded, tested, ...) and percentage...

Added by di naiz about 14 years ago

Hi !

After struggling a bit to install it on a shared hosting, I finally discovered the power of redmine. I must say I'm pretty impressed. However I'm a beginner, and stumbling into the manual and the forums didn't help much for what I'm trying to do, so I ask here. PLease forgive me if it's already addressed somewhere

We are doing a software developpment project, and we are trying to get organized. At the moment, we entered all the developpement tasks as features into redmine. However we would like to enforce that, for a task to be completed, it must have been
- specified
- coded
- tested
- some other project specific stuff not relevant here

I can't use issue statuses, because that would impose a particular order (like testing after coding, BUT sometimes, we want to be able to write the test before the code, and sometimes not)

I don't really know how to achieve that :-(

What I tried so far is :

  • for every task, create a subtask, for coding, testing, and so on ... It works well but it's very tedious, and it makes the number of issues a bit overwhelming
  • use custom boolean fields. It's ok but :
    - I can't make a search filter like "find the tasks which are NOT
    - I can't setup the completion percentage to depend on the subtasks (e.g : prevent someone from marking a task as 100% completed if it hasn't been tested)

I'd like to get some insights from experiences redmine users, about how to achieve this. I must admit I'm a beginner in both redmine and project management, so I'm really trying hard to find the best way to deal with that.

Any help appreciated
Best regards


Replies (2)

RE: Issue status (specified, coded, tested, ...) and percentage... - Added by di naiz about 14 years ago

Sorry, apparently it's in the wrong section. Moved to "general discussion".

RE: Issue status (specified, coded, tested, ...) and percentage... - Added by Kai Meyer about 14 years ago

I think that the Workflow based on status is the only way you can accomplish what you're after.

I was given some good advice some time ago that applies well here. "There's always two sets of rules. The ones that are written down, and the ones you follow." Just because you can start on step #2 before step #1 is completed, that doesn't mean that you have to express that in your workflow. Just make it so that you can't complete step #2 before step #1 is completed. You can't finish writing the code before you've specified it. You can't finish testing the code unless you've finished coding it. You can't do something else with the project unless you've tested the code.

Establish the work flow in Redmine, and then work on the project the best way you can.

    (1-2/2)