Redmine

Hi.

I use redmine for my private task managing. Thank you for your effort.

Recently, my team use codebeamer for new project.

Codebeamer is very good tool. That has almost all feature for project management. Ticket, Build system, Deploy, Configuration management etc..)

During so many functions, "ticket relation" is very useful. So I recommend this function for next redmine.

Ticket relation is simple. All ticket can has three kind of relations.

• parent
• child
• related
  Each Ticket relations is not limit number each other.

And this relation show in task list, task detail. Close ticket is strike mark in list. (See below work process story)
(See Also, See Codebeamer task list 's number 27831 ticket and find closed tickets )

If ticket relation exist, we can have this process.

(Foo, Bar, Sam is person.)

1. 'Foo' reported bug A ticket.
2. 'Bar' reported bug B ticket.
3. Bug A,B ticket is small and related each other. So, 'Sam' make 'A and B' task ticket that related bug A, B ticket.
4. useful this relation
   1. During task, 'Foo', 'Bar' search their reported task and related task.
   2. After 'A and B' task end, team are retrospected 'work process' by ticket relation.

As a result, we can see this style list.

1. Task-13 edit for bug A, bug B
   1. Bug-11 , Bug-12
2. Task-14 ...
3. Task-15 ...

After my team recently milestone end, We easily see ticket dependencies and retrospecting.

Before we use, My team write ticket number to content area and search. But this method is useless.

I recommend ticket relation.