# WebHookEventType and the solved and assign plugins

**URL:** <https://meta.discourse.org/t/webhookeventtype-and-the-solved-and-assign-plugins/144180>\
**Category:** Bug\
**Created:** [March 13, 2020, 8:32am UTC](https://meta.discourse.org/t/webhookeventtype-and-the-solved-and-assign-plugins/144180 "2020-03-13T08:32:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [March 17, 2020, 7:40pm UTC](https://meta.discourse.org/t/webhookeventtype-and-the-solved-and-assign-plugins/144180/8 "2020-03-17T19:40:28Z")

</div>

Ok, you are completely right, my apologies for being unclear. I was mixing up ‘broken’ and ‘not available’, and since this is a new feature there is indeed nothing broken.

It does feel a bit strange how seeding code for a plugin is moved into core though. I can understand that you want to reserve the ID’s but I think it would be more clean to leave the seeding in the plugin. But that’s just my own personal opinion 😉

---

_[View the full topic](https://meta.discourse.org/t/webhookeventtype-and-the-solved-and-assign-plugins/144180)._
