Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How to hide issue type from Create drop down

Lara Arthur
Contributor
March 13, 2019

Hello all,

I've seen multiple questions like this but no answer for what I'm actually looking for.

I have an issue type that I'm creating using the clone function from scriptrunner during a workflow. Here's the overall process in a nutshell - 

SDLC Workflow > @ transition xyz testing subtask is auto created (testing workflow) > tester finds defect and clicks on CREATE DEFECT > issue type "Defect" is created (with it's own Defect workflow) by pulling some info in from the testing subtask > Defect is linked to testing subtask

These defects should only be created via the testing subtask, but they are also in the Create drop down. How can I hide the issue type from the create drop down?

 

2 answers

0 votes
Payne
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 14, 2019

Issue types can be limited using a ScriptRunner Behaviour - https://scriptrunner.adaptavist.com/latest/jira/recipes/behaviours/restricting-issue-types.html

We use this approach, and it works nicely.

Lara Arthur
Contributor
March 15, 2019

Thanks Payne, will give it a try and add a response after I do!

kdickason
Contributor
December 9, 2021

@tpay I just tried this script and I'm getting an error here:

import com.atlassian.jira.component.ComponentAccessor

import com.atlassian.jira.security.roles.ProjectRoleManager

import

static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE

Error:  Unexpected token: import @ line 4, column 1.  Can you provide guidance?

0 votes
Joe Pitt
Community Champion
March 14, 2019

You can't. This has been asked many times, but as you've probably seen there are only some workarounds that prevent actually creating the issue. It's been asked about since before I started working in JIRA in 2007 so I don't think it will change. 

Lara Arthur March 14, 2019

Thanks for the response Joseph. Not the answer I was hoping for but at least now I can put the issue to rest.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events