nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom Field Value disappear in Edit Screen

Abinash Satapathy

Hello ,

We are facing some strange Issues. We are cloning one Ticket from One project (Lets Say Project1 ) to Project 2 .
Script runner works good . Cloning is happening and fields are also getting cloned from Project 1 to Project 2.

But when we Click on "Edit" in the Issue in Project 2 , the Custom Field Values disappears and it automatically gets set to None even though the Fields are visible in the View Screen.

One thing we have found out that if if the custom field context is common for both the projects then the issue is not happening .
But if we split the context into two for two projects the issue reappears even though the Option values are completely same .

We are not using any behaviors or any scripts in those projects .

Any one facing similar kind of problem.

Accepted answers

All comments

Antoine Berry

Hi @Abinash Satapathy

Have you checked if there is any behaviour for the Project 2 ?

Abinash Satapathy

Hello Antoine ,

No behavior in the second project . just two simple projects .

Br,
Abinash

Jack Brickey

Can you review the history or all tab to see if it provides a clue. Is there an entry that indicates the field’s value changed?

Antoine Berry

I am terribly sorry I missed the part in italics and below. I would have suspected a custom field configuration too. Do you dynamically see the value "disappearing" when you edit the issue ?

Abinash Satapathy

Hello I reviewed my History Tab and nothing shows up there .

Br,
Abinash

Abinash Satapathy

The values are not visible in edit screen at all . I mean no dynamic disappearing is happening .

If i select any option and click on Save then the value appears .

Br,
Abinash

PD Sheehan

While I agree from the other answer thread that ideally, mapping any select fields from the original issue context to the cloned issue context should be covered in the built-in postfunction "clones an issue and links".

I think maybe something like this may work (not tested)

import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.issue.fields.config.FieldConfig
def keysWithOptions = [
   'com.atlassian.jira.plugin.system.customfieldtypes:select',
   'com.atlassian.jira.plugin.system.customfieldtypes:multiselect',
   'com.atlassian.jira.plugin.system.customfieldtypes:cascadingselect',
   'com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes',
   'com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons'
]
ComponentAccessor.customFieldManager.getCustomFieldObjects(issue).each{cf -> 
   if(cf.customFieldType.key in keysWithOptions ) {
      def cfVal = issue.getCustomFieldValue(cf)
      def oldConfig = cf.getRelevantConfig(sourceIssue)
      def newConfig = cf.getRelevantConfig(issue)
      if(cfVal){
         if(oldConfig.id != newConfig.id ){
            def newVal
            if(cfVal instanceof ArrayList ){
               //findAll{it} should remove any nulls
               newVal = cfVal.collect{ getNewOption(newConfig, it.value )}.findAll{it}
            } else {
               newVal = getNewOption(newConfig, cfVal.value )
            }
            if(newVal){
               issue.setCustomFieldValue(cf, newVal) 
            } else {
               //no matching option in the other context
               // i'm not sure if it would still get cloned, but best force null
               issue.setCustomFieldValue(cf, null) 
            }
         }
      }
   }
}

def getNewOption(FieldConfig newConfig, value){
   def optionsManager = ComponentAccessor.optionsManager
   def newOptions = optionsManager.getOptions(newConfig)
   return newOptions.find{ it.value == value}
}

Abinash Satapathy

Thanks @PD Sheehan ,

I will giev a try on the code provided by you.

Today i tried to clone using JSU and JMWE plugin and both this plugin works like charm. Fields with shared context behaves as expected .

It seems this is an bug with scriptrunner .

Br,
Abinash

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

scriptrunner

custom-field

jira

jira-server