[CWD-76] Aliases needed for legacy integration

Feedback Policy:

Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

CWD-1467 Highlight application-specific alias when searching in the context of that application

CWD-1468 Add alias information to user UI

CWD-1470 Re-enable by-email search tests when new schema lands on trunk

CWD-1521 Implementation of the AliasService/Manager

CWD-1522 Alias Object Model + Hibenate DAO

CWD-1523 XML Migration for Alias Information

CWD-1524 Search by Alias and other User attributes

CWD-1561 Test Trusted Application support with Aliased applications

incorporates

CWD-1468 Add alias information to user UI

CWD-1469 Remote API for managing user aliasing

is duplicated by

CWD-1030 Investigate ability to add account aliases for "change username" capability for Atlassian apps.

relates to

CWD-1133 Provide ability to rename users in Crowd.

(4 details, 2 incorporates, 1 is duplicated by, 1 relates to)

Katherine Yabut made changes - 19/Sep/2019 5:51 AM

Workflow	Original: JAC Suggestion Workflow [ 3389184 ]	New: JAC Suggestion Workflow 3 [ 3630964 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]