Forums

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

Drop Down list of issue types does not show the same issue type when moving issue to another project

Mattias Ohlsson March 22, 2012

Problem

We have issues that are registered in wrong jira-projects. So we want to move issues from one project to another. After the upgrade to Jira 5 we have noticed that the drop down list does not show the same issue type (as registered) in drop down list of issuetypes when selecting the new jira-project we want to move to. This makes it very confusing for the users not finding the same issue type. (It works in my on-demand instance).

There's a "workaround"... If you start typing the issue type you want, it is possible to select it.. but annoying though. So is this something in our configuration or is this something general with the jira installation?

Backround

(On the issue we select => move issue and the move issue screen is shown. => Selects another project => Want to select the same issue type, but not shown in drop down => We start typing the issue type name => It works.. But not good though..)

2 answers

0 votes
Susan Cline April 13, 2012

Thanks for the workaround. This solved our issues.

0 votes
Jobin Kuruvilla [Adaptavist]
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 22, 2012

I am guessing it is a change similar to the 'assignee' dropdown where it initially shows only the frequently used values but once you start typing, it will show all the matching ones.

Do you have a large number of issuetypes?

Mattias Ohlsson March 22, 2012

Hi Jobin,

thanks for your reply. No, we only have 5 issue types to select... :S

Dieter
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.
April 13, 2012

just thought the same as Jobin, so maybe there is also a parameter

-Datlassian.darkfeature.frother.issuetype.field=false

to return the old behaviour ? ...

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events