Somehow we have users that shouldn't be listed as customers in a certain project. They have accounts, and we don't want to remove the account. We just want to remove them from this specific project.
These users aren't showing up under people, so it looks like they were added as customers somehow. And we don't know how, but there is no option for me to remove them from being a customer of this project.
I've tried adding to an organization, and that doesn't work. When I remove the org, they just go back to being listed as individual users. I'm at my wits end here.
you simply need to remove them from the projects where they do not belong. If a customer is on multiple projects and you remove them from one project it only removes them from that project. If you want to remove them from all projects then remove them from the User Management screen. Sometimes what happens is that a user is added to an org and that org is used on multiple projects. If you share an org across projects you need to ensure that the customers in that org apply to all projects using the org. Make sense?
ok so either they aren't part of the project OR they are in an organization. Let's check the later:
let's try two things:
If 1 & 2 strike out then let me ask a stupid question - are you 100% sure you are looking at the same project when looking at this screen and when looking at the Customers listed under the Project level? can you share an image of that screen that illustrates customers?
so u aren't crazy for sure. i think i'm learning something new about this "people" stuff which BTW is, IMO, a very poor implementation or at least very confusing. I'm not 100% sure what is going on or how to explain it just yet but it appears as if customers don't show up in the people list if their open/closed are both 0. This might indicate the customer has never logged in and maybe they don't show on the People view until that happens. Looking at one of my projects I see the same thing you are seeing. While I see many customer in the People screen I do not see any that have 0/0 issues.
I'm going to ping other community champions in hopes they know what is going on here. I'm also going to read up on the latest documentation to see if there is a clue there.
So hang tight...now that I'm stumped i'm having fun. ;-)
no answers yet but I wanted to add the results of a test I just performed in the event it helps others more quickly drive this question to closure.
Hypothesis: New customers added to a project do not result in that customer showing up under the Settings>People view.
So now the question I'm trying to answer is - Why do some customers not show under the People view for some projects? This is required if one needs to remove the customer from the project.
New Hypothesis: The reason a user shows under Customer but not under People is that their "Role" is not set (somehow). Users under People (in my instance) all have one of: Administrators, Contract Developers, Developers, Service Desk Customer, Service Desk Team, Tempo Project Managers. This theory needs to be tested and proven/disproven just not sure how to do that just yet.
@Boris Berenberg - Atlas Authority, thanks for chiming in here with this. However, i'm a bit perplexed by this workaround TBH. I thought that removing from an org only placed them back into the Customer list. Maybe the "delete org" action is the trick? Further, in reading back thru Brianna's notes I think she may have already attempted this but not sure. @Brianna Barnes, can you please try Boris' steps on one of your Customers and let us know if it works for you?
BTW, I searched in Atlassian's bug reports but didn't find anything there so I plan to open a support request w/ Atlassian in hopes they can spread some light on this topic. I will chime back here as I learn more. Here is the ticket (not that anyone else can view but it will serve me in the future) - #JST-389505
@Jackyou are correct, that was one of the work arounds that I did try and it didn't work. When you remove the user in an org, it drops it as an individual customer in the customer view (still not under the people section) and when you delete the org ALL the customers get dropped into the customer view.
so I heard back from Atlassian and I have copied their response below. I don't know if this is your situation or not but suspect it is. If so it appears to be WAD (works as designed). To be honest I don't like that answer and I doubt I would implement that way, but I sort of understand it. I haven't tried changing my config to test this but will. Can you verify that this is your issue and if you change your Customer Permision then it will address your needs?
======== snip ========
The customer xxxxxxxxx exists on the Customer list due to the Customer Permission is currently configured to Anyone can send a request without logging in as you can see at
As the customer does exist on your site, the customer would have access to the project. If the permission is set to Customers my team adds to the project, then only you would deny access to the user.
The difference between People and Customer list is People section is where you configure other roles including customers such as admins, team, collaborators while the Customer list will display all users who have access the project as all users including admins and agent can also become customers (act as a customer).
That shoots a hole in the response from Atlassian. While it might be what I see in my instance it isn’t your situation. I will update the ticket with them as such. Ultimately you may need to open a ticket with them so they can log into your instance to investigate.
@Boris Berenberg - Atlas AuthorityThe global setting is the same, we made sure that it's only who we want and not everyone that has access. So this is the same thing.
@JackThe funny thing is, I have a ticket going with Atlassian as well, and so far we haven't been able to figure it out there either.
I have exactly the same problem
I have a User Group in User Management which is 'All staff' for a company - 'All staff' is added into Service Desk as 'Service Desk Customers' for Users and Roles.
They are then in the Customers section as customers.
If you go https://jiraurl/projects/PROJECTNAME/customers customers are listed there as they were put there before being put an in an organisation.
You can delete the customers within an organisation but not when they have been placed directly into 'Customers'.
This is a problem and in fact for us could break GDPR as we are unable to remove them from a project that they are in.
AFAIK and for our instance; users will show up under Customers if they have the 'Browse Projects' permission.
Things to check:
Settings/Customer permissions - if this is set to 'Anyone can send a request', all users in your instance show up under Customers
Settings/Permissions - What roles/groups are allowed to 'Browse Projects'? If you have a group here or you've given a group a role from 'Settings/People' that has the Browse Projects ability they'll show up under Customers
Settings/People - As above, check what roles people/groups are assigned to and what permissions these roles have under the 'Settings/Permissions'
If a customer is directly added to Customers and not in an organization, they can be removed from the project Customers under 'Settings/People' where they'll be listed as 'Service Desk Customers'. If they have been added as part of an org. you can click on the organisation and to the right of the user's name an 'x' will appear if you hover over their name. If they still appear then they still have the Browse Projects somehow due to groups/roles and the permission scheme.
Now, where's the option to only allow actual customers under Customers? :)
We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan. &nb...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events