Duplicated tasks are not automatically closed

[tobelix87]

If you duplicate a task to another project and close the origin task, the duplicate is not closed.

In my eyes this makes no sense. As long as both tasks have an internal link between each other, this means that the task stands for the same work. If this work is done and the task gets closed, the duplicated task connected with an internal link should be closed automatically as well.

If I duplicate a task and remove the internal link, then I can use it as a copy and maybe adjust the copy a little bit. In this case it is not necessary that the duplicate gets automatically closed.

[Kolossi]

FWIW I can see some value in this "duplicate is same work" use case, but I think it's a stretch to say that a duplicated task in another project not closing "makes no sense".

I can see this as a feature request if there is e.g. a "same work" link type between the tasks, but not just on all duplicates - a use case off the top of my head : a task "clean classroom for governor's visit" in teachers work project gets duplicated to "clean staffroom for governor's visit" in maintenance staff project. classroom being cleaned does not mean staffroom is cleaned!

This scenario might be flawed but hopefully makes the point that a duplicated task in another project may or may not represent the same work.

Any changes to support the idea when it is applicable should be careful not to break scenarios when it isn't.

[rautamiekka]

A compromise: when duping, choose whether to delete the link.

^ Better yet: allow deleting and ignoring the link when doing something that involves the link. Once deleted, no such choice, of course.

[Kolossi]

Whilst seemingly not unreasonable on the face of it, this would change existing functionality which is not a good approach to software development.

It's sometimes necessary in certain cases of a clear bug, but I don't think that's the case here - and certainly not with software in maintenance-only mode.

If any change happens istm it would be best to have it as a new option - my suggestion being based on a specific new link type, but anything non-breaking of existing would be great.

[tobelix87]

I can see this as a feature request if there is e.g. a "same work" link type between the tasks, but not just on all duplicates - a use case off the top of my head : a task "clean classroom for governor's visit" in teachers work project gets duplicated to "clean staffroom for governor's visit" in maintenance staff project. classroom being cleaned does not mean staffroom is cleaned!

This scenario might be flawed but hopefully makes the point that a duplicated task in another project may or may not represent the same work.

I agree that this is a valid scenario but I am wondering if there is a reason that I need to know that cleaning staffroom was duplicated from cleaning classroom. I would say duplication was in this case only done to save time in creating the task. In this case a link between both tasks would not be needed.

Any ideas why a link would be needed for duplicated tasks which are not same work?
If not, how about

1. choosing if link should be deleted or not while duplicating.
2. adding functionality to automatically closing (or actually updating in general) all linked tasks. this functionality can be toggled via config. By default, it is disabled. So no system will break when upgrading to a new release

[tobelix87]

any thoughts from anyone else?

[Zelkin0815]

Hi

the function to link tasks together and keep their content synchronized across projects would be very helpful!
this could be solved via the internal link?!
duplicates are first independent of each other until you link them, then the content is kept completely synchronous.
If then still the possibility exists to link sub tasks with tasks in other projects, then this would be a huge benefit!
this could be e.g. then depending on the column or when the task is closed as a subtask mark done

What's the best way to make a feature request??
Here there is only pull request!