JSM Team-managed project user cannot use a user picket

Robert Hean
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 23, 2025

Hey team,

I'm in a bit of a pickle.. .I've got a JSM Team-managed project with about 10 agents. All the agents have the following:

  1. The default "Agent" role in the project
  2. A JSM license
  3. Access to all tickets (e.g. no restrictions)
  4. Ability to add/change the reporter and/or assignee field

4 of these individuals (all happen to be located in India) cannot change a custom user picker field.

The other 6 can (including one who sits in India with the 4 who can't).

None of the following has helped:

  1. Making a new Role and assigning folks to it
  2. Removing, then re-adding to the project
  3. making them project Admins

 

Given it's team-managed I'm not quite sure what else to look into... would appreciate any ideas!

3 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Roger February 24, 2025

Maybe you can get more insight if you replicate the situation in a minimal setting on a test-environment.

0 votes
Paul Daly February 24, 2025

Is there any user filtering on the user picker field? 

0 votes
Csaba Vertessy February 23, 2025

Hey, 

 

Hm, just a guess: are these agents part of the group on which the user picker is based on?

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

TAGS
AUG Leaders

Atlassian Community Events