Resetting a prefilled field when changing the issue type

Alexander B. December 12, 2023

Hi all,

sorry, I have not been able to find any information on this so far, hence the following question:

I have created a behaviour with Scriptrunner, which pre-fills the field "Description" with a text for a certain project, for a certain issue type.

In Jira Cloud, as soon as I call up the "Create" button in the header, the correctly filled "Description" field is prefilled for this ticket type.

However, if I change the issue type in this window, the field REMAINS prefilled and is not cleared.

This was solved with Jira Server by entering the script in the "Initialiser" area. However, this does not exist in Jira Cloud. I have tried to add an issue type check to the script, but without success.

Question: How can I ensure that the "Description" field is only pre-filled for a specific issue type and is reset if the user selects a different issue type?

Thanks for your support!

1 answer

1 vote
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
December 12, 2023

Hello @Alexander B_ , 

Welcome to the community!

I am not sure whether script runner is capable to cater such use case. 

However, with my experience, I saw a couple of add-on that cater template for issue type . 

For example: Issue Template for Jira

I am sharing a list of add-on that you might want to explore here

Hope it will help. 

Alexander B. December 13, 2023

Hi @Himanshi,

with Scriptrunner for Jira Server this was possible without any problems. With Jira Cloud there seems to be a step backwards here. I'm sure one of the addons will solve the problem, I just would have liked it better if I could have solved it with Scriptrunner (again).

I think the next step will be to create separate description fields for the different ticket types - which is of course rather unfortunate for JQL searches.

Thank you,

Josh Moore February 23, 2024

Hi @Alexander B_ 

Did you ever find a fix for this?  We recently migrated from Server and have noticed the same issue.  We have a Behaviour to populate the description field for certain issue types, but it does not get reset if the issue type changes like it did in server.

I used the example template they provide as well.

Alexander B. February 25, 2024

Sorry, unfortunately not.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events