I started to look into this at one point and thought it would be good to switch to using the credentials plugin before working on JCasC support. That is still currently my plan.

I'm currently looking at validating the support. I can say that the defaultTriggerIds are not considered.

The problem seems that the majority of the configuration  is done in ExtendedEmailPublisherDescriptor#configure and not through setters. I'm trying to solve this but I'm afraid I might end up breaking more things than I solve. To be continued.{{}}

I'm already going down this path, I don't think we should duplicate effort.

Do you know when you can allocate time on this? As you are the maintainer, I'm all in to let you handle this the way you prefer.

I didn't mean to rush you or anything. I just want to see how I can help you best on this.

I'll look at it this next week. I have a repo somewhere with most of the changes.

Alex, how can I help you with this task? Could you push your branch publicly, maybe we can divide the work to conquer..

Adrien, Now looking back on this, I remember why it was taking me longer to get it figured out. When using the binding instead of pulling data from the forms manually, there were some things I had to convert to individual jelly files for describable objects. I will push something to a branch soon, I appreciate the help!

Mostly, I deleted the configure method and used @DataboundSetter on the setters. The main issue was on the filters and some other field.