<?xml version="1.0" encoding='utf-8'?>
<!-- 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153
-->
<?xml-stylesheet type="text/xsl" href="https://rollerweblogger.org/roller-ui/styles/atom.xsl" media="screen"?><feed xmlns="http://www.w3.org/2005/Atom">
    <title type="html">Blogging Roller</title>
    <subtitle type="html">Dave Johnson on open web technologies, social software and software development</subtitle>
    <id>https://rollerweblogger.org/roller/feed/entries/atom</id>
        <link rel="self" type="application/atom+xml" href="https://rollerweblogger.org/roller/feed/entries/atom?tags=jira" />
    <link rel="alternate" type="text/html" href="https://rollerweblogger.org/roller/" />
    <updated>2026-05-18T08:23:39+00:00</updated>
    <generator uri="http://roller.apache.org" version="6.1.5">Apache Roller</generator>
    <entry>
        <id>https://rollerweblogger.org/roller/entry/jira_finally_gets_its_own</id>
        <title type="html">JIRA finally gets its own REST API</title>
        <author><name>Dave Johnson</name></author>
        <link rel="alternate" type="text/html" href="https://rollerweblogger.org/roller/entry/jira_finally_gets_its_own"/>
        <published>2012-03-01T09:20:30+00:00</published>
        <updated>2014-01-20T03:14:55+00:00</updated> 
        <category term="Web Development" label="Web Development" />
        <category term="jira" scheme="http://roller.apache.org/ns/tags/" />
        <category term="json" scheme="http://roller.apache.org/ns/tags/" />
        <category term="oslc" scheme="http://roller.apache.org/ns/tags/" />
        <category term="rest" scheme="http://roller.apache.org/ns/tags/" />
        <content type="html">&lt;p&gt;JIRA&amp;#39;s got a real REST API now:&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;REST easy with JIRA 5 | Atlassian Blogs: Now that JIRA 5 is out, let&#146;s talk about one of my favorite features of this new release, JIRA&#146;s new REST API. JIRA has supported remote APIs for many years with SOAP, XML-RPC, and JSON-RPC. However, telling developers that you support SOAP (and only SOAP) is like saying that you like writing applications with COBOL &#151; it&#146;s out of style. Today&#146;s cool kids gravitate towards REST. It&#146;s clean, simple, and highly portable across languages and frameworks.&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;And checkout the &lt;a href=&quot;http://docs.atlassian.com/jira/REST/latest/&quot;&gt;nice looking API docs&lt;/a&gt;, which look like they were generated by &lt;a href=&quot;https://github.com/mnot/wadl_stylesheets/&quot;&gt;WADL-to-HTML&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;An alternative to Atlassian&amp;#39;s new API is the recently release &lt;a href=&quot;https://plugins.atlassian.com/plugins/Rational_OSLC_Adapter_for_JIRA.jar&quot;&gt;Rational OSLC Adapter for JIRA&lt;/a&gt;, which allows you to do more sophisticated integrations with JIRA including delegated UIs for issue creation and selection.&lt;/p&gt;</content>
    </entry>
    <entry>
        <id>https://rollerweblogger.org/roller/entry/jra_19796_rest_api_for</id>
        <title type="html">[#JRA-19796] REST API for JIRA</title>
        <author><name>Dave Johnson</name></author>
        <link rel="alternate" type="text/html" href="https://rollerweblogger.org/roller/entry/jra_19796_rest_api_for"/>
        <published>2010-05-11T18:20:48+00:00</published>
        <updated>2010-07-10T17:08:52+00:00</updated> 
        <category term="IBM" label="IBM" />
        <category term="atlassian" scheme="http://roller.apache.org/ns/tags/" />
        <category term="jira" scheme="http://roller.apache.org/ns/tags/" />
        <category term="oslc" scheme="http://roller.apache.org/ns/tags/" />
        <content type="html">&lt;img src=&quot;http://rollerweblogger.org/roller/mediaresource/04fe2c5b-9719-4e13-9221-70a0645b48e0&quot; alt=&quot;oslc logo&quot; style=&quot;float:right;&quot;&gt;

&lt;p&gt;It&amp;#39;s kind of surprising to me that &lt;a href=&quot;http://www.atlassian.com/software/jira/&quot;&gt;JIRA&lt;/a&gt; does not have a &amp;quot;REST API.&amp;quot; Looking on the bright side, this may be an opportunity for &lt;a href=&quot;http://open-services.net/&quot;&gt;Open Services for Lifecycle Collaboration (OSLC)&lt;/a&gt; to show its value, so back in March I made a little pitch in the appropriate JIRA issue:&lt;/p&gt; 

&lt;blockquote&gt;
&lt;p&gt;&lt;a href=&quot;http://jira.atlassian.com/browse/JRA-19796&quot;&gt;JIRA-19796 - REST API for JIRA&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Dave Johnson added a comment  - 10/Mar/10 9:24 AM - edited&lt;/p&gt;
&lt;p&gt;You should consider making the JIRA REST API conformant with the Open Services for Lifecycle Collaboration (OSLC) interface for Change Management (OSLC-CM). This would allow JIRA to integrate with ALM tools from IBM, Oracle, Rally, SourceGear, etc. The Mylyn folks are already involved. Here&amp;#39;s the link to the OSLC-CM home page: &lt;a href=&quot;http://open-services.net/bin/view/Main/CmHome&quot;&gt;http://open-services.net/bin/view/Main/CmHome&lt;/a&gt;. OSLC-CM v1 is the current spec and work on v2 is underway. It&amp;#39;s an open effort and we&amp;#39;d love JIRA and/or JIRA users to join in and help us define v2.&lt;/p&gt;
&lt;/blockquote&gt;
</content>
    </entry>
</feed>

