Manage Contributors
Contributors are developers and other team members who complete actions and activities that contribute to your SEI metrics and insights. Contributors are represented by contributor records in SEI. SEI contributor records serve two primary functions: Account association and Collection association.
Account associations connect related user accounts across your SDLC tools. For example, you can associate a contributor's Jira, GitHub, and Harness accounts so the data from those accounts are correlated to the same record in SEI, rather than three "instances" of a user. This makes it easier to track individual contributor activity across tools.
You can use any attributes as dynamic filters for contributor-based Collections. Some attributes are included by default, such as Name, Email, and Integration. You can add custom attributes to further refine contributor records and create dynamic filters unique to your organization or teams.
SEI contributor records don't control access to SEI; these records are for data management only.
Configure attributes
To view and modify contributors select the Contributors tile under Settings.
Select the Settings (wrench) icon to edit contributor attributes. By default, contributors only include a Name and Email. You can use attributes as dynamic filters for contributor-based Collections. Therefore, you might find it useful to add custom attributes, such as roles, team names, departments, supervisors, or other designations.
To add custom attributes:
Select the Settings (wrench) icon.
Select Add Custom Attribute.
Enter a Title for the custom attribute category.
Select the Type.
In the Description column, define where the attribute's values come from.
Integration attribute
For the Integration attribute, SEI uses Email as the primary attribute to collate contributor identities across integrations.
For example, assume a user's email is a.developer@myorg.com, and you have integrations with Jira, GitHub, and Slack. If SEI finds the same email address in Jira, GitHub, and Slack, then the data from those integrations are all correlated to the same contributor in SEI.
However, if the user is registered under a.developer@myorg.com in Jira and Slack, but uses a different email for GitHub, then the GitHub data is associated with a separate contributor record. This is because SEI does not know that the other email address also belongs to a.developer@myorg.com unless you modify the contributor to include the user's GitHub email address.
Modify contributors (export and import)
SEI automatically detects user identities in your integrations and creates contributors from those identities. However, there are several reasons you might need to modify contributors, such as:
Users don't have the same email address for all accounts.
A user's identity wasn't detected through the integration.
You need to populate data for custom attributes that aren't otherwise populated.
To modify contributors, you must export a CSV file, edit it, and then import the edited file.
Select Contributors under Settings.
Select Import and Export Contributors.
Select Export Existing Contributors or, if you don't yet have any contributors, select Export Sample CSV.
Open the CSV file and edit the data accordingly.
Go back to the Contributors page in SEI, and select Import and Export Contributors.
Select Import Contributors, and upload your modified CSV file.
Manually add contributors
SEI automatically detects user identities in your integrations. If you need to manually add a contributor, follow the steps to Modify contributors, and add a row for each new contributor. At a minimum, you must provide a name and email for the contributor to be valid.
Go to the Contributors section within your account
Make the necessary updates to the user's information, including their email and related integrations and save your changes.
Common Use Cases
Merge contributors with the Collection merge operation
In this case, we have an existing user with an integration ID for example for Jira and an associated email. The goal is to add another integration ID, let's say for Github, to this user and merge the two accounts into a single user.
Identify the contributor with the Jira integration ID and an associated email.
Identify the contributor with the GitHub integration ID but without an associated email.
Select both contributors for the merge operation.
Once both contributors are selected, an option for Merge Contributors will appear in the top-right corner of the screen.
Click on the Merge Contributors option.
After clicking Merge Contributors you will be redirected to a screen where you can review the merge details.
Review the merge details, ensuring that the correct users are selected for merging.
Click on the Merge button to initiate the merge operation.
After clicking Merge you will be redirected to a screen showing the merged user. Click on the Save button to confirm the merge.
After clicking Save a pop-up confirmation window will appear. Click on the Proceed button to confirm the merge.
Last updated
