-
Suggestion
-
Resolution: Unresolved
-
505
-
16
-
At the moment, we can't set an ETA for this feature to be released, since there's a number of factors that determine how our product team prioritizes new features. Consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.
You can learn more by reading Implementation of New Features Policy.
Although we understand the value of this feature, we do not have a short term timeline for its delivery. The main reason for this is there are dependent projects that need to be completed first.
I recently published a blog looking at our customer management vision https://community.atlassian.com/t5/Jira-Service-Management-articles/Choosing-the-right-approach-to-Customer-Management-in-Jira/ba-p/1970761. I hope to be in a position to prioritise this feature in the next horizon of this vision. It is definitely amongst the top requirements for External Customers.
I will update again at the end of the year, or if anything changes.
Problem Definition
There's no easy way to change the customer's email address.
Suggested Solution
For the Jira Service desk administrators to have the ability to change the customer's e-mail address and retain all the issues that is in progress.
Workaround
Try migrating the customer account to "Atlassian account":
- Login as a site-admin
- Operate migrate to Atlassian account for the portal customer account in question
- Optional: maybe you want to disable the product access for the account. But make sure to keep Has access on site enabled.
With that, now the user can change the email address at https://id.atlassian.com/manage-profile/email.
Besides, consider adding yourself as a watcher to be kept informed as to the state of this feature request moving forward. With that way, if our development team updates the ticket, you'll be notified via email.
- duplicates
-
- Closed
- is duplicated by
-
- Closed
- is related to
-
- Gathering Interest
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
-
-
-
-
-
-
-
-
-
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSDCLOUD-5746] Change the customer e-mail address
| UIS | Original: 503 | New: 505 |
| UIS | Original: 476 | New: 503 |
| UIS | Original: 460 | New: 476 |
| UIS | Original: 459 | New: 460 |
| UIS | Original: 458 | New: 459 |
| UIS | Original: 459 | New: 458 |
| UIS | Original: 461 | New: 459 |
| UIS | Original: 458 | New: 461 |
| UIS | Original: 443 | New: 458 |
When you migrate a portal only customer to a migrated account, will it keep the setup as customer? I don't want to pay a license for them in Jira. They need portal only access and I need to change their email address for the same reason? Also, bulk edit would be nice too.
We use Jira Customers for internal as well. We have 250+branches that we support nationwide and use Jira for our ticketing. I only want my branch guys to have access to the portal so I added them all as customers. Now we rebranded and have a different domain name that I want to update them all to. I can't do that and can't find an API setup that shows how to bulk edit them. All I need to do is change the domain part of the email address. So, if migrating them to an Atlassian account is the right way, 1. does that keep them as customer only and 2. can that be bulk edited at that point to change the email address? Otherwise it's migrate, then open each one again and update the email address. That is close to 1500 emails. Insights or direction on where I can turn for answers?