Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do you simplify your boilerplate Groovy code?


It is interesting - how do you get rid of long and verbose Jira Java API calls using Groovy tricks?

As for me, i've found rather elegant way (besides making regular helper classes) to use Groovy categories. Let's pretend we want to get readable customer request type name for issue.

Step 1:

package com.funlabs.category

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue

class ServiceDeskCategory {
String getCustomerRequestName() {
def customerRequestTypeCF = ComponentAccessor.customFieldManager.customFieldObjects.find { cf ->
cf.untranslatedName == 'Customer Request Type' && cf.customFieldType.key == 'com.atlassian.servicedesk:vp-origin'
if (customerRequestTypeCF) {
def internalCustomerRequestName = this.getCustomFieldValue(customerRequestTypeCF)
if (internalCustomerRequestName) {
} else {
} else {
throw new IllegalStateException('Can\'t find internal Customer Request Type customfield')

Step 2:

package com.funlabs

import com.atlassian.jira.component.ComponentAccessor
import com.funlabs.category.ServiceDeskCategory

def issue = ComponentAccessor.issueManager.getIssueObject('TEST-38')
use(ServiceDeskCategory) {


Could you please share your experience?



Log in or Sign up to comment

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you