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; } } }

Where does a Scriptrunner UI fragment need to run for the issue creation screen?

Midya Rahmani_qoled8

I've created some Javascript code and I'm trying to create a Scriptrunner UI fragment. Under the "Context(s)" option, I'm unsure which one to select. I need my javascript UI fragment to run on the issue creation screen. Here's the section I'm referring to:
Screenshot 2024-04-25 at 8.28.06 AM.png

Accepted answers

Vikrant Yadav

Hi @Midya Rahmani Welcome to Atlassian Community!

It is not possible to use Script Fragments on the Create Screen.

You can use Scriptrunner Behaviour for create issue screen.

All comments

Vikrant Yadav

Hi @Midya Rahmani Welcome to Atlassian Community!

It is not possible to use Script Fragments on the Create Screen.

You can use Scriptrunner Behaviour for create issue screen.

Vikrant Yadav

@Ram Kumar Aravindakshan _Adaptavist_ Do you have any suggestion or workaround to add Script fragment on create issue screen ?

Nic Brough -Adaptavist-

Welcome to the Atlassian Community!

The easiest way to work this out is to use the fragment finder in SR. See https://docs.adaptavist.com/sr4js/latest/features/fragments for how to find and use it

Improving the language and layout of fragments, including making the fragment finder easier to find and use is something we have in progress at the moment.

Midya Rahmani_qoled8

@Vikrant Yadav Thanks for the reply. I tried to create a behaviour for this in Jira DC, however I ran into some issues. I wasn't able to create a behaviour for the create issue screen that could hide certain drop down values on a single select drop down custom field depending on a selected component. Do you know if this is possible with behaviours?

Midya Rahmani_qoled8

Thanks for your response Nic, I tried enabling the fragment locator, however it unfortunately doesn't seem to show anything for the issue creation screen:

Screenshot 2024-04-25 at 8.47.54 AM.png

Midya Rahmani_qoled8

@Vikrant Yadav Thanks for your answer, I was able to figure it out using the following behaviour:

import com.onresolve.jira.groovy.user.FieldBehaviours
import static com.onresolve.jira.groovy.user.FieldBehaviours.getFieldById
import com.atlassian.jira.component.ComponentAccessor

def componentsField = getFieldById("components")
def affectedAreaField = getFieldById("customfield_10200")
def selectedComponents = componentsField.getValue() as List<Map<String, Object>>
def isApplicationSelected = selectedComponents.any { it["name"] == "Application" }
def optionsManager = ComponentAccessor.getOptionsManager()
def customFieldManager = ComponentAccessor.getCustomFieldManager()
def affectedAreaCustomField = customFieldManager.getCustomFieldObject("customfield_10200")
def config = affectedAreaCustomField.getRelevantConfig(issueContext)
def options = optionsManager.getOptions(config)

if (isApplicationSelected) {
// Filter the options, retaining only "Administration" and "Authoring"

def allowedOptions = options.findAll {
 it.value in ["Administration", "Authoring"]
 }
 affectedAreaField.setFieldOptions(allowedOptions)
} else {

// If "Application" is not selected, show all options
 affectedAreaField.setFieldOptions(options)

}

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

data-center