The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

Assignee Picker providing unassignable users (and null default in Move Issue).

Deleted user
July 25, 2013

Using 5.1.8 and 5.2.11, I wonder what is the (near future) status of Assignee User Picker?:

Currently, we're very unhappy with the “Assignee-Drop-Box”

1. showing suggested users including non assignable users!

2. Additionally, in the Move Issue dialog a default of "-1" - instead of (Automatic) – is pre-selected, which causes tickets assigned incorrectly (Automatic is used to / assumed by users).

So far we're using the "disable new assignee picker" workaround described in JRA-27396 which at least provides back to "Automatic" default (for Move Issue) and showing (for us) less unassignable users, but I agree, it is a workaround.

As I would describe showing "Non-Assignees" in a assignee select to be major (as it was withJRA-4643), I wonder if there is a current or [near] solution ticket issue/discussion for this (I did not find)?

Regards
Torsten

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Deleted user
September 18, 2013

The Atlassian Bug for the "-1" issue is JRA-29938.

TAGS
AUG Leaders

Atlassian Community Events