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.
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 “deduping”, and it turns out that around 80% of their issues were closed as duplicates.
The solution outlined below, does a search for possible duplicates after the summary field loses focus. The results of the search can either be displayed below the summary, or for a more in-your-face experience, in an overlay.
At this stage the user can click the possible dupes which will open the issues in a new tab. Then they either abandon or creating a new issue, or if none of them are a match they can proceed.
My long-term business partner, Trent, told me the other week he was going to write a rebuttal to my previous rant, “What’s wrong with ClearQuest“, called “What’s getting slightly better about ClearQuest”. I think he’s struggling to fill a few paragraphs though, because it hasn’t been forthcoming.
He recently wrote a reply on the forum that the admins must have deleted, completely lacking a sense of humour as they do. Anyway, it’s worth blogerising for posterity.
i am a fresher to clearquest.i am still in learning phase of it.i will be very thankful to you if some of you can give me some information on clearquest scope for career growth
In my neck of the woods you’re more typically seeing $35.00/hr for a contract position for ClearQuest admin.
Trent responded with the following:
$35/hr? To work on ClearQuest? No thanks, I’d rather stay home and pull teeth.
I won’t get out of bed these days for anything less than £100/hr if I have to do ClearQuest work. And I increase my minimum hourly rate annually at about 5 times the rate of inflation. You can be horrendously incompetent in London and still fetch £450-600/day, depending on whether your client has any idea about ClearQuest. (The hidden subtext here is that you can make a lot of money claiming to specialise in ClearQuest, and as long as no-one else in the company knows any better, get away with it even if you know diddley-squat.)
Here is a relatively simple way to highlight overdue issues… the more overdue they are, the hotter the colour:
As an addendum to the previous post, I'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 |
I’ve refreshed the workflow plugin a bit. If you want jump straight to the installation section.
A problem I’ve noticed with the workflows people create (not my own ones of course!) is that the resolution is often inconsistent.
This might stem from a lack of understanding of the resolution field and what it’s used for. In the default workflow, there is a state called Resolved, and when you get to that state the resolution must be set, and if you reopen the issue it’s unset, so people tend to think it happens by magic. It doesn’t, that’s the way the default workflow has been written, and there is no relationship between workflow states and the resolution, unless you define one. Continue reading ‘Jira Workflow Report Update’
This simple plugin allows you to run Groovy scripts in the context of confluence. Groovy scripts have full access to the API.
This is in the same spirit as the Jira groovy runner, that is, it lets you quickly develop proofs of concepts and simple macros, without having to worry about all the boilerplate of a Confluence plugin, and the agonisingly slow edit-debug-deploy cycle (even with JavaRebel). Developing should be as simple as adding your macro, saving the page, make changes to your groovy script, then reload the page.
If you use IDEA (probably true of Eclipse too) you can attach the debugger, and break in to your groovy scripts.
Example page output from running the three supplied scripts:
I set up Confluence to integrate with our LDAP infrastructure, to take advantage of protecting spaces with LDAP groups. We had performance issues but I increased the cache timeout in the confluence-coherence-cache-config.xml properties file as documented here.
I then thought everything was well as performance seemed “OK”, however reports of poor performance, like 15-25 seconds to get the dashboard page, started to trickle through to me. It turned out I had been in a fool’s paradise, as if you are in the confluence-administrators group all the permissions checks are bypassed.
Continue reading ‘Synchronising LDAP Groups with Confluence Groups’
Someone recently asked me if the release notes in JIRA could contain the files that have changed to fix that issue. Perfectly reasonable. However, the changelists (the $client uses Perforce) that fix the issue are not held in JIRA, instead, the plugin runs some p4 commands to get the changelists, and in turn each delta that is part of that changelist. It also does some nice stuff such as turning it in to link to p4web so you can click through to see the diffs. I considered re-using the code from the Perforce plugin, but…
I’m not a big fan of the release notes feature in jira. It’s too restrictive, although you can add templates for release notes, they’re available to everyone, and then they can’t be configured further, much. Everyone wants a different format, with different custom fields and so on. At the least the release note feature should support standard features of the query navigator. The feature of copying the HTML is a bit gimmicky IMHO.
You are currently browsing the onresolve team blog weblog archives for the Uncategorized category.
