Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,364,818
Community Members
 
Community Events
168
Community Groups

How do you simplify your boilerplate Groovy code?

Hi!

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

@Category(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) {
customerRequestTypeCF.customFieldType.getDisplayedValue(internalCustomerRequestName)?.name
} else {
null
}
} 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) {
issue.customerRequestName
}

Voila!

Could you please share your experience?

0 comments

Comment

Log in or Sign up to comment