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

Hide Issuetypes from displaying during Move Jira screen

Vasanta Kumaar

Hi All,

I have currently hidden issuetypes from the create screen using script runners, but while we are moving the JIRA, users are able to still see the hidden issuetypes.

How can we hide those issuetypes same as I did in Create screen.

So When a user tries to move a issue from another JIRA project to Target Project they should not see hidden issuetypes.

Can anyone suggest.

Thanks,

Vasantakumaar

Comments

Mario Carabelli_h0bo0y

The documentation from Scriptrunner Staates that this isn't possible (https://scriptrunner.adaptavist.com/6.20.0/jira/behaviours-limitations.html#_screens).

What do you want to achieve?

Vasanta Kumaar

Hi @Mario Carabelli ,

In one of the JIRA project (Project A), I have hidden 3 issue types based on user roles to avoid creating jira with those issuetype.

So Whenever user tries to create a JIRA user will not see those issue types.

Recently the owner of the project has raised a concern that whenever a user from other JIRA project tries to move issue to this project A, they are able to view all the hidden issuetypes as well in the dropdown.

So our requirement is to hide the issuetypes in Move issue screen as well or is there any way to restrict the user to create jira's with those issue type.

Thanks,

Vasantakumaar

Mario Carabelli_h0bo0y

Hey @Vasanta Kumaar

thank you for the additional information. In this case you can use a special workflow in the project and restrict the "Create-Transition" of this workflow with a scripted condition/validator.

What you do logically is:

check if the executing user is or isn't a member of the roles with the permission to create issues of the restricted issue types. If he/she isn't a member then let the condition/valdiation fail if yes let it suceed.

Because the workflow isn't bound to the javascript UI (as behaviours are) you will disable the creation of these issuetypes also in the move action (and in bulk move operations).

Some pointers for the implementation can be found here: https://community.atlassian.com/t5/Jira-questions/Script-Runner-Restrict-creation-of-specific-issue-type-for/qaq-p/344865.

I unfortunately don't have the time to script it out for you right now but I hope it helps you to fullfill your requirement.

Good luck,
Mario

Vasanta Kumaar

Hi @Mario Carabelli ,

Thanks for information.

I tried to implement using validators in script and it works well by restricting user to create in create screen level, but not working during moving issues.

I can able to move issues without any restrictions.

Thanks,

Vasantakumaar

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira

adaptavist

jira-server

behaviours