id summary reporter owner description type status priority component severity resolution keywords cc release 2692 "TracError : Invalid action ""resolve"" when used with svn hooks and testing workflow" pierreroth64@… Ryan J Ollos "I'm trying ot use this MasterTickets plugin with the following configuration : {{{ Trac: 0.11dev-r6647 Python: 2.5.2 (r252:60911, Feb 21 2008, 13:11:45) [MSC v.1310 32 bit (Intel)] setuptools: 0.6c7 SQLite: 3.5.2 pysqlite: 2.4.1 Genshi: 0.5dev-r789 mod_python: 3.3.1 Pygments: 0.9 Subversion: 1.4.6 (r28521) jQuery: 1.2.3 }}} The problem is the following : I've set up the trac post and pre commit hooks on the SVN server side. They enable me to close a ticket when committing doing a '''""fixes # - ""''' and '''everything's working fine...''' I've configured trac to use the [http://trac-hacks.org/wiki/TestingWorkflow testing ticket workflow ]. Then when committing with a ""fixes #56 - blabla"" message, the ticket #56 is automatically sent to the testing status '''everything's still working fine...''' I installed the MasterTickets plugin. Then created two tickets #12 and #13 for example , #12 blocking #13. If I try to resolve #13 from the trac interface, trac reports that #13 is blocked by #12... ok... that's fine ! But, and finally the problem comes : what happenss if I commit a change to my repos with a ""fixes #13 - blabla"" ? -> I tested it '''and it failed''' : * the hooks executes without any error (normal as no check on the blocked state is done within the hooks) * if I refresh the ticket #13, trac reports the following error: {{{ Trac Error Invalid action ""resolve"" }}} So, don't know if that's to be corrected on the hook side (returning an error when committing a ""fixes.."" command on a blocked ticket) or on the trac (MasterTicket plugin) side ignoring the fixes command which sets the resolve field..." defect new normal MasterTicketsPlugin normal pierreroth64@… 0.11