Redmine

Hans Raaf wrote:

When I switch the tracker to "defects" the parent task field appears but is empty.

That is the expected behavior. The field is an autocomplete field.

Hans Raaf wrote:

I also wonder why adding sub tasks does not start with the same tracker type.

Good point, this should be changed.

Etienne Massip wrote:

Hans Raaf wrote:

When I switch the tracker to "defects" the parent task field appears but is empty.

That is the expected behavior. The field is an autocomplete field.

Yes, but if you arrive on the new issue form after clicking "add subtask" from an existing issue, this means that this issue id is lost.

Just a thought while talking about subtasking: I think that the "Add" link in "Subtasks" should be renamed to "Create new" to prevent confusion with the "Add" link of the "Related issues" (or best, have the 2 options).

Each time I think it will behave just like "Related issues" and offer me a field where I could fill the subtask id.

And why not even rename "Subtasks" to "Sub-issues" to make vocabulary consistent…

Jean-Philippe Lang wrote:

r10662 sets the tracker of the parent issue as the default tracker for the subtask, it should solve your problem.

Etienne Massip wrote:

Just a thought while talking about subtasking: I think that the "Add" link in "Subtasks" should be renamed to "Create new" to prevent confusion with the "Add" link of the "Related issues" (or best, have the 2 options).

If we need to change, I think that "Add new" would be better ("Create" is generally use for saving submitted data).

Why not just "New" and I can fill a FR to add a "Add" actually working the same as the "Add" of "Related issues", i.e. allowing user to select already existing issues for being subtasks of the current issue?

And why not even rename "Subtasks" to "Sub-issues" to make vocabulary consistent…

While it may look more "consistent" (and my practice of english is not good enough to judge), it looks also not so natural (just have a look at the request #443).

Same, agreed.