-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
4.19.1
-
None
-
1
-
Severity 3 - Minor
-
Issue Summary
Starting on JSM 4.19, when users are with 'Assignable User' permission but NOT with service desk role, the user is showed in user picker but cannot have the tickets assigned.
The expectation, as the user is not in a role that can assign tickets, is the users not shown in user picker auto complete or search.
This is reproducible on Data Center: yes
Steps to Reproduce
- In an 4.19+ environment create users
- Create a group and assign the users to the group
- In Project Settings > Permission add the group to 'Assignable User'
- In Project Settings > User and Roles ensure the group/users are not in roles
- In any JSM ticket go to Assignee field and start typing the username of the user from the group, it will shown and if try to assign the ticket a message will appear indicating the user cannot be assigned issues.
Expected Results
Neither have the users appearing in Assignee user pick nor give the possibility to assign.
Actual Results
The unexpected users are shown as well as can try to assign the ticket to them, resulting in error.
Workaround
Remove the unnecessary group/users from 'Assignable User' permission.
- relates to
-
-
- Gathering Impact
-
- was cloned as
-
-
- Gathering Impact
-
[JSDSERVER-12403] JSM 4.19+ user pick showing unnecessary users
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Closed [ 6 ] |
| Link | New: This issue relates to JRASERVER-74888 [ JRASERVER-74888 ] |
| Link |
Original:
This issue is related to |
| Link |
New:
This issue is related to |
| Link | New: This issue was cloned as JSDSERVER-12416 [ JSDSERVER-12416 ] |
| Description |
Original:
h3. Issue Summary
Starting on JSM 4.19, when users are with 'Assignable User' permission but NOT with service desk role, the user is showed in user picker but cannot have the tickets assign. The expectation, as the user is not in a role that can assign tickets, is the users are not shown in user picker auto complete or search. This is reproducible on Data Center: yes h3. Steps to Reproduce # In an 4.19+ environment create users # Create a group and assign the users to the group !group.png|thumbnail! # In Project Settings > Permission add the group to 'Assignable User' !permission.png|thumbnail! # In Project Settings > User and Roles ensure the group/users are not in roles !roles.png|thumbnail! # In any JSM ticket go to Assignee field and start typing the username of the user from the group, it will shown and if try to assign the ticket a message will appear indicating the user cannot be assigned issues. !userpicker.png|thumbnail! !error.png|thumbnail! h3. Expected Results Neither have the users appearing in Assignee user pick nor give the possibility to assign. h3. Actual Results The unexpected users are shown as well as can try to assign the ticket to them, resulting in error. h3. Workaround Remove the unnecessary group/users from 'Assignable User' permission. |
New:
h3. Issue Summary
Starting on JSM 4.19, when users are with 'Assignable User' permission but NOT with service desk role, the user is showed in user picker but cannot have the tickets assigned. The expectation, as the user is not in a role that can assign tickets, is the users not shown in user picker auto complete or search. This is reproducible on Data Center: yes h3. Steps to Reproduce # In an 4.19+ environment create users # Create a group and assign the users to the group !group.png|thumbnail! # In Project Settings > Permission add the group to 'Assignable User' !permission.png|thumbnail! # In Project Settings > User and Roles ensure the group/users are not in roles !roles.png|thumbnail! # In any JSM ticket go to Assignee field and start typing the username of the user from the group, it will shown and if try to assign the ticket a message will appear indicating the user cannot be assigned issues. !userpicker.png|thumbnail! !error.png|thumbnail! h3. Expected Results Neither have the users appearing in Assignee user pick nor give the possibility to assign. h3. Actual Results The unexpected users are shown as well as can try to assign the ticket to them, resulting in error. h3. Workaround Remove the unnecessary group/users from 'Assignable User' permission. |
| Status | Original: Gathering Impact [ 12072 ] | New: Needs Triage [ 10030 ] |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Impact [ 12072 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
Starting on JSM 4.19, when users are with 'Assignable User' permission but NOT with service desk role, the user is showed in user picker but cannot have the tickets assign. The expectation, as the user is not in a role that can assign tickets, is the users are not shown in user picker auto complete or search. This is reproducible on Data Center: yes h3. Steps to Reproduce # In an 4.19+ environment create users # Create a group and assign the users to the group # In Project Settings > Permission add the group to 'Assignable User' # In Project Settings > User and Roles ensure the grou/users are not in roles # In any JSM ticket go to Assignee field and start typing the username of the user from the group, it will shown and if try to assign the ticket a message will appear indicating the user cannot be assigned issues. h3. h3. Expected Results Not appear the user or give the possibility to assign (and return an error) h3. Actual Results The unexpected users are shown as well as can try to assign the ticket to them. h3. Workaround Remove the unnecessary group/users from 'Assignable User' permission. |
New:
h3. Issue Summary
Starting on JSM 4.19, when users are with 'Assignable User' permission but NOT with service desk role, the user is showed in user picker but cannot have the tickets assign. The expectation, as the user is not in a role that can assign tickets, is the users are not shown in user picker auto complete or search. This is reproducible on Data Center: yes h3. Steps to Reproduce # In an 4.19+ environment create users # Create a group and assign the users to the group !group.png|thumbnail! # In Project Settings > Permission add the group to 'Assignable User' !permission.png|thumbnail! # In Project Settings > User and Roles ensure the group/users are not in roles !roles.png|thumbnail! # In any JSM ticket go to Assignee field and start typing the username of the user from the group, it will shown and if try to assign the ticket a message will appear indicating the user cannot be assigned issues. !userpicker.png|thumbnail! !error.png|thumbnail! h3. Expected Results Neither have the users appearing in Assignee user pick nor give the possibility to assign. h3. Actual Results The unexpected users are shown as well as can try to assign the ticket to them, resulting in error. h3. Workaround Remove the unnecessary group/users from 'Assignable User' permission. |