You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Benson Margulies (JIRA)" <ji...@codehaus.org> on 2011/06/04 17:16:22 UTC

[jira] Commented: (MCHANGES-255) fixVersionIds supports human readable display versions in JIRA 4

    [ http://jira.codehaus.org/browse/MCHANGES-255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=269541#action_269541 ] 

Benson Margulies commented on MCHANGES-255:
-------------------------------------------

Once could, but there's no JIRA API to obtain them, and it would be a big job to add jira-4-specific querying. Obtaining them is a matter of waving your mouse over an obscure location in jira.

> fixVersionIds supports human readable display versions in JIRA 4
> ----------------------------------------------------------------
>
>                 Key: MCHANGES-255
>                 URL: http://jira.codehaus.org/browse/MCHANGES-255
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Bug
>          Components: jira
>    Affects Versions: 2.5
>            Reporter: SebbASF
>
> http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#fixVersionIds says
> bq. Sets the fix version id(s) that you want to limit your report to include. These are JIRA's internal version ids, NOT the human readable display ones.
> This may be true for JIRA 3, but for JIRA 4, AFAICT one can use the human readable versions.
> It would be helpful to document how to obtain the internal version ids, if these are still supported or needed.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira