• Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • 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.

      Currently cwd_user table in Crowd contains created_data column that shows when the user created. However, it'd be useful to add a column that shows who created this user. It's useful for administrators to know who created a particular user in Crowd instance.

            [CWD-4548] Show a creator of user in Crowd database

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3388626 ] New: JAC Suggestion Workflow 3 [ 3630714 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Simplified Crowd Development Workflow v2 [ 1393555 ] New: JAC Suggestion Workflow [ 3388626 ]
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Marek Radochonski (Inactive) made changes -
            Remote Link New: This issue links to "Page (Extranet)" [ 329666 ]
            Marcin Kempa made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Verified [ 10005 ] New: Closed [ 6 ]
            Marcin Kempa made changes -
            Link New: This issue duplicates CWD-538 [ CWD-538 ]
            Marcin Kempa made changes -
            Status Original: Open [ 1 ] New: Verified [ 10005 ]
            Owen made changes -
            Workflow Original: Crowd Development Workflow v2 [ 981973 ] New: Simplified Crowd Development Workflow v2 [ 1393555 ]
            Saleh Parsa (Inactive) created issue -

              Unassigned Unassigned
              sparsa Saleh Parsa (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: