Don’t want to be annoying, just hope this report is useful 
Tested in try.vikunja
Frontend Version: 0.22.0+32-5e991f3024
API Version: v0.22.0+10-27a5f6862b
How to reproduce:
- Create two tasks: Task A and Task B
- Make Task B subtask of Task A
- Move Task A to different project
Expected behaviour:
Alternative A:
- Task A is shown in new project
- Task B is shown in new project as subtask
Alternative B:
- Task A is shown in new project
- Task B stays visible in initial project
What happens:
- Task A is shown in new project
- Task B is hidden
- (can see Task B when viewing Task A’s details)
Looks like a bug - I’ll take a look.
Fixed in 664bf0a5f4 - please check with the next unstable build (also on try in ~30 min).
@kolaente I have couple of questions here. Need to understand how it should be functioning before fixing a related bug.
On try Task B is no longer displayed in initial project after Task A (parent) was moved to other project. That’s even though initial project is still assigned to Task B.
- Should Task B still be visible in inital project without parent?
- Should Task B still be visible in inital project under the parent?
- Shouldn’t Task B project automatically be changed to parent’s Task A new project IF all Task B’s parents are now of same project?
Yes.
I’d say no, but that’s debatable. What would you expect?
Definitely no, because that would defeat the feature of related tasks being in different projects.
1 Like