How to calculate “Lead Time” or “Real Average Resolution Days” with EazyBI and JIRA

The default calculated measure of EazyBI “Average Resolution Days” counts until the last Resolution filled ( not until the first value of the Resolution field), then if you set a new Resolution from “Resolved” to “Close” statuses, the value will be measured until “Close”. EazyBI counts the resolution time till the last resolution. This is…

Read More

Two tricks to improve the performance and security of your Jira Server 7.4

There are two tricks to improve the performance and the security of a large Jira Server 7.4 For the first “trick“, we can develop a little Jira plugin, or we can set a “Script Fragment” with the plugin Adaptavist Groovy Scriptrunner. The purpose of the improvement is to avoid problematic JQL queries. In Jira, by default,…

Read More

Atlassian Crowd LDAP problems and downtimes?… see this post

After the upgrading of Crowd, our servers experimented a new problem… sometimes Crowd becomes “stuck” (also JIRA & Confluence because the SSO) and the log of Crowd show errors in the LDAP connection… but not always… two times a week.. etc. Examples of errors in the log: Caused by: com.atlassian.crowd.exception.OperationFailedException: org.springframework.ldap.PartialResultException: nested exception is javax.naming.PartialResultException…

Read More

Is a regular JIRA restart important? TRICK TO SOLVE THE PERFORMANCE DEGRADATION IN JIRA 6.3

Do you restart JIRA e.g. once a week? Is it recomended in order to speed it up? Some users using JIRA very intensively are requesting this, realising that the system is slowing down after a certain time…. VERSION: JIRA 6.3 TRICK 1: The performance increases dramatically if you use Java8 instead of Java7!!  SEE MORE: https://confluence.atlassian.com/display/JIRAKB/Java+8+Improves+JIRA+Performance+Dramatically…

Read More