Ok, I see. There are already several tickets describing this Problem. And for 1.3.0 there's a new chain Event for preprocessing which gets called before any status-transisitions are handled. This solution looks good.
So I will create a local patch (firing the event before the status-handling) in ...
Search found 4 matches
- 23 Jun 2016, 05:37
- Forum: Help
- Topic: How can I enforce a two-man rule for closing issues
- Replies: 10
- Views: 10327
- 22 Jun 2016, 12:23
- Forum: Help
- Topic: How can I enforce a two-man rule for closing issues
- Replies: 10
- Views: 10327
Re: How can I enforce a two-man rule for closing issues
ok, next one, can't stop researching this ;)
bug_update.php calls bug->bug_resolve which calls bug->bug_set_field for the status which update bug-table and calls history_log_event*.
So the poblem seems to be, that the code block to "hadle status transitions that come from pages other than bug ...
bug_update.php calls bug->bug_resolve which calls bug->bug_set_field for the status which update bug-table and calls history_log_event*.
So the poblem seems to be, that the code block to "hadle status transitions that come from pages other than bug ...
- 22 Jun 2016, 11:51
- Forum: Help
- Topic: How can I enforce a two-man rule for closing issues
- Replies: 10
- Views: 10327
Re: How can I enforce a two-man rule for closing issues
Since my last changed on my first reply are not approved yet, I have to write a new reply:
Some deeper digging and logging gave the following result:
history_log_event_direct is called for the field "status" after submitting the bug_change_status_page.php but before the event_signal in bug_update ...
Some deeper digging and logging gave the following result:
history_log_event_direct is called for the field "status" after submitting the bug_change_status_page.php but before the event_signal in bug_update ...
- 22 Jun 2016, 05:50
- Forum: Help
- Topic: How can I enforce a two-man rule for closing issues
- Replies: 10
- Views: 10327
Re: How can I enforce a two-man rule for closing issues
Hello,
I am a colleague of TDS and started to write a plugin yesterday.
I have one big problem:
My hook on the event "EVENT_BUG_UPDATED" seems to be called only AFTER the bug-update has been written to the DB. This way, I cannot prevent a status-change from "to be tested" to "resolved".
The ...
I am a colleague of TDS and started to write a plugin yesterday.
I have one big problem:
My hook on the event "EVENT_BUG_UPDATED" seems to be called only AFTER the bug-update has been written to the DB. This way, I cannot prevent a status-change from "to be tested" to "resolved".
The ...