forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Scherler (JIRA)" <j...@apache.org>
Subject [jira] Commented: (FOR-972) Export Jira Issues as they are resolved/closed so they can be imported into status.xml
Date Thu, 29 Mar 2007 08:27:25 GMT

    [ https://issues.apache.org/jira/browse/FOR-972?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12485106
] 

Thorsten Scherler commented on FOR-972:
---------------------------------------

I am not sure but have a look at https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-xml/temp/SearchRequest.xml?&pid=12310000&fixfor=12310040&sorter/field=issuekey&sorter/order=DESC
See the source code and find that all information are there.
<item>
  <title>[FOR-959] HowTo sample </title>
  <link>https://issues.apache.org:443/jira/browse/FOR-959</link>
  
  <description>It would be useful to have a HowTo sample document in the
    src/documentation/content/xdocs/samples folder when a user seeds a new project with
    &apos;forrest seed&apos;. There is an excellent HowTo-HowTo document in the Forrest
svn
    repository at /site-author/content/xdocs/howto-howto.xml that perhaps could serve
    this function. This document may need to have a few changes made to serve as a sample:
it has 3
    &apos;site:&apos; links in it that are, I think, specific to the Forrest project,
but
    which could be replaced with full url links.</description>
  
  <environment></environment>
  <key id="12364016">FOR-959</key>
  <summary>HowTo sample </summary>
  <type id="4">Improvement</type>
  
  <priority id="4">Minor</priority>
  <status id="6">Closed</status>
  <resolution id="1">Fixed</resolution>
  
  <assignee username="rgardler">Ross Gardler</assignee>
  
  <reporter username="randym">Randy Metcalfe</reporter>
  
  <created>Sat, 3 Mar 2007 01:18:15 -0800 (PST)</created>
  <updated>Wed, 14 Mar 2007 18:11:25 -0700 (PDT)</updated>
  
  <version>0.8-dev</version>
  
  <fixVersion>0.8-dev</fixVersion>
  
  <component>Documentation and website</component>
  
  <votes>0</votes>
  
  <comments>
    <comment author="rgardler" created="Wed, 14 Mar 2007 18:11:25 -0700 (PDT)">
      Copied howto-howto into fresh-site samples.
      &lt;br/&gt;
      &lt;br/&gt; Removed site: links rather than replacing with hard coded URLs that
may
      create a maintenance problem. It still serves the purpose of being an
      example.</comment>
  </comments>
  
  <attachments>
  </attachments>
  
  <subtasks>
  </subtasks>
  
  <customfields>
  </customfields>
  
</item>

So jira already does what you describe, or?

> Export Jira Issues as they are resolved/closed so they can be imported into status.xml
> --------------------------------------------------------------------------------------
>
>                 Key: FOR-972
>                 URL: https://issues.apache.org/jira/browse/FOR-972
>             Project: Forrest
>          Issue Type: New Feature
>          Components: Other
>    Affects Versions: 0.8-dev
>            Reporter: Gavin
>            Priority: Minor
>             Fix For: 0.9
>
>
> Jira can be configured to export XML backups/files and can be further filtered.
> I would like Jira to export automatically a Jira Issue as it is closed/resolved.
> The exported data would be filtered further to only contain relevent fields.
> This XML file can then be used/imported or transformed with XSLT to automagically
> add an entry into status.xml.
> Somebody with Jira Admin status of Forrest needs to check if XML Export is enabled
> and possibly go further and log an Issue with Infra > Jira to get the appropriate
> export enabled.
> I'm on Atlassian Jira Mail List so I know it is possible (The filtered export part I
mean)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message