Redmine

+10 for this one.

I dont know how this is implemented, but probably there's a model 'relation' with a key to both issues being in relation. If so, it is really easy to add a "follows" in the menu popup, that will just created a 'precedes' by inversing the two issues.

As Jonas, almost all the time when i need such a relation is when i create the second issue, and i want to say it should only be adressed after another one. My current way of doing is to 'remember' the number of the new one, go to the other one and add a relation "precedes" .. which is both tedious and dangerous (i have a very very bad short term memory)

+ 1
I find myself have the same problems as Thomas, (including the short term memory).
I was wondering if the implementation could be on the issues page. This would take two parts
1. Use the right click and be able to perform the relationships.
2. The second part would be to be able to display and sort by relationship.
This would alow us to go through all of the tasks and do the first shot as scheduling on the page that has all of the tasks.

Just another +1 on this. It is an important time saving feature for us.

Krzysztof Podejma there seems to be a lot unrelated changes in this patch. Why is that?

Krzysztof Podejma wrote:

Sorry, I had a strange problem with my svn working copy. I'm uploading once again.

Thank you! This patch works great for me.

I'm happy it helps you.
Is it possible to apply my patch to the trunk?

Regards
Krzysztof Podejma

This is just a bump so it shows up in activity. This patch is good and ready for the trunk!

Eric says the only thing holding this patch back is people to push for it. But more particularly unit tests for the Issue Relation Model, see #4438. Any up to coding those tests?