This is an old entry - re-added because of a problem with redirects, sorry.
It’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 be a mapping of issue types to issue security schemes (in the same way as Field Configuration Schemes), but unfortunately not.
There are two ways to get round this, one using Javascript, one with a post-function.
Continue reading ‘Setting issue security level by issue type’
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.
Continue reading ‘JIRA SQL Plugin’
Introducing an utterly unglamourous plugin - the "Properties Manager". This allows you to browse and edit the propertyset on most jira "entities". 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's probably best to describe this by way of a few examples. Say you wanted to assign a cost centre to each project. Using this plugin you could export the list of projects, then add the cost center column, then import. Why is this useful? You could then display it on a custom field for each issue in this project (when the custom field is available), or query for all projects with this cost centre (when the searcher is available).
Continue reading ‘Using Properties in JIRA’
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.
Continue reading ‘Auto duplicate search in JIRA’
For a long time I’ve been meaning to rewrite the “groovy runner” plugin so that groovy wasn’t a requirement, and having found myself with some unexpected but welcome time on my hands I have finally done so.
Continue reading ‘Script Runner JIRA Plugin’
Here is a relatively simple way to highlight overdue issues… the more overdue they are, the hotter the colour:
Continue reading ‘Highlight Overdue Issues’
I was keen to get my grubby mitts on the JIRA 4.0 beta to see what JQL (jira query language) was all about… this is my first test-drive, I haven't read much of the release notes or the bug reports, so I'm probably way off on some of this.
Continue reading ‘JIRA 4.0 Beta Test Drive’
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 |
Continue reading ‘How to Make JIRA Twelve Times Faster’
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 settings.
- Bypassing the apache reverse proxy and going direct to Tomcat
- Use AJP13 connector instead of (as well as?) ProxyPass.
BTW, if you're looking for the instruction on where the "go-faster switch" is and can't be bothered to read the following, I'll tell you simply that you should replace the group jira-users in your roles or permission schemes with Anyone. If you're not using that then hopefully there will be something else of interest here, if only how to set up a simple load test to get some figures.
For the record our numbers at the time of testing are:
Issues 112897 Projects 475 Custom Fields 505 Workflows 239 Users 7613 Groups 698
Continue reading ‘How to make JIRA 6 1/2 times faster’
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’