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

How do you simplify your boilerplate Groovy code?

Anton Chemlev - Toolstrek -
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2019

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
TAGS
AUG Leaders

Atlassian Community Events