-
Suggestion
-
Resolution: Fixed
The columns list is fixed for the jiraissues macro. It would be nice to be able to pull in data from custom fields for display. For example - our rss feed has the following custom fields.
-
<customfields>
-
<customfield id="customfield_10010" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
<customfieldname>Commited To</customfieldname>
-
<customfieldvalues>
<customfieldvalue>No</customfieldvalue>
</customfieldvalues>
</customfield>
-
<customfield id="customfield_10020" key="com.atlassian.jira.plugin.system.customfieldtypes:float">
<customfieldname>Rank</customfieldname>
-
<customfieldvalues>
<customfieldvalue>
2
</customfieldvalue>
</customfieldvalues>
</customfield>
</customfields>
It would be great to be able to add "customfield_10020" to the list of columns to display.
- incorporates
-
CONFSERVER-6878 jiraissue macro not including desired columns
-
- Closed
-
- is duplicated by
-
- Closed
- is related to
-
- Closed
-
- Closed
- relates to
-
- Closed
[CONFSERVER-2407] Add custom fields to the list of columns to display in jiraissues macro
Jonathan Costello [Atlassian]
added a comment - https://support.atlassian.com/browse/JSP-34174 Jonathan Costello [Atlassian]
added a comment - Hi Nathan,
I was able to produce this problem using JIRA 3.13.2 and Confluence 2.10.1. I created a custom field, filtered on it, and the field didn't show.
Cheers,
Jon
Jonathan Costello [Atlassian]
added a comment - Hi Nathan,
I was able to produce this problem using JIRA 3.13.2 and Confluence 2.10.1. I created a custom field, filtered on it, and the field didn't show.
Cheers,
Jon 
Nathan Dwyer [Atlassian]
added a comment - This issue has been moved to http://developer.atlassian.com/jira/browse/CONFJIRA-98 because all the related code is in that plugin. The code review is being handled there as well.
Nathan Dwyer [Atlassian]
added a comment - This issue has been moved to http://developer.atlassian.com/jira/browse/CONFJIRA-98 because all the related code is in that plugin. The code review is being handled there as well. Nathan Dwyer [Atlassian]
added a comment - Please see CONFJIRA-98 
Cheryl Jerozal [Atlassian]
added a comment - Hi Frank~
Selection of columns will be done using the custom field name, not the id. (Even for engineers, the id is a bit much. 
) There is no prefix in our implementation, but we may implement some sort of prefix in the future (though probably not in the way it seems you have according to comment above). Thanks for reminding me to file an issue for this:
http://developer.atlassian.com/jira/browse/CONFJIRA-91
~Cheryl
Cheryl Jerozal [Atlassian]
added a comment - Hi Frank~
Selection of columns will be done using the custom field name, not the id. (Even for engineers, the id is a bit much. ) There is no prefix in our implementation, but we may implement some sort of prefix in the future (though probably not in the way it seems you have according to comment above). Thanks for reminding me to file an issue for this:
http://developer.atlassian.com/jira/browse/CONFJIRA-91
~Cheryl 
Frank Stiller
added a comment - Sounds promissing Per,
How will the API be to select such Customfields? is it with the internal Customfield_10000 ID or like my current implementation the output-name? I guess you are not using a prefix for it, do you?
cheers
Frank
Frank Stiller
added a comment - Sounds promissing Per,
How will the API be to select such Customfields? is it with the internal Customfield_10000 ID or like my current implementation the output-name? I guess you are not using a prefix for it, do you?
cheers
Frank 
Daniel Phalp
added a comment - This is an automatic reply. I will be away today returning on Sept 12.
Thanks,
Daniel
Daniel Phalp
added a comment - This is an automatic reply. I will be away today returning on Sept 12.
Thanks,
Daniel 
Per Fragemann [Atlassian]
added a comment - Hi John and Frank (and all other watchers of this issue)
we had planned to deliver this improvement in Confluence 2.9, but unfortunately the code was just not ready for production, so we didn't release it. It will ship in Confluence 2.10 though, which is due in early November. See attached screenshot from our internal Confluence system (and yeah, ignore my funny UI settings)
Cheers,
Per Fragemann
Team Lead Confluence Development
Per Fragemann [Atlassian]
added a comment - Hi John and Frank (and all other watchers of this issue)
we had planned to deliver this improvement in Confluence 2.9, but unfortunately the code was just not ready for production, so we didn't release it. It will ship in Confluence 2.10 though, which is due in early November. See attached screenshot from our internal Confluence system (and yeah, ignore my funny UI settings)
Cheers,
Per Fragemann
Team Lead Confluence Development John you are right, its still with the community. But the Labels of this Issue say: 2_9_plugin_work potential. Well whatever that means, but i think looking at 2.9 will give us some light. But still i have doubts that this will get fixed by Atlassian soon (no statements no light).
Frank Stiller
added a comment - - edited John you are right, its still with the community. But the Labels of this Issue say: 2_9_plugin_work potential . Well whatever that means, but i think looking at 2.9 will give us some light. But still i have doubts that this will get fixed by Atlassian soon (no statements no light). 
To everyone watching this issue,
This was mistakenly reopened; we haven't found any indication that this functionality is not working correctly. If you do discover any issues, please follow the guidelines for dealing with issues marked as fixed against a released version.
Apologies for the inconvenience.
Regards,
Andrew Lynch