<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.2.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>

<channel>
	<title>onresolve team blog</title>
	<link>http://blogs.onresolve.com</link>
	<description></description>
	<pubDate>Tue, 11 May 2010 10:59:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2.2</generator>
	<language>en</language>
			<item>
		<title>Setting issue security level by issue type</title>
		<link>http://blogs.onresolve.com/?p=140</link>
		<comments>http://blogs.onresolve.com/?p=140#comments</comments>
		<pubDate>Tue, 11 May 2010 10:59:11 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=140</guid>
		<description><![CDATA[This is an old entry - re-added because of a problem with redirects, sorry.
It&#8217;s not possible in JIRA to create an Issue Security Scheme by issue type. For instance, you may want that defects should default to Private, and enhancements should default to public (or none). You might expect that issue type security scheme would [...]]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=140</wfw:commentRss>
		</item>
		<item>
		<title>JIRA SQL Plugin</title>
		<link>http://blogs.onresolve.com/?p=134</link>
		<comments>http://blogs.onresolve.com/?p=134#comments</comments>
		<pubDate>Tue, 27 Apr 2010 11:34:47 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=134</guid>
		<description><![CDATA[The SQL Plugin lets users run SQL predefined queries against the JIRA database, the results are rendered using velocity templates customised by an administrator.
The same template can be used as a portlet/gadget or a report, although generally additional information will be shown in the report, for instance the data table driving the chart. 

]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=134</wfw:commentRss>
		</item>
		<item>
		<title>Using Properties in JIRA</title>
		<link>http://blogs.onresolve.com/?p=126</link>
		<comments>http://blogs.onresolve.com/?p=126#comments</comments>
		<pubDate>Sun, 18 Apr 2010 11:16:11 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=126</guid>
		<description><![CDATA[Introducing an utterly unglamourous plugin - the &#34;Properties Manager&#34;. This allows you to browse and edit the propertyset on most jira &#34;entities&#34;. Depending on the amount of additional work you are willing to put in, this could be a partial solution to JRA-1991 and JRA-2980. 
It&#39;s probably best to describe this by way of a [...]]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=126</wfw:commentRss>
		</item>
		<item>
		<title>Auto duplicate search in JIRA</title>
		<link>http://blogs.onresolve.com/?p=123</link>
		<comments>http://blogs.onresolve.com/?p=123#comments</comments>
		<pubDate>Tue, 30 Mar 2010 08:57:39 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=123</guid>
		<description><![CDATA[A requirement came up recently that the user should be encouraged (forced) to search for a matching existing issue before submitting a new one. This particular group spent a lot of time &#8220;deduping&#8221;, and it turns out that around 80% of their issues were closed as duplicates.
The solution outlined below, does a search for possible [...]]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=123</wfw:commentRss>
		</item>
		<item>
		<title>Script Runner JIRA Plugin</title>
		<link>http://blogs.onresolve.com/?p=122</link>
		<comments>http://blogs.onresolve.com/?p=122#comments</comments>
		<pubDate>Mon, 29 Mar 2010 12:40:41 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[Groovy]]></category>

		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=122</guid>
		<description><![CDATA[For a long time I&#8217;ve been meaning to rewrite the &#8220;groovy runner&#8221; plugin so that groovy wasn&#8217;t a requirement, and having found myself with some unexpected but welcome time on my hands I have finally done so.
]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=122</wfw:commentRss>
		</item>
		<item>
		<title>What&#8217;s Wrong with ClearQuest II</title>
		<link>http://blogs.onresolve.com/?p=121</link>
		<comments>http://blogs.onresolve.com/?p=121#comments</comments>
		<pubDate>Wed, 20 Jan 2010 22:09:20 +0000</pubDate>
		<dc:creator>Trent Nelson</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=121</guid>
		<description><![CDATA[My long-term business partner, Trent, told me the other week he was going to write a rebuttal to my previous rant, &#8220;What&#8217;s wrong with ClearQuest&#8220;, called &#8220;What&#8217;s getting slightly better about ClearQuest&#8221;. I think he&#8217;s struggling to fill a few paragraphs though, because it hasn&#8217;t been forthcoming.
He recently wrote a reply on the forum that [...]]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=121</wfw:commentRss>
		</item>
		<item>
		<title>Highlight Overdue Issues</title>
		<link>http://blogs.onresolve.com/?p=111</link>
		<comments>http://blogs.onresolve.com/?p=111#comments</comments>
		<pubDate>Fri, 20 Nov 2009 07:05:39 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=111</guid>
		<description><![CDATA[Here is a relatively simple way to highlight overdue issues&#8230; the more overdue they are, the hotter the colour:


]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=111</wfw:commentRss>
		</item>
		<item>
		<title>JIRA 4.0 Beta Test Drive</title>
		<link>http://blogs.onresolve.com/?p=106</link>
		<comments>http://blogs.onresolve.com/?p=106#comments</comments>
		<pubDate>Wed, 03 Jun 2009 15:52:34 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=106</guid>
		<description><![CDATA[I was keen to get my grubby mitts on the JIRA 4.0 beta to see what JQL (jira query language) was all about&#8230; this is my first test-drive, I haven&#39;t read much of the release notes or the bug reports, so I&#39;m probably way off on some of this.

]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=106</wfw:commentRss>
		</item>
		<item>
		<title>How to Make JIRA Twelve Times Faster</title>
		<link>http://blogs.onresolve.com/?p=102</link>
		<comments>http://blogs.onresolve.com/?p=102#comments</comments>
		<pubDate>Tue, 14 Apr 2009 17:56:57 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=102</guid>
		<description><![CDATA[As an addendum to the previous post, I&#39;ve done some more cleaning up, and JIRA is now 12 times faster on the average measurement.


		

Label
# Samples
Average
Min
Max


Login
3
18
13
29


LoginFBrowse
10
41
10
184


Get issue
903
590
21
7792


Dashboard
9
14836
10006
18698


LazyLoaderPortlet
9
632
298
1091


CreateIssue Link
9
367
165
634


Create Choose type
9
289
141
677


Issue Details
9
2195
1269
3521


TOTAL
961
727
10
18698


]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=102</wfw:commentRss>
		</item>
		<item>
		<title>How to make JIRA 6 1/2 times faster</title>
		<link>http://blogs.onresolve.com/?p=95</link>
		<comments>http://blogs.onresolve.com/?p=95#comments</comments>
		<pubDate>Wed, 01 Apr 2009 14:44:01 +0000</pubDate>
		<dc:creator>Jamie Echlin</dc:creator>
		
		<category><![CDATA[JIRA]]></category>

		<guid isPermaLink="false">http://blogs.onresolve.com/?p=95</guid>
		<description><![CDATA[Over the last few months JIRA performance has tanked, but gradually. Difficult to think of any particular inflexion point, just more users, projects and issues.
I had a number of changes I had in mind to help:

Application server
DBMS type and location
Caching for static content
Reducing numbers of projects, groups etc.
Optimising indexes.
Turn gzip compression on.
Memory and garbage collector [...]]]></description>
		<wfw:commentRss>http://blogs.onresolve.com/?feed=rss2&amp;p=95</wfw:commentRss>
		</item>
	</channel>
</rss>

; Maximum allowed size for uploaded files.
upload_max_filesize = 100M