since i plan to make the whole thing a little more flexible i wouldn't want to pollute a system table of trac with my stuff. At the moment I am at a point where i could allow to creat as many webhooks as a user would need and provide as many payload templates as needed. That said only one template for each ticket action would be active of course.
Over the weekend I hammered out a basic user interface in the admin panels for all this but its not really ready for the github repo since i need to decide how to store the data first. I am no frontend guy so my stuff looks pretty ugly at the moment but it will do the job i guess. If someoen with more skills in jinja2 / js / css out there wants to take a shot at the design as soon as i push it to the repo feel free to do so and make a pull request. Here are some pics how it looks like at the moment
but back to the config for the webhooks and payloads, for now i would simply store it in the ini and that would be fine since it would be onyl one template for each type of payload but as mentioned it will be more flexable and then i dont want to pollute the ini further with it. So I guess i try to figure out how to update the database with a table for the payloads and the webhooks or try to store the payload stuff in a seperate file as well as the webhooks.