[
https://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271572#comment-271572
]
Alan Parkinson commented on MCHANGES-255:
-
Created MCHANGES-263
> fixVersionIds supports
in JIRA 4.x
> --
>
> Key: MCHANGES-263
> URL: https://jira.codehaus.org/browse/MCHANGES-263
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Components: jira
> Reporter: Alan Parkin
Reporter: Alan Parkinson
JIRA 4 introduced a powerful SQL like query language called JQL. Supporting JQL
can provide powerful ways of downloading issues; Using textual status and
resolved ids instead of numeric based ids, Query by ranges of fixVersion, etc...
Sample JQL:
project
[
https://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=271480#comment-271480
]
Alan Parkinson commented on MCHANGES-255:
-
I'm quite interested in exploiting the JIRA 4
[
https://jira.codehaus.org/browse/MCHANGES-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Parkinson updated MCHANGES-262:
Attachment: MCHANGES-262-maven-changes-plugin.patch
Potential fix
> Using custom issue types
Using custom issue types mapping (MCHANGES-245) throws a llegalArgumentException
Key: MCHANGES-262
URL: https://jira.codehaus.org/browse/MCHANGES-262
Project: Maven 2.x C
[
http://jira.codehaus.org/browse/MCHANGES-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alan Parkinson updated MCHANGES-245:
Attachment: MCHANGES-245-maven-changes-plugin.patch
I have created a possible solution to the t
Custom mapping of IMS issue types to action types for announcements
---
Key: MCHANGES-245
URL: http://jira.codehaus.org/browse/MCHANGES-245
Project: Maven 2.x Changes Plugin
Iss