Richard Barnett created MCHANGES-333:
----------------------------------------
Summary: announcement-generate for JIRA don't query for relevant
issues
Key: MCHANGES-333
URL: https://jira.codehaus.org/browse/MCHANGES-333
Project: Maven Changes Plugin
Issue Type: Bug
Components: jira
Affects Versions: 2.9
Reporter: Richard Barnett
{{announcement-generate}} for JIRA submits a JQL query eg
{code}
Address: https://palomamobile.atlassian.net/rest/api/2/search
...
Payload: {"jql":"project = PCSV AND status in (5, 6) AND resolution in (1,
8)","maxResults":25,"fields":["*all"]}
{code}
and then selects issues from the response which were fixed in the current
version. If no issues are selected the goal fails, eg:
{code}
Couldn't find the release '1.0.76' among the supplied releases:
[Release[version='1.0.73.1', date='null', description='null', actionsSize=2],
Release[version='1.0.73', date='null', description='null', actionsSize=3],
Release[version='1.0.72', date='null', description='null', actionsSize=2],
Release[version='1.0.75', date='null', description='null', actionsSize=5],
Release[version='1.0.74', date='null', description='null', actionsSize=4],
Release[version='1.0.74.1', date='null', description='null', actionsSize=1],
Release[version='1.0.71.2', date='null', description='null', actionsSize=1],
Release[version='1.0.71.1', date='null', description='null', actionsSize=1]]
{code}
By contrast, {{jira-report}} uses a JQL query with a constraint on
{{fixVersion}}; eg when {{onlyCurrentVersion=true}} for the same pom as above
the query is:
{code}
Address: https://palomamobile.atlassian.net/rest/api/2/search
...
Payload: {"jql":"project = PCSV AND fixVersion = \"1.0.77\" AND status in (5,
6) AND resolution in (1, 8) ORDER BY priority DESC, created
DESC","maxResults":100,"fields":["*all"]}
{code}
It seems like {{announcement-generate}} should use the same JQL query that
{{jira-report}} does in this case.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
