4 answers
Hey Antoine:
Tried your script above (to copy custom field value from parent) and got this:
I thought it would be good to summarize what finally worked here:
Goals:
- Have a story, bug, task, etc. inherit a custom field value from epic upon create.
- Have a sub-task inherit a custom field value from a parent task upon create.
Goal 1 Post Function (Copy custom field from Epic to Story upon create):
- Create custom post function using script-runner on the Create transition in your workflow.
- Script should precede the out-of-the-box "Create the issue originally" post function
- Script:
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.MutableIssue
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def issue = issue as MutableIssue
["Initiative"].each { cfname ->
def cf = customFieldManager.getCustomFieldObjects(issue).find {it.name == cfname}
log.error("cf : " + cf)
log.error("issue : " + issue)
def epicCf = customFieldManager.getCustomFieldObjects(issue).find {it.name == 'Epic Link'}
if (!cf || !epicCf) {return}
def epic = issue.getCustomFieldValue(epicCf) as Issue
if (!epic) {return}
def cfValue = cf.getValue(epic)
log.error("cfValue : " + cfValue)
issue.setCustomFieldValue(cf, cfValue)
}
4. Screen capture:
Goal 2 Post Function (Copy custom field from Story to sub-task upon create):
- Create custom post function using script-runner on the Create transition in your workflow.
- Script should FOLLOW the out-of-the-box "Create the issue originally" post function
- Script:
mport com.atlassian.jira.issue.util.DefaultIssueChangeHolder
import com.atlassian.jira.issue.ModifiedValue
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.index.IssueIndexingService
def customFieldManager = ComponentAccessor.getCustomFieldManager()
int cfId = 11002
def cf = customFieldManager.getCustomFieldObject(cfId)
log.error("cf : " + cf)
log.error("issue : " + issue)
def cfValue = issue.getCustomFieldValue(cf)
log.error("cfValue : " + cfValue)
def cfParentValue = issue.getParentObject().getCustomFieldValue(cf)
log.error("cfParentValue : " + cfParentValue)
def issueIndexingService = ComponentAccessor.getComponent(IssueIndexingService)
issue.store()
issueIndexingService.reIndex(issue)
if (issue.isSubTask()){
cf.updateValue(null, issue, new ModifiedValue(cfValue, cfParentValue), new DefaultIssueChangeHolder())
log.error("Custom field updated on issue " + issue.getKey() + " with value " + cfParentValue)
}
Groovy didn't like the nested expression. See attached and this link:
https://github.com/fabric8io/fabric8/issues/2707
error:
The script could not be compiled: <pre>org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed: Script730.groovy: 54: expecting '}', found '' @ line 54, column 2. } ^ 1 error </pre>.
Hi Barbara,
I think there is a typo in your custom field id because it cannot be 4 digits only. Go to Custom fields > Configure :
As for your script, I usually encourage to use custom field ID instead of name (so you are fine if any admin changes the name). But of course it is up to you.
However I strongly recommand using
cf.updateValue(...instead of
issue.setCustomFieldValue(cf, cfValue)because as you can see here https://docs.atlassian.com/software/jira/docs/api/7.1.2/com/atlassian/jira/issue/IssueImpl.html setCustomFieldValue does not write the value in the database.
Antoine
Yes, I'm sure it is not updated (from jql and edit issue). The issue getting updated is a sub-task. Does jira see a sub-task as just another issue?
When I added the line above I got this error:
Screenshot of transition post functions here:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.