indeed.
we need to decide here what automation we want (each flow has its cons & pros)
moving bugs from POST->MODIFIED
- pros
- bugs are not forgotten on POST and waiting for manual action, leaving possibility of not moving to ON_QA on a release even though they are fixed.
- cons
- bot can't know if bug is solved completely and more patches are coming.
solution:
- use bug-url ONLY in the main patch that when its merged then bug will move to MODIFIED, all other patches should use related-to: (we can ensure bug won't change status for related to patches)
moving MODIFIED->POST
- i think in any case we should stop doing this, and its the maintainer responsibility to move it back to POST if he didn't add all patches.
- adding a comment will help the bug owner know about this issue.
e.