A typical workflow in the ASF is:

1. upload patch to a Jira issue
2. set state to Patch Available via Submit Patch
3. Jenkins testing + human reviews
4. upload new patch
5. go back to step 3 until reviews are all positive and Jira is closed or work is abandoned

To enable this workflow, we currently handle the JIRA+Jenkins integration via the Apache Yetus' precommit-admin script located [here|https://github.com/apache/yetus/blob/master/precommit/src/main/python/jenkins-admin.py].  As more users move to pipeline jobs, authing via REST to trigger the other jobs is harder since Pipelines don't support token-based auth.  Before we start reworking this code (likely as Groovy code that calls buildJob() via hackery), we thought we'd check in on what Jenkins plug-ins  have to offer.

jira-trigger-plugin is the closest to handle this workflow.  With it, checking the state is relatively easy (changelog matching, status = Patch Available). However, it doesn't appear that jira-trigger-plugin gives any sort of state of the attachment or that there was a new one uploaded.  In fact, my attempts to debug this led to trying to setting the Parameter mapping to 'attachment' or anything closely related  causing nothing getting executed.  (I don't have access to the logs to see if there is a stack trace, but I suspect that there is.)

Hopefully I'm just missing something, but if not:

My feature request would be this:  we need a way to trigger specifically on attachment changes and expose attachment details.