-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Hello!
We are reviewing the user management experience as a whole.
As we get closer to what the new experience looks like, we will post updates here. In the meanwhile, if you have specific requirements, please comment and let us know here.
Thank you,
The HipChat Data Center team.
Problem
We have integrated our Hip-chat to crowd. We created a delegated directory in Crowd dedicated for Hipchat only. This is allowing our users to authenticate against our AD.
Currently, Hip-chat log in page asking for email address for login, instead of username, unlike all other Atlassain applications. This is confusing for our usersas they are using their NT username for their authentication in all other Aastlassain application we have including JIRA, Confluence,Stash,Bamboo,Fe-Cru etc
Suggested Solution
Provide the option for users to log in using their usernames instead of email addresses.
Workarounds
None at this time
- is duplicated by
-
HCPUB-2447 Allow login with username or email
- Closed
- is related to
-
HCPUB-1137 Add UUID attribute to HipChat Server AD integration
-
- Closed
-
- mentioned in
-
Page Failed to load
[HCPUB-858] Provide an option to log in to HipChat Server using the username instead of email.
Workflow | Original: JAC Suggestion Workflow [ 3351576 ] | New: JAC Suggestion Workflow 3 [ 3606739 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: HF: Simple Issue Tracking Workflow v3 [ 1399588 ] | New: JAC Suggestion Workflow [ 3351576 ] |
Status | Original: Done [ 10044 ] | New: Resolved [ 5 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Reviewed [ 11472 ] | New: Done [ 10044 ] |
Link |
New:
This issue is duplicated by |
Attachment | Original: 1Z0-462-Exam-Dumps-2018.pdf [ 309010 ] |
Attachment | New: 1Z0-462-Exam-Dumps-2018.pdf [ 309010 ] |
Status | Original: To be reviewed [ 10026 ] | New: Reviewed [ 11472 ] |
Description |
Original:
h3. Problem
We have integrated our Hip-chat to crowd. We created a delegated directory in Crowd dedicated for Hipchat only. This is allowing our users to authenticate against our AD. Currently, Hip-chat log in page asking for email address for login, instead of username, unlike all other Atlassain applications. This is confusing for our usersas they are using their NT username for their authentication in all other Aastlassain application we have including JIRA, Confluence,Stash,Bamboo,Fe-Cru etc h3. Suggested Solution Provide the option for users to log in using their usernames instead of email addresses. h3. Workarounds None at this time |
New:
{panel:title=Atlassian Status as of 28 September, 2017|borderStyle=solid|borderColor=#3c78b5|titleBGColor=#3c78b5|bgColor=#e7f4fa}
Hello! We are reviewing the user management experience as a whole. As we get closer to what the new experience looks like, we will post updates here. In the meanwhile, if you have specific requirements, please comment and let us know here. Thank you, The HipChat Data Center team. {panel} h3. Problem We have integrated our Hip-chat to crowd. We created a delegated directory in Crowd dedicated for Hipchat only. This is allowing our users to authenticate against our AD. Currently, Hip-chat log in page asking for email address for login, instead of username, unlike all other Atlassain applications. This is confusing for our usersas they are using their NT username for their authentication in all other Aastlassain application we have including JIRA, Confluence,Stash,Bamboo,Fe-Cru etc h3. Suggested Solution Provide the option for users to log in using their usernames instead of email addresses. h3. Workarounds None at this time |
Remote Link | New: This issue links to "Page (Extranet)" [ 317731 ] |
Same as Michael Rudel on all points. Having the login to HipChat be different than the login to jira/confluence is confusing to users and makes it look like a disjointed product.