<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Fri, 24 May 2013 23:24:11 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Lorna Mitchell's Blog: Using JIRA's REST API to Create a Dashboard]]></title>
      <guid>http://www.phpdeveloper.org/news/17743</guid>
      <link>http://www.phpdeveloper.org/news/17743</link>
      <description><![CDATA[<p>
In <a href="http://www.lornajane.net/posts/2012/using-jiras-rest-api-to-create-a-dashboard">this recent post</a> to her blog, <i>Lorna Mitchell</i> shows how to use the Jira REST API (provided as a part of some of the newer versions of the tool) to create a "dashboard" of the latest items added to the tracker.
</p>
<blockquote>
Today what you get is an example of integrating with JIRA's REST API, because their recent "upgrade" locked me out of the issue listings pages completely and I really do need to be able to see a list of bugs! Their bug editing screen is quite usable, so it's just the list that I need here, but you could easily call their <a href="http://docs.atlassian.com/jira/REST/latest/">other API methods</a> as you need to. These examples are PHP and use the <a href="http://pecl.php.net/pecl_http>PECL_HTTP</a> extension, because it's awesome, but these examples could be easily adapted to use another language or library.
</blockquote>
<p>
She includes an example of the REST-based URL to fetch the issues (based on the <a href="http://joindin.jira.com">Joind.in Jira tracker</a>), parsing the JSON results and displaying the results as a simple list, looping with a foreach and outputting some HTML.
</p>]]></description>
      <pubDate>Wed, 28 Mar 2012 10:57:56 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Zend Developer Zone: Announcing July's Zend Framework Bug Hunt Days]]></title>
      <guid>http://www.phpdeveloper.org/news/16641</guid>
      <link>http://www.phpdeveloper.org/news/16641</link>
      <description><![CDATA[<p>
On the Zend Developer Zone, <i>Matthew Weier O'Phinney</i> has posted a notice about this month's <a href=http://devzone.zend.com/article/16578-Announcing-Julys-Zend-Framework-Bug-Hunt-Days">Bug Hunt Days</a> for the Zend Framework. This month they'll be held July 28th through the 30th.
</p>
<blockquote>
For those who haven't put the recurring event in their calendar, the Zend Framework Monthly Bug-hunt is here again! This Thursday, Friday and Saturday (the 28th, 29th and 30th of July), we'll be hosting our monthly bug hunt. For those of you unfamiliar with the event, each month, we organize the community to help reduce the number of open issues reported against the framework.
</blockquote>
<p>
He reminds those wanting to participate of a few pieces of information - that they'll <a href="http://framework.zend.com/cla">need a CLA on file</a>, where to find <a href="http://framework.zend.com/issues/secure/IssueNavigator.jspa?requestId=11385&sorter/field=issuekey&sorter/order=ASC">unresolved issues</a>, getting help on the <a href="http://zftalk.com/">zftalk.dev IRC channel</a> and a <a href="http://framework.zend.com/wiki/display/ZFDEV/Monthly+Bug+Hunt+Days">getting started guide</a> for those first-timers.
</p>]]></description>
      <pubDate>Wed, 27 Jul 2011 11:13:44 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Lorna Mitchell's Blog: Github to Jira Bug Migration Script]]></title>
      <guid>http://www.phpdeveloper.org/news/16019</guid>
      <link>http://www.phpdeveloper.org/news/16019</link>
      <description><![CDATA[<p>
As part of a migration the <a href="http://github.com/joindin/joind.in">Joind.in project</a> made to track their bugs on a hosted Jira instance instead of the Issue Tracker on Github, <i>Lorna Mitchell</i>, one of the leads on the project has written up an import script she used to move current issues. The code is <a href="http://www.lornajane.net/posts/2011/Github-To-Jira-Bug-Migration-Script">in her latest post</a>.
</p>
<blockquote>
I migrated only our open issues, and comments (and the comments ended up a bit weirdly formatted on the other end but this was the best they could do). It was nothing pretty or clever but in case it's useful to someone else.
</blockquote>
<p>
The script connects to the github API and pulls down the information for the open issues including their titles, user and body of the issue. This is then used to make another connection for each to fetch their comments. The whole thing is dumped out to a CSV file that can be easily imported by the Jira team.
</p>]]></description>
      <pubDate>Wed, 09 Mar 2011 10:18:18 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Jim Plush's Blog: How to Auto Create Issues in Jira From PHP]]></title>
      <guid>http://www.phpdeveloper.org/news/15863</guid>
      <link>http://www.phpdeveloper.org/news/15863</link>
      <description><![CDATA[<p>
<i>Jim Plush</i> has a new post to his blog today that points out a bit of code you can use to <a href="http://jimplush.com/blog/article/176/How-to-Auto-Create-Issues-in-Jira-From-PHP">auto-create issues in Jira</a> from your PHP application.
</p>
<blockquote>
We use Jira at Gravity for tracking issues and bugs. Since I'm not always on VPN or have access to our network managing my todos has been cumbersome. I've tried every Todo app out there and always fail to use them for more than 2 days. I finally saw a great article on just using a simple Todo.txt file in your Dropbox folder and working from that. It's been a dream and working out great. 
</blockquote>
<p>
His tool lets him use the Todo list example to push its contents out to the PHP script that connects to the Jira instance and make a new issue. The code is included <a href="http://jimplush.com/blog/article/176/How-to-Auto-Create-Issues-in-Jira-From-PHP">in the post</a>, ready for cut-and-pasting.
</p>]]></description>
      <pubDate>Mon, 07 Feb 2011 08:06:52 -0600</pubDate>
    </item>
  </channel>
</rss>
