Eventually, I found the JQL that the Maven plugin uses by running the jira mojo 
with -X.

For whatever reason, I resolved the problematic issue with a wrong value in the 
"resolution"
field. It should have been "Fixed (1)" but was "Resolved (longish number)". 
After changing
the resolution, the issue also appeared in the report.

Vote cancelled. I'm redoing the RC.

-- Richard

> On 16.05.2017, at 14:57, Marshall Schor <[email protected]> wrote:
> 
> one other thing, is it repeatable?  I notice apache infra is fiddling with 
> Jira
> - they've got the ability to see what commits go with a Jira almost working
> again (they've set up a version of atlassian fisheye for this, but haven't yet
> enabled logging on, I think).
> 
> -Marshall

Reply via email to