Redmine

Frederic FORESTIER wrote:

I install the last release of redmine and since, i can't do what i did before.

You should still be able to use your workflow. The change seems to only affect the autocomplete on the field, so you should still be able to manually set an 'unrecognized' issue as the value.

Why do you want to disable the respective patch? I'm asking because the scope of that patch was to propose in the autocompleter only valid issues. Even if you'll type manually an 'unrecognized' issue, you'll receive a validation error on save.

Frederic Raes: sorry, but please forget my first answer. Marius confirmed the actual behaviour. And, after his answer, I'm curious too, about your specific use-case.

Marius BALTEANU wrote:

[...] Even if you'll type manually an 'unrecognized' issue, you'll receive a validation error on save.

Thanks for chiming in and clearing it up. Though I wasn't entirely sure while posting (hence my use of 'seems to'), I should have had a better read on the issue (with its ancestry).

Hello and thanks for your answers.

You should still be able to use your workflow.

Why do you want to disable the respective patch? [...] you'll receive a validation error on save.

And, after his answer, I'm curious too, about your specific use-case.

I use subtasks to create a tree between different types of trackers like "evolution" and "bug".

I can finish an evolution and discover a bug later, but like the "evolution" is closed, i can't write it in parent task's field without receive a validation error on save.

Frederic FORESTIER wrote:

[...]
I can finish an evolution and discover a bug later, but like the "evolution" is closed, [...]

Parent issues can only have open subtasks if itself isn't closed. So, in your case, you would have to reopen the parent before you can add open subtasks to it. See issue #10989.