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

Permissions based on Workflow Status in JIRA

In the Workflow transition properties you can set diverse permissions restrictions like this: jira.permission.comment.group=group jira.permission.comment.denied=true/false jira.permission.edit.group.1=group1 jira.permission.edit.group.2=group2 jira.permission.modifyreporter.user=username jira.permission.delete.projectrole=10000 jira.permission.subtasks.delete.projectrole=10000 jira.permission.close.user=username jira.issue.editable=false … You can see more permissions and terminology in this link  

Read More

JIRA JQL trick: Filter issues based on transition state execution date in JIRA

Very easy, see the JQL example: Project = “JIRA” AND Status CHANGED TO “In Progress” DURING (“2015/08/01″,”2015/10/05”) Other Syntax: This JQL shows all issues which have been in “Status A” for more than 14 days project=XXX and status changed to “Status A” before startofday(-14) and status = “Status A” This JQL shows all issues which…

Read More

Workflow properties

jira.field.resolution.exclude Resolution id Add comma-separated resolution ids to the transition properties where you want to not show certain resolutions jira.field.resolution.include Resolution id Add comma-separated resolution ids to the transition properties jira.i18n.submit i18n property key Transition (usage: action submit button name) jira.i18n.title i18n property key Transition (usage: action name, etc.) jira.issue.editable true, false Configuring Workflow Step jira.permission.*…

Read More