tips

def screen = ComponentAccessor.getIssueTypeScreenSchemeManager().getFieldScreenScheme(issue).getFieldScreenSchemeItem(IssueOperations.EDIT_ISSUE_OPERATION )

if (screen.getId().toString() in ["18100", "19920", "19925"]) {

getFieldById("customfield_21952").setHidden(true)//Custom Field

}

Update date time field

import com.atlassian.jira.issue.ModifiedValue

import com.atlassian.jira.issue.util.DefaultIssueChangeHolder

currField.updateValue(null, issue, new ModifiedValue("", (Object) date.toTimestamp()), new DefaultIssueChangeHolder())

Get all methods for a class:

import com.onresolve.scriptrunner.canned.jira.utils.CannedScriptUtils

/**

* @function printAllMethods

* @purpose Prints an objects class name and then list the associated class functions.

// Filename: printAllMethodsExample.groovy

void printAllMethods( obj ){

if( !obj ){

log.error( "Object is null\r\n" );

return;

}

if( !obj.metaClass && obj.getClass() ){

printAllMethods( obj.getClass() );

return;

}

def str = "class ${obj.getClass().name} functions:\r\n";

obj.metaClass.methods.name.unique().each{

str += it+"(); ";

}

log.error "${str}\r\n";

}

//def priorities = CannedScriptUtils.getPriorityOptions(true)

printAllMethods(CannedScriptUtils)

Fragment:

"HOW TO HIDE THE CREATE SUB-TASK FROM MORE WORKFLOW BUTTON AT PARTICULAR STATUS IN JIRA TICKET" . To execute this need "Script Runner" Add-On.

so GoTo--->Admin Settings--->Add-On's--->Left Pannel List Script Runner--->Select Script Fragements--->Add New Item and Select 'Hide system or plugin UI element ' -----> In that in Hide What option select the "com.atlassian.jira.plugin.system.issueoperations:create-subtask" ------> In Condition run this script given below

def currentStatus = issue.status.name

!(currentStatus == "Done") // instead of 'Done' put your status in which status you want to hide the Create Sub-Task

Drop all attachments in the Issue
List AttachmentI = attachmentManager.getAttachments(issue)

AttachmentI.each {attachment ->

attachmentManager.deleteAttachment(attachment)

}

Re-Index
MutableIssue newIssue = issueFactory.getIssue()

newIssue.setProjectObject(targetProjectObject)

newIssue.setIssueTypeObject(subTaskIssueType)

newIssue.setReporter(reporter)

newIssue.setSummary(summary)

newIssue.setPriorityId(priorityId)

newIssue.setCustomFieldValue(appDueDate, parentIssue.getCustomFieldValue(appDueDate))

newIssue.setComponent(parentIssue.getComponents())

newIssue.setCustomFieldValue(appSubDesc, parentIssue.getCustomFieldValue(appSubDesc))

String issueKey = ""

Map<String, Object> newIssueParams = ["issue": newIssue] as Map<String, Object>

if (true) {

Issue reallyNewIssue = issueManager.createIssueObject(reporter.name, newIssueParams)

issueKey = reallyNewIssue.getKey()

log.error "New issueKey:" + issueKey

ComponentAccessor.subTaskManager.createSubTaskIssueLink(parentIssue, reallyNewIssue, loggedInUser)

issueLinkManager.createIssueLink(reallyNewIssue.id, parentIssue.id, 10260L, 0L, reporter)

boolean isIndex = ImportUtils.isIndexIssues()

ImportUtils.setIndexIssues(true)

IssueIndexingService IssueIndexingService = (IssueIndexingService) ComponentAccessor.getComponent(IssueIndexingService.class)

IssueIndexingService.reIndex(reallyNewIssue)

ImportUtils.setIndexIssues(isIndex)

}

Page updated

Google Sites

Report abuse