|
The motivation behind this feature is to provide more detailed information than a typical RSS feed has, and allow the user to transform that information into another format.
The first part of that statement is related to JRA-12062, the second part goes beyond the scope of that issue though. More than simply having all displayed fields available in XML, I want to be able to transform those fields into different document formats. People typically use the issue information to drive their projects. Most often this involves using the information for project plans (in MS Project or GanttProject), or as documentation in a Requirements Document. In a previous job, I created a new issue type called "Requirement" and then used Oracle's XSQL functionality to query JIRA and generate documentation. This made the process of delivering software fairly transparent and easy to manage. I was also able to generate GanttProject files. Rather than having to recreate this hack though, it would be nice if JIRA provided this functionality "out of the box". This would give JIRA a more central role in the software delivery life cycle, since it would then be able to handle everything from Requirements gathering to Implementation, Testing, Deployment and Maintenance. Mark,
Thanks for the update. The things you are doing with JIRA are definitely interesting. The Issue Navigator views are plugins in JIRA since 3.7. So it is possible to add your own. Therefore, it should be possible to make a plugin based on the XML Navigator View to export a different XML. Once we implement JRA-12062, it should be possible to then extend the plugin to ask the user which transform to apply. I am not sure if we will add the ability to plugin transforms to the default Issue Navigator XML view. I would prefer to keep that view simple. Will the addition of JRA-12062 solve most of your needs? I will leave this issue open to see how many other users are interested in this. Please note, however, that while we would really like to address all improvements in JIRA, we do have thousands of feature and improvement requests, and we cannot address them all. For more information on the way new features and improbvements are scheduled please see: Thanks again for your feedback! Cheers, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Allow Pluggable XSLT support in XML Export
This is a interesting idea.
Is the main motivation behind this feature, to be able to select which Issue Fields should be shown?
We are hoping to implement JRA-12062 in the future, and allow users to select which fields should be shown. If we do this, do you think the need to plug XSLT will be reduced?
Cheers,
Anton