Query related to Scripted Field OR any other approach to get duplicated custom field

Is scripted field appear on ISSUE EDIT or any transition screen ?

As now, for me, it appear on issue view screen only and unable to see on issue edit screen.

I want it to appear on EDIT screen as well as a readonly.

(have verified by just keeping - "free text template" and - return "some value").


When i have use below script on scripted field then it shows me error while execute :

Error message as below:
The indexer for this field expects a java.lang.String but
the script returned a com.atlassian.jira.issue.fields.CustomFieldImpl - this will cause problems.


import com.atlassian.jira.ComponentManager

import com.atlassian.jira.issue.fields.CustomField

import com.atlassian.jira.issue.CustomFieldManager

CustomFieldManager customFieldManager = componentManager.getCustomFieldManager()

def componentManager = ComponentManager.getInstance()

def issueLinkManager = componentManager.getIssueLinkManager()

def selectedValues = customFieldManager.getCustomFieldObject("customfield_11447")
//custom field has multi selected values as it is a "multi select" field type.

return selectedValues

How i could use scripted field in issue edit/transition screen and also resolve above error.


any other approach to get duplicated custom field on issue EDIT screen, i will be fine on javascript or any way.

basically, during create isssue screen, there are coupleof fields (calendar, multi select) which needs to be populate on EDIT issue screen under additional tab but, by default, unable to add that fields as its already existed in same screen in first tab.

Please let me know if need more details.


2 answers

I am still looking in this if any one can help me.

0 votes

Mmm, the error message is not exactly clear, but I suspect you've created your own custom field *Type* here, and not got the indexing correct. I say that because you mention "text searcher", but the code says "multi select". Following this train of thought further, I suspect your code might be allowing for one type of searcher to be added to the field, but you've allowed a completely inappropriate type. A text searcher won't work on a field holding options, and a select searcher won't work on a text field. This goes on to break your field and your script because the index is incompatible with what the field asks for when the script runs.

Is my guesswork right? If not, then could you explain what type of standard custom field you have, and what the searcher is?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Mar 13, 2019 in Marketplace Apps

Marketplace Spotlight: Marketing apps for Confluence to keep your teams working on the same page


270 views 0 7
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you