Manage Users

The "Manage Users" section in the Teamployees plugin is designed to facilitate the administration and oversight of both internal and external users within Jira. This feature provides an intuitive interface for viewing, filtering, and managing users based on various criteria such as team affiliation, account type, and assigned workload schemes. Additionally, managers can assign new workload schemes to individual users or groups of users seamlessly.

Assigning Workload Schemes

Efficiently assign or reassign workload schemes to individual users to align with changing project demands or organizational structures:

• Select User: Define the user for whom you want to apply the new workload scheme. If necessary, use the search function or filters to find the desired user.

• Choose Workload Scheme: In the "Workload scheme" column opposite the user, select the appropriate workload scheme from the drop-down list. The new workload scheme will be automatically applied to the user.

Bulk Assignment

Select multiple users and apply workload schemes in bulk, saving time and ensuring consistency:

• Select Users: Check the boxes next to the users you wish to assign a new workload scheme to.

• Choose Workload Scheme: Select the desired scheme from the "Bulk actions" drop-down list. The workload schema updates will then be automatically applied to the selected users.

Workload Schemes History

The "Workload Schemes History" function within the Teamployees plugin enables users to view the historical workload schemes for each user. This feature is essential for tracking changes in workload allocation over time, analyzing past workloads, and making informed decisions regarding future workload planning.

Go to the "Manage Users" section in the settings and click on the Workload History icon next to the user profile:

By default, the default scheme is set for all users, according to the settings in the Workload Schemes section:

The history is displayed in a chronological timeline format, showing changes in workload schemes over time. Each entry in the workload history is time-stamped, providing a clear timeline of changes:

• The period between the “Start Date” and the “End Date” means that all events will be processed according to the specified workload scheme ;

• "ongoing" means that the scheme is active from the "Start Date" and is valid until the current scheme for that user is changed.

• The “Start date” is the day the workload scheme changes.

  The “End date” is set to the day before the workload scheme changes.

• It is possible that different users may have different first workload schemes. This is due to which default schema was active when the change was first made.