Redmine

I'm using #100 as the one you set the relationship on and #101 as the "related to"

• Related - Just adds a link to the other issue
• Duplicates - Links issues so that changing the status of one, will change the other (e.g. closing #100 will close #101)
• Blocks - Defines an "order". I think it might affect the Gnatt chart but I don't know.
• Precedes - Defines an "order", where issue #100 needs to be completed x days before y can be started on.

I only use Related and Duplicates. Related is great for linking similar issues.

I've added this documentation to the FAQ.

Eric

Maybe Jean-Philippe has to explain this, because I remember there was an incomplete implementation of this feature in r506.

Quote:

• relates to: do nothing special. Just to know that the 2 issues are related...
• duplicates: will close the related issue with the same status when closing the issue (not implemented yet)
• blocks: will require to close the blocking issue before closing the blocked issue (not implemented yet)
• precedes (end to start relation): start date of the related issue depends on the due date of the preceding issue (implemented). A delay can be set so that the related issue can only start n days after the end of the preceding issue. When setting dates for an issue, dates of all downstream issues are set according to these relations.

And what is this in the Wiki page, Eric: "Blocks - Defines an "order". I think it might affect the Gnatt chart but I don't know." !?
This FAQ page is supposed to give answers, not guessings.

Regards,
Nikolay

IMHO, implementation of duplicates should be something like this:
Let's say we have ticket A (master) and users created also tickets B C D - (let!s call them slaves).
So B C and D are set as duplicates to A.
For me as project manager, when I found duplicates I would like to close duplicases and keep just one master ticket A.
So first I would like to set B C D as master and then close them (mabe I copy and paste some usefull additional info into mastter ticket).
But when closing is done automaticaly to all linked (blocked) issues, the all issues will be closed, even when I would like to close slave only...
I thing that closing master should also close slaves, but closing of slave should left other issues intact.

I agree with Maxim on this one. The automatic closing of duplicates left me unexpectedly with no open issues tracking my overly reported problem. In other words, even though the behavior of duplicates is clearly explained above, that implementation is counter intuitive to the casual user.

I think it also causes a subtle record updating bug as described in my other post.

Best regards,
Dan

So, open a feature request, pointing to this thread.