Change an Issues but keep the old ones

[maximilian_lieder]

Hey Community.

With the launch of 2024, I would like to change our issue type BUG.
New mandatory fields are to be added.

What can I do so that I don't lose or have to change the existing BUGS?

I would like only newly created BUGS to be created according to the new requirements and the old BUGS can remain as they are.

Thanks in advance. 

Max 

[Antuan Sammak]

Hi @maximilian_lieder 

you can navigate to settings menu from top right corner and select issues, then create the new fields you want (if they are not available yet). then head to screens and select the screen relevant (the screen used by the bugs on a specific project) and add the fields to it). last go to field configurations and select the one used by the bugs (please make sure the one selected is used only by the bugs for specific project, sometimes the same config will be used across different type of tickets and/or projects) and from there you will get a list of all fields available where you can simply mark the field as required.

of course the above cannot be automated, so you will have to manually set it on the year starts.

also, this will not affect existing bugs and only will be applicable on new created ones.

you can find also further description about how to setup a field behavior in this link https://support.atlassian.com/jira-cloud-administration/docs/specify-field-behavior/

[Joe Pitt]

@maximilian_lieder @Antuan Sammak Actually, it will affect existing bugs if they are edited or transitioned in the workflow after the configuration is changed. 

[Antuan Sammak]

thanks @Joe Pitt for bringing this up to my attention.

appreciated.