<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/" version="2.0">
  <channel>
    <title>IdeaScale : Allow idea integration from 3rd party case tracking systems</title>
    <description />
    <item>
      <title>Allow idea integration from 3rd party case tracking systems</title>
      <link>http://questionpro.ideascale.com/akira/dtd/49-393</link>
      <description>&lt;table width="100%"&gt;
&lt;tr&gt;&lt;td width="100" valign="top"&gt;
&lt;div id="IdeaScale_Vote" align="center"&gt;&lt;div style="padding:5px;font-size:2em"&gt;6&lt;/div&gt;&lt;div&gt;&lt;a href="http://questionpro.ideascale.com/akira/dtd/49-393"&gt;Vote&amp;nbsp;On&amp;nbsp;Idea&lt;/a&gt;&lt;/div&gt;&lt;/div&gt;
&lt;/td&gt;&lt;td valign="top"&gt;
&lt;div&gt;Its common for companies to track new features in existing case tracking tools like Agility, Jira, Trac or others.  Most of these have an API into them.&lt;br/&gt;&lt;br/&gt;It would be nice to be able to integrate a ideascale instance into an exising case tool such that all the cases are still stored in only one location but the idea scale system manages the voting and commenting.
&lt;/div&gt;&lt;div id="IdeaScale_IdeaFooter"&gt;&lt;span style="border-right: 1px solid silver; margin:0 10px 0 0; padding: 0 5px 0 0; color: #666;"&gt;&lt;a id="DiscussionTopic_49" href="http://questionpro.ideascale.com/akira/dtd/49-393"&gt;Comments (2)&lt;/a&gt;&lt;/span&gt;&lt;span id="DiscussionTopicTag_49"&gt;Category/Tags : &lt;a href="/akira/ideafactory.do?discussionID=97"&gt;IdeaScale (25)&lt;/a&gt;&amp;nbsp;&lt;/span&gt;&lt;span style="border-left: 1px solid silver; margin:0 10px 0 0; padding: 0 5px 0 0; color: #666;"&gt;&amp;nbsp;&amp;nbsp;  Mark as &lt;a href="javascript:ajaxLink('DiscussionTopicFlag_49', '/akira/flagDiscussionTopic.do?mode=duplicate&amp;discussionID=97&amp;ID=49')"&gt;duplicate&lt;/a&gt;&lt;/span&gt;&lt;div style="margin-top:3px;" id="DiscussionTopicFlag_49"&gt;&lt;/div&gt;&lt;div style="margin-top:3px;" id="DiscussionTopicComment_49"&gt;&lt;/div&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</description>
      <pubDate>Wed, 09 Apr 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://questionpro.ideascale.com/akira/dtd/49-393</guid>
    </item>
    <item>
      <title>Comment by vivek.bhaskaran</title>
      <link>http://questionpro.ideascale.com/akira/dtd/49-393</link>
      <description>This is going to be really tricky and the number of bug/issue tracking systems out there are too many for us to integrate with each and every one of them.</description>
      <pubDate>Sun, 13 Apr 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://questionpro.ideascale.com/akira/dtd/49-393</guid>
    </item>
    <item>
      <title>Comment by roberts</title>
      <link>http://questionpro.ideascale.com/akira/dtd/49-393</link>
      <description>Well, how about creating an API set that the external system can call to bring the IdeaScale info onto the glass there and just receive rating info back.  Most likely people will use both your API and the bug/issue tracking API to create a mash up application where they can do things that neither application had considered.&lt;br/&gt;&lt;br/&gt;It seems to me that IdeaScale can be successful on the low end of the market without an API, but to make enterprise sales, most people are going to need some sort of API to truly do great/customized things with it.  Assuming it is architected well, it should not be hard to build a library of customer ready web services.</description>
      <pubDate>Mon, 16 Jun 2008 00:00:00 PDT</pubDate>
      <guid isPermaLink="true">http://questionpro.ideascale.com/akira/dtd/49-393</guid>
    </item>
  </channel>
</rss>

