Hi,

I am using OneDev 9.1.2 and having some trouble defining some new issue transitions.

Currently I have issue states (among others):

• Ready to implement
• In development
• Committed

Then I have defined a new asymmetric, multi-valued issue link named Task with other side named Parent and disallowed multiple parents. Also the issue link only allows issues to be linked with "Type" is "Task". The backlink from task to parent does not have that restriction because the top level issue might be a feature issues or similar. The idea is that an issue can be broken down into smaller tasks and each can be referenced in a commit.

Then I created a following issue hierarchy with all issues being in state Ready to implement:

• Feature issue
  • Task 1
    • Task 1.1
  • Task 2

Now I want:

• transition Feature issue from Ready to implement to In development as soon as any task changes to in development. To do so I used the corresponding issue transition with issue query any "Task" matching(current issue). This works. If I change Task 1.1 to in development via batch edit the whole chain up to Feature issue changes automatically as well.
• transition Feature issue from in development to committed once all tasks are committed. To do so I used a transition with query any "Task" matching(current issue) and all "Task" matching("State" is "Committed"). However this does not work for some reason. I am using batch edit to manually modify the state of tasks one-by-one to state committed but the feature issue does not transition automatically once all tasks are in state committed. Once I manually put all task issues into state committed I can use the query in the issue list search and replace current issue with "Number" is "#3" (assuming that Task 1.1 has number 3 for example) and the query returns the feature issue. So I assume that the query is correct and the feature issue should have transitioned.

Any idea? It is weird that other issue transitions work.