You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jeff Black (JIRA)" <ji...@codehaus.org> on 2013/01/15 17:09:14 UTC

[jira] (MCHANGES-286) Support for Jira custom fields in jira-report columnNames

    [ https://jira.codehaus.org/browse/MCHANGES-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317360#comment-317360 ] 

Jeff Black commented on MCHANGES-286:
-------------------------------------

I second the idea, as it is important concept for the report to be delivered to external clients that do not have access to our internal JIRA system.
                
> Support for Jira custom fields in jira-report columnNames
> ---------------------------------------------------------
>
>                 Key: MCHANGES-286
>                 URL: https://jira.codehaus.org/browse/MCHANGES-286
>             Project: Maven 2.x Changes Plugin
>          Issue Type: Wish
>          Components: jira
>    Affects Versions: 2.7.1
>            Reporter: Peter Friberg
>
> A lot of important info is often described in Jira custom fields. In my case, the report will not fulfill the requirements because I can't output some important customfields in the report.
> I would be happy to see support for this. For example, be able specify:
> {code:xml}<columnNames>Key,Type,Priority,Summary,customfield_10023, customfield_10041</columnNames>{code}
> The descriptive name of the customfield should be returned back to the report.
> It would be a good start with the simple custom field types, such as text fields and single select.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira