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

Prefill Description in one Request Type on Jira Service Management

Vera_wyss

Before the update to Jira 9.12.7, i had that the description was prefilled in one Request Type with a Script Runner Behaviour and it worked until the last update to Jira Data Center 9.12.7 and Jira Service Management 5.12.7. So does anyone know, how to do a description prefill just for one Request Type?

Accepted answers

Vera_wyss

Solution

I made an inquiry to the manufacturer and have now been away for 2 weeks. During this time there are Bug fix updates from the Script Runner app. Now that i have updated the app to version 8.33.0, my template is working as desired again.

Unfortunatly I don't know which bug fixed my problem but that means my code and settings were correct.

All comments

Ciara - _Eficode_

Hi Vera,

Welcome to the Atlassian Community.

Can you advise what version of Scriptrunner you are running please?

Thank you

Vera_wyss

Hi Ciara, thank you.
We use Script Runner version 8.31.0
Best regards

Ciara - _Eficode_

Can you check if all modules are enabled in the app?

And that the behaviour itself is enabled.

If it is enabled then can you see it being executed when the form is loaded?

Vera_wyss

where do i find the modules in the app?

the behaviour itseld is enabled.

no it is not executed, there is nothing in the execution.

Stefan Salzl_0i980g

Hi @Vera_wyss

Would it be possible to share your custom behavioue code? (as it should be prefilled on the create I guess it appears in the initializer ?)

Furthermore:

Is the code/initializer activated at all? Is there a run logged? And if yes: what does the log tell?

Best
Stefan

Vera_wyss

Hi @Stefan Salzl

Thank you for the feedback, I have added the code below. The Behaviour is also linked to the corresponding project and the associated issue type.

def desc = getFieldById("description")

def defaultValue = """

   

*Testdescription*

   

Test1:

Test2:

Test3:

   """.replaceAll(/    /, '')

if (!underlyingIssue?.description) { 

    desc.setFormValue(defaultValue)

}

Is the code/initializer activated at all? --> Not sure, where can I activate it?
Is there a run logged? --> No, there is no run logged.

Best regards, Vera

Stefan Salzl_0i980g

Hi @Vera_wyss

sorry for the confusing wording. I meant if the initialiser gets triggered and the code gets excuted. If so you can find the runs right below the script field. in general the script should be triggered every time the create screen opens (as this is the main part of the initialiser). so there should be runs logged (there are no runs in the screenshot but in the highlighted field you should find runs/executions on your side):

The question for me is the if statement:

Why the following statement?:

(!underlyingIssue?.description)

This will only result in true when there is NO description field in the issue. Then it will execute the block within the if (which could not be executed as there is no description field).

IF the description field DOES EXIST this statement results in FALSE and therefore the code within the IF block never runs and therefore the description field is never pre-filled.

Best
Stefan

Vera_wyss

Hi @Stefan Salzl

Okei i understand.

I didn't program the code myself and therefore can't say exactly why this statement is stored like this. What's strange is that I actually didn't change anything in the code but after the update it no longer works.