Hide the issuetype options from issuetype field

[nalams]

In one project I have to hide bug,support issuetype options from  issuetype field.For this I have used scriptrunner behaviours

I have used the script provided by scriptrunner for hiding few issuetypes from the issuetype field.

Solved: ScriptRunner - How To Restrict Issue Type Creation...

The issue here is the script is working on firefox browser but not working on Edge and Chrome.

Referred this community post but it is not working on chrome and edge browsers.

Hide Issue Types with ScriptRunner Behaviors (not ...

Solved: ScriptRunner - How To Restrict Issue Type Creation...

Can anyone please let me know what might be the issue for this script not working on chrome and edge browsers 

[Florian Bonniec]

HI @nalams 

Why do you need to hide them ? Could you remove them by creating a dedicated Issue Type Scheme for this project instead ?

Regards

[Dick]

Exactly! And this functionality comes right out-of-the-box.

Kind regards,
Dick

[nalams]

Actually the project was migrated from other instance to our instance and we have issues in the issuetypes we want to hide.

If we remove the issuetypes from the issuetype scheme,then we have to associate the issuetypes of the existing issues.,

For eg: I have Bug,Task,Support,Epic currently I want to remove Bug and Task, then the exisitng issues which have issuetype of Bug and Task should be migrated to either support or Epic

[Dick]

@nalams 

If you don't want the issues visible (at all), then why don't you move them to another project before moving the others to the desired new project without these bug/task issue types. Keep it simple for yourself.

Kind regards,
Dick

[Ram Kumar Aravindakshan _Adaptavist_]

Hi @nalams

In your description, you mentioned:-

The issue here is the script is working on firefox browser but not working on Edge and Chrome.

Please clarify, what version of ScriptRunner and Jira you are using. There was a major bug fix for the ScriptRunner Behaviours after Google Chrome version 127.x.x.x which caused mutation problems resulting in the Behaviour to fail  in Chrome based Browsers.

Please refer to this Bug report for more information.

Thank you and Kind regards,
Ram