Content
General info
User story
As a …
I want …
So that …
Visual design:
Desktop:
Mobile:
|
|
Acceptance criteria |
|
|---|---|---|
|
01 |
Given: When: Then: |
|
|
02 |
Given: When: Then: |
|
|
03 |
Given: When: Then: |
Category: ROCKEN Documentation
-
Story 2.2.4.1. RT. Profile account. Profile page. Personal edit mode
-
Story 1.6.3.3. Process list view table
Content
General info
This story involves the layout and functionalities of the process list view table in the CRM system. The table should display essential information about each process and include interactive elements like chat icons and status change options.
User story
As a CRM user,
I want to view a detailed table of processes with interactive elements,
So that I can efficiently manage and navigate through process details and interact with relevant information directly from the list view.Visual design:
Acceptance criteria
01
Scenario: Viewing Process Table
Given: User is on the process list view page
When: View the table
Then: The table includes columns for Date, icon chat, Company with Country, Vacancy, Status, Responsible, candidate, and forecast02
Scenario: Interacting with Chat Icon
Given: User is on the process list view page
When: Click the chat icon in a row
Then: Transfer to the chat tab in the collapsed view of the respective process03
Scenario: Changing Status in Table
Given: User is on the process list view page
When: Click to change the status in a row
Then: Ability to change the status for that process directly in the table04
Scenario: hover on the notes icon
Given: User is on the process list view page
When: hover on the note icon
Then: Display only the Note which was saved during the last status change in the list view, and not any last Note
-
Release Notes – ROCKEN-TALENT – Release NA 03.09.2024 – Sep 03 19:00
How to use this page
The release notes on this page have been generated using the Jira issues macro. Each column of the table represents one of the issue fields you selected to include when you created these release notes in Jira.
To edit any of these fields:
-
Select Edit or type e to edit this Confluence page.
-
Select the Jira issues macro table and then select the edit icon.
-
Select Display options to adjust the columns and number of issues that will appear in your table of issues.
-
Select Insert to save your changes.
-
-
Story 1.7.6.4. Adding a New User to Specific Business Units
Content
General info
This story involves the ability to associate a new user with specific business units within the organization. This ensures that the new user is correctly categorized and connected with the appropriate teams.
User story
As a CRM user,
I want to associate a new user with specific business units,
So that they are correctly categorized within the company’s organizational structure.Visual designVisual design
–
#
Acceptance Criteria
01
Scenario: Selecting a Business Unit
Given the CRM user is in the User Creation Mode
When they reach the business unit section
Then they should be able to select one or more business units from a dropdown menu or list.02
Scenario: Associating User with Multiple Business Units
Given the CRM user is assigning business units
When they select multiple units
Then the new user should be associated with all selected units in the CRM system.03
Scenario: Saving Business Unit Information
Given the CRM user has selected the business units
When they save the user creation form
Then the business unit associations should be saved and linked to the new user profile. -
Story 1.7.6.3. Adding User Contact Information
Content
General info
This story covers the functionality related to entering and saving contact information for new users. This includes phone numbers, email addresses, and office locations, ensuring that the new user can be easily reached by other team members.
User story
As a CRM user,
I want to enter and save contact information for new users,
So that they can be easily reached by other team members.Visual design
#
Acceptance Criteria
01
Scenario: Entering Contact Information
Given the CRM user is in the User Creation Mode
When they reach the contact information section
Then they should be able to enter a phone number, email addresses, and office location.
02
Scenario: Validating Contact Information
Given the CRM user has entered contact details
When they try to save the form
Then the system should validate the format of the phone number and email address and prompt for corrections if necessary.03
Scenario: Saving Contact Information
Given the CRM user has entered valid contact information
When they save the user creation form
Then the contact details should be saved and associated with the new user profile. -
Story 1.7.6.2. Assigning Roles and Permissions
Content
General info
This story focuses on the ability to assign specific roles and permissions during the user creation process. CRM users will be able to define the new user’s role within the organization and set the appropriate permissions that align with that role.
User story
As a CRM user,
I want to assign specific roles and permissions during the user creation process,
So that the new team member has the appropriate access rights and responsibilities within the CRM system.Visual design
#
Acceptance Criteria
01
Scenario: Selecting a User Role
Given the CRM user is in the User Creation Mode
When they reach the role assignment section
Then they should be able to select a role from a dropdown menu (e.g., Consultant, Recruiter, Admin).
02
Scenario: Setting User Permissions
Given the CRM user is assigning roles
When they choose a specific role
Then the system should automatically adjust the available permissions based on the role selected. -
Story 1.7.6.1. CRM. User Creation Form
Content
General info
This story covers the functionality of the user creation form, where CRM users can enter essential information to create a new user profile within the system. The form includes fields for entering names, roles, business units, contact information, and optional fields like avatars and additional links.
User story
As a CRM user,
I want to access a user creation form with fields for essential user details,
So that I can add new team members with the necessary information to the CRM.Visual design
#
Acceptance Criteria
01
Scenario: Accessing User Creation Form
Given the CRM user is in the User Creation Mode
When they click “+“ (Add New User)
Then the system should display a form with fields for first name, last name, role, business unit, division, position, email, phone, and country.
02
Scenario: Mandatory Fields Validation
Given the CRM user is filling out the user creation form
When they try to save the form without completing mandatory fields
Then the system should display an error message indicating which fields are required.
03
Scenario: Optional Fields for Additional Information
Given the CRM user is in the User Creation Mode
When they choose to add optional details like avatar or extra links
Then the form should allow them to upload an avatar and add extra links (LinkedIn, website) with a preview.04
Scenario: Saving New User Information
Given the CRM user has completed the user creation form
When they click the "Save" button
Then the system should create a new user profile with the entered details but not return to the user list view.05
Scenario: Canceling User Creation
Given the CRM user is in the User Creation Mode
When they click the "Cancel" button
Then the system should discard the entered information and return to the user list view without saving any changes. -
Epic 1.7.6. CRM. User creation mode
Content
General info
The User Creation Mode in the CRM system is designed to enable CRM users to add new team members to the system. This mode provides a streamlined and intuitive interface for entering essential user information, assigning roles, setting categories, and associating the new user with specific business units. The mode should also handle additional details like contact information, user privileges, and optional fields like avatar uploads. The goal is to ensure that the process of adding new users is efficient and aligns with the company’s organizational structure.
Epic ticket:
RT-6818
–
Получение подробных данных проблемы…
СТАТУС
User stories
- Story 1.7.6.1. CRM. User Creation Form
- Story 1.7.6.2. Assigning Roles and Permissions
- Story 1.7.6.3. Adding User Contact Information
- Story 1.7.6.4. Adding a New User to Specific Business Units
Visual design
-
2024-08 Search Queries for Candidate Search
Details about the dataset used for the analysis: All candidate searches between 7-20. August 2024, which is 10 working days and around 80 consultants (esitmated) were actively working at that time. There were 19067 total searches which means 1906 seaches per day or 24 searches per consultant per day.
Most queries have one or two words like Servicetechniker or Service Manager and almost all focus on one query type, there are almost no combinations like Informatiker Zürich or Azure DevOps.
No query uses advanced features like quotation marks for exact matches. Consultants might not be aware that this is a feature.
Query Types
Query Type
Example
Frequency
location
Zürich, Kreuzlingen
rarely
empty
frequently
phone
+41 123456789, 41213456789, 213456789
often
job
Business Analyst, Schweisser
frequently
skill
3D-Druck, .NET
frequently
language
Englisch, Italientisch
rarely
keyword
SAP Berechtigungen, 3D, Asset
frequently
company
Aldi, Apple, Adobe
often
product
Azure, AutoCad
often
email
john.doe@example.com
rarely
industry
Energiewirtschaft, Bauphysik, Biochemestry
rarely
unfinished
Gyn, Hyper, Lul, Elektrom
rarely
name
John Doe
frequently
copy/paste
Sehr geehrte…
rarely
address
Wydenstrasse 123, 8575 Bürglen, Schweiz
rarely
Frequency of the searches
Search Type
Count
% based on total
Per Day
Per Consultant Per Day
with free text query
10753
56
1075,30
13,44
with skills filter
238
1
23,80
0,30
with place_id filter
13959
73
1395,90
17,45
with categories filter
6295
33
629,50
7,87
with salary not default value
4817
25
481,70
6,02
Pagination details
Page
#
Cumulative
% Cumulative
Potential candidates seen
Notes
empty
13211
13211
69,3
20
Initial page load
1
253
13464
70,6
20
Paginated and came back to 1
2
2576
16040
84,1
40
84% of searches only look at page 1 or 2. Might be due to # of results
3
1134
17174
90,1
60
4
664
17838
93,6
80
5
397
18235
95,6
100
6
261
18496
97,0
120
7
157
18653
97,8
140
8
129
18782
98,5
160
9
78
18860
98,9
180
10
74
18934
99,3
200
11
34
18968
99,5
220
12
32
19000
99,6
240
13
28
19028
99,8
260
14
22
19050
99,9
280
15
8
19058
100,0
300
16
3
19061
100,0
320
17
4
19065
100,0
340
18
2
19067
100,0
360
19
0
19067
100,0
380
20
0
19067
100,0
400
Candidate Status
Candidate Status
#
Notes
empty
181
1
12
2
12
3
0
4
4
5
12987
6
30
7
0
8
3
[0]5
5811
Value was in an array
[0]6
58
Value was in an array
