Default members keeps one person for each of five roles: Tech Lead, Project Manager, Tester, Developer and Product Owner. Every new project gets these people as team members when it is created, and Force default puts one of them on the projects that are already running. This guide shows how to set them and what forcing does.
Who can use it
Default members is in the side menu of the admin panel. To reach the panel, open the menu at the top right and choose Go To Admin Panel.
Every administrator sees the entry, but only a super administrator can use it. Anyone else who opens it gets a page saying they are not allowed in.
Set a default member
- Open Default members.
- In Add or update role, choose the Role.
- Choose the Person. The list shows only active people who have that role, with their email. Until you choose a role it says Select a role first.
- Click Save default member.
You see The default member for Tech Lead was updated., with the role you chose. Each role holds one person: if the role already has one, saving replaces them.
If the person stops being valid before you save, you see The selected person is invalid. or The selected person does not belong to that role.
The current list
Current configuration lists each role with its Person and their email. With nothing set, it says No default members configured yet.
To take a role off the list, click Remove on its row and confirm Remove this default member?. You see The default member for Tester was removed., with the role you removed. New projects stop getting someone for that role. The people already on projects stay where they are.
New projects
When a project is created, each default member joins it with their role, as long as they are still active. They join exactly as a member added by hand: the same database access a member with their role gets (a Tech Lead, Project Manager or Product Owner on the production and development databases, a Developer only on the development ones, and a Tester on none), and their hourly rate history is kept from the day you set how they are paid. They join without any way of being paid set; choose how each one is paid in the project's Team Members. See Manage projects and sprints.
Force a default member onto the active projects
Force default makes the default person the only one with that role on the projects you choose.
- Click Force default on the role's row.
- Force default member opens with the person and the role, and lists the active projects with an open sprint. Hidden projects and internal administrative projects are left out. Every project starts ticked; untick the ones to leave alone.
- Click Apply force, or Cancel to close without changes.
On each chosen project:
- If the default person is already the only one with that role, nothing changes.
- Otherwise, everyone else with that role leaves the project, and the default person joins if they were not there. They take the payment settings of the last person who had the role, or none if nobody had it.
- Tasks of that project waiting for validation are handed to the reviewers the project has now.
- Database access on the project's applications follows the change: the people who left lose it and the new person gets it. See Sync users with Ploi.
You must tick at least one project. If no project is active, the window says There are no active projects with open sprints to update. and Apply force stays disabled. If the default person is no longer active, you see Nothing to force.
The force report
When it finishes, a notice says how many projects were processed and how many changed, and Last force report appears below the list, one row per project:
- Project and Role.
- Before: who had the role, or Unassigned.
- After: the default person.
- Status: Added when nobody had the role, Updated when someone else was replaced, Unchanged when it was already right.
The report is not saved. It disappears when you leave the page.
Forcing cannot be undone from here. To put someone back, add them again in the project's Team Members.