Uploaded image for project: 'Crowd'
  1. Crowd
  2. CWD-76

Aliases needed for legacy integration

    XMLWordPrintable

    Details

    • 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.

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              ssmith Steve Smith
              Votes:
              7 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: