How to Create and Manage Groups in Redmine
Administrators can characterize groups of clients in Redmine. Groups can be included as individuals from ventures simply like normal clients, utilizing similar Roles as well. While adding a client to a current group, this client acquires the entirety of the group benefits.
Making groups
To make a group, do the accompanying:
- Snap Administration
- Snap Groups
- Snap New Group
- Put the title of your group in Name
- Snap Create
Including individuals and partner ventures
To add individuals to a group, do the accompanying:
- In Administration >> Groups
- Snap the name of the Group you wish to change.
- You'll see 3 tabs: General, Users, Projects
- General
❖ Change the name by altering the Name field
- Clients
❖ Include clients by checking the username box for every client
❖ Snap Add
- Projects
❖ Select a project from the spring up menu
❖ Set the Role
❖ Snap Add
Figure 1: Example Group Users tab
Figure 2: Adding Members to a Group
Figure 3: Example Group Project tab
Figure 4: Associating a group to a venture (from the Group setting)
Setting up User groups in Redmine
Admin > Groups
Here heads can oversee a group of Redmine clients.
Two client bunches are predefined: Anonymous clients and Nonmember clients. These groups have constrained consents concerning Redmine Projects and Issues.
Nonmember clients are completely enlisted clients (signed into Redmine) who are not added as Members to the undertaking they are seeing. Unknown clients are for the most part unregistered clients. These two groups will see a task on the off chance that it isn't private.
Note: Adding clients to bunches streamlines overseeing client jobs in regards to Projects since an entire gathering can be included as a venture Member with comparable Roles to clients.
Each gathering is appeared in the rundown by its name and number of clients. There is a sifting alternative by a catchphrase (e.g., group's name).
To make another gathering, click New gathering, type a name, and snap Create or Create and Continue (in the event that you need to make another group).
To alter a gathering, select it from the rundown. You can change the name of the gathering or include clients or partner ventures. Each assignment can be acted in the comparison tab.
To add clients to a chose gathering, go to the gathering's Users tab, click New client, and select at least one clients to include:
At the point when a client is added to a gathering, he consequently gets all gathering benefits (e.g., Roles in projects).
Rest Groups in Redmine
/groups.:format
GET
Returns the rundown of gatherings.
This endpoint requires administrator benefits.
Example:
GET/groups.xml
Response:
<groups type="array">
<group>
<id>53</id>
<name>Managers</name>
</group>
<group>
<id>55</id>
<name>Developers</name>
</group>
</groups>
POST
Makes a group.
This endpoint requires administrator benefits.
- Boundaries:
❖ Group (required): a hash of the gathering properties, including:
❏ name (required): the gathering name
❏ user_ids: ids of the gathering clients (an unfilled gathering is made if not gave)
- Example:
❖ POST/groups.xml
<group>
<name>Developers</name>
<user_ids type="array">
<user_id>3</user_id>
<user_id>5</user_id>
</user_ids>
</group>
❖ POST/groups.json
{
"group": {
"name": "Engineers",
"user_ids": [ 3, 5 ]
}
}
Response:
- 201 Created: bunch was made
- 422 Unprocessable Entity: bunch was not made because of approval disappointments (reaction body contains the mistake messages)
/Groups/:id.:format
GET
Returns subtleties of a gathering.
This endpoint requires administrator benefits.
- Parameter:
❖ incorporate (discretionary): a state of unconsciousness isolated rundown of relationship to remember for the reaction:
❏ user
❏ member
Example:
GET/group/20.xml?include=users
Response:
<group>
<id>20</id>
<name>Developers</name>
<users type="array">
<user id="5" name="John Smith"/>
<user id="8" name="Dave Loper"/>
</users>
</group>
PUT
Updates a current gathering.
This endpoint requires administrator benefits.
Erase
Erases a current gathering.
This endpoint requires administrator benefits.
/groups/:id/users.:format
POST
Adds a current client to a gathering.
This endpoint requires administrator benefits.
- Parameters:
❖ user_id (required): id of the client to add to the gathering.
Example:
POST/gatherings/10/users.xml
<user_id>5</user_id>
- Response:
❖ 200 OK: user was added to the gathering
/groups/:id/clients/:user_id.:format
Erase
Expels a client from a gathering.
This endpoint requires administrator benefits.
Example:
Delete/groups/10/users/5.xml
Response:
200 OK: User was evacuated to the group
