-
Suggestion
-
Resolution: Fixed
-
None
Consider the following scenario:
- I have Confluence and JIRA installed at my site; no SSO
- On Confluence my login is 'ssmith', however on JIRA my login is "steve@atlassian.com"
- We deploy Crowd to unify the logins, using Confluence to seed the user DB
What happens to the old issues which are assigned-to/reported by steve@atlassian.com (who is now ssmith)?
Ideally we would have a method of assigning aliases to the logins, so that Crowd will know to map the old logins to the new.
- details
-
CWD-1464 Documentation link for new Users screen in Application and other help links
- Closed
-
CWD-1467 Highlight application-specific alias when searching in the context of that application
- Closed
-
CWD-1468 Add alias information to user UI
- Closed
-
CWD-1470 Re-enable by-email search tests when new schema lands on trunk
- Closed
-
CWD-1521 Implementation of the AliasService/Manager
- Closed
-
CWD-1522 Alias Object Model + Hibenate DAO
- Closed
-
CWD-1523 XML Migration for Alias Information
- Closed
-
CWD-1524 Search by Alias and other User attributes
- Closed
-
CWD-1561 Test Trusted Application support with Aliased applications
- Closed
- incorporates
-
CWD-1468 Add alias information to user UI
- Closed
-
CWD-1469 Remote API for managing user aliasing
- Closed
- is duplicated by
-
CWD-1030 Investigate ability to add account aliases for "change username" capability for Atlassian apps.
- Closed
- relates to
-
CWD-1133 Provide ability to rename users in Crowd.
- Closed