Category: ROCKEN Documentation

  • Transcription of CRM (old arch) shadowing

    1. The first screen is empty, there is nothing on it. We will use it for Task Manager or dashboard.

    2. Clicking on the magnifying glass icon, then selecting processes. Processes are the first thing they view, but they are too hidden.

    3. It’s important that in the processes, all new changes are marked in green (as new), so in the morning, they can log in, check updates, and process those workflows.

    4. Most often, updates throughout the day are new messages from candidates, they respond to something, and the status may also change.

    5. Within the process, in the correspondence, it’s not very clear which messages are new and which have already been viewed, only the date can help distinguish between today’s and yesterday’s. The question is how to understand this throughout the day.

    6. The icon near the candidate indicates that the candidate applied for the job themselves, otherwise, it’s the consultant who suggested the vacancy to them.

    7. Check on the expert.

    8. When there are no green rows in the processes, the red dot from the process menu disappears. This happens when all processes have been viewed.

    9. Matching begins, you review the found vacancy and manually transfer the data from the vacancy to the CRM.

    10. In the filters, they have pre-selected only the categories in which they specialize.

    11. The second filter they use is by region, selecting all the German-speaking parts of Switzerland, while not selecting the Italian and French parts.

    12. New vacancies are marked with a “New” badge.

    13. Relevance is not very clear, it’s on the side of h28 (but it might be better not to use such a progress bar or describe it better).


    1. Companies are duplicated. It is explained that they are added separately by those who create publications on Rocken.jobs and those who add companies when matching vacancies. Something can be done about this. They find the relevant company based on the completeness of the profile.

    1. They look at the list of applicants filtered by their name (i.e., those they manage themselves). This filter is saved, it seems, even when you close the page.

    1. They manually copy all the data from the company’s website.

    1. When creating a vacancy, they select the working location. Here, you can choose Germany, somehow. They specify the city and the company’s address, then the default city/region.

    1. Application by Download — this is when the company’s website, where the original vacancy is posted, has a button to submit an application, otherwise, profiles can be sent via email.

    1. When creating a publication, they select categories from the list. But when adding skills, they use the search. It’s hard because to select from the list, you need to always know what and in which category something might be, so it’s easier to search in any case.

    1. For example, Visual Basic is VBA, which is impossible to find if you don’t know it (although they are usually experts in their domain, so this is worth remembering).

    1. A new publication typically adds one hard skill and two soft skills by default.

    1. The requirements for the candidate and qualifications are simply copied as text from the job vacancy website.

    2. On the candidate list page, candidates are marked as active, and there’s also a “Rockentalent” badge (this means there’s a profile on Rocken).

    3. They often use a radius filter when searching for candidates for a vacancy. It’s important that it’s not too far for the person to travel to the office, as companies might not be interested or it might not be cost-effective. (50 km is the basic maximum).

    4. After adding a vacancy to the system from an external site, they start searching for suitable candidates.

    5. They also use the category filter to narrow the search (you can automate candidate suggestions for vacancies, but it’s important to remember that different recruiters have different approaches).

    6. After narrowing the search, they review the candidate page; it’s more convenient to view it not through the CRM but via profile preview. There, they search for matches, particularly in skills.

    7. On the candidate’s page in the CRM, you can see all the applications of the candidate in the system. This candidate had a process with this company, so you need to check how their communication ended. If nothing serious, the candidate can be proposed.

    8. From the vacancy page (in the CRM), they send the candidate proposal. The candidate can be selected by either ID or name.

    9. You can suggest several candidates for a vacancy at once.

    10. You can choose not to send an email or send a notification to the candidate after logging in.

    11. There are also limits on the number of emails that can be sent (it seems more than two per day is not allowed). But the problem is no one knows if the limit has been reached before sending. However, there is an option to ignore this limit.

    12. On the candidate’s page, you can see vacancies that might suit them.

    13. Professional search — these are the processes related to this candidate.

    14. They have bookmarks in the browser for pages with typical search queries or filter sets and company pages they work with.

    15. On the company page, there are also suitable candidates.

    16. Shows how statuses work in processes. The issue with the 3rd interview — there can be more than three interviews, which happens rarely (but a live example was found right away). They solve it by sticking with the 3rd status and managing everything manually from there.

    17. Talks about the “On Hold” badge (on the “offered” status), meaning no one can handle this candidate until the candidate or company makes a decision. This block is removed after the decision is made.

    18. Shows notifications — they never use them.

  • Rocken Jobs Redesign Feedback

    DONE

    Discussion

    • Linking issue between Rocken.Jobs and the actual Talent Platform – lack of clarity for candidates between the two.

    • Anonymity concerns regarding the jobs advertised on our website versus the jobs displayed in the RT profile. (Do not show company logo and name on RJ)

    Landing Page

    • Suggestion: Add a “Already a member?” prompt. (quick apply, ask about account, all places to switch to RT)

    • Vacancy confusion – we tell candidates that jobs in the RT are named as such, but this may be unclear.

    • Categories: What are the main categories based on? Stats or random selection?

    • Functionality briefing: Shouldn’t this be on the homepage?

    • Consultants vs. staff: Clarify the distinction between recruiters and consultants.

    • Filter placement: Why aren’t the filters at the top? Having them in the footer makes them less visible.

    Application Page

    • Verified company: How do we determine if a company is verified? Verified = official partner?

    • Applicant regions: Is it possible to restrict applications by region?

    • Adding documents later: No, avoid this option!

    Publications

    • Salary expectation: Is it necessary? Not all publications provide this data.


    I have the same notes as listed above; however, I would like to add the following points:

    • Blocks about blog articles: These are not necessary as they are used solely for SEO purposes.

    • Clarify the distinction between Rocken Jobs and Rocken Talent in every step: Ensure that the difference between these two services is highlighted in every possible step or context. This should be made clear in case the user overlooks it in earlier steps or considers it only later on.

    • Increase links and CTAs to Rocken.ch: More links and calls to action should be incorporated.

    • Reevaluate the quick apply function: Consider whether it is truly necessary. Assess if the difference between “Apply” and “Quick Apply” is significant enough to warrant both options.


    Are the Employment type filters necessary? Because we only offer permanent. I know we have it as a filter in our CRM, but can you make it non-transparent to the outside world? (all filters view)

    Is it possible to insert a small button so that the candidate can apply without clicking on the job? (in Similar jobs block on Job page)

    more compact? That flashes the eye too much (Benefits block in job description view)

    Perhaps the position behind the name? (Rocken Contact on Job view)

    I think the blocks are good, but I prefer them to be a little smaller (more compact view of benefits of important information)

    Prefer language setting top right (footer)

    Job starters "Berufseinsteiger". The target group of young professionals usually has a lot of general questions about the labour market (salary, photo, certificates, career map, etc.). If they click on it, we can redirect them to a ‘career counselling page’. We can provide input. (Quick Filters at the bottom)

    from our Rocken Talents or Customers? Or both? (reviews on the main page)

    There are too many categories. Can you limit this so that perhaps only 10 are displayed, you click on them and then click on subcategories in a pop-up window? (categories on the main page)

    I would say "job categories", because otherwise candidates could think of industry (categories on the main page)

    Our professional consultants and recruiter (main page block about RT profile)

    Better: Timeline and as Cheryl mentioned like a map. Maybe also a sneakpeek in the background of the Talent platform "Benachrichtigungen" so that it is visualized for the candidate how the platform looks like. (main page how it works)

    Black is better than pink. What is the algorithm in the backend for the search line? Is it with boolean rules? For example: Will be there a drop down menu, If i type a letter? Or is it a free text field? (header while scroll)

    Just consultant. Not Expert, because not all of them are experts 🙂 Maybe like: Our consultants support the way from your application to your new job offer (hero benefits)

  • Task Manager Feedback

    DONE

    Missing functionality in tasks:

    1. Marking tasks as done

    2. Marking multiple users as assignees to the task

    To add functionality in Notifications:

    1. Add categorization, e.g.:

      1. New Vacancy in SPOC company

      2. If vacancy gets assigned to someone and there are no matches in the stated period of time

        1. Is it reassigned?

        2. Deleted

        3. Reserved

    Next steps:

    1. Add a TM view for management positions (BM, HoD)

      1. Need to see all tasks from the different people overview.

        1. All

        2. Specific employees

        3. Reassigning to tasks

    2. Add a TM view for recruiting positions (HoR, Recruiters, Customer Support)

      1. Notifications based on timelines (e.g. The publication going expired, applicant remaining in "in progress"/completing the interview for more than X days etc)

      2. Display of planned interviews in the calendar (they’ll need to add them there manually, there is no functionality of creating events in the profiles yet)

    3. Add categorization to the tasks, notifications, reminders, calendar events

    Idea: adding a possibility to send non-progress-related messages to the recruiter. We had this functionality in design when we started the NA but refused from it since it would take a lot more time to implement. This can be added later though, but also not as part of the TM, but as a part of the chat.

  • Release Notes – ROCKEN-TALENT – Release NA 29.08.2024 – Sep 29 09:19

    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:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro


  • Release Notes – ROCKEN-TALENT – Release NA 09.09.2024 – Sep 9 09:17

    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:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro


    Ключ Краткое описание Тип запроса
    RT-4610
    Create a docker-compose file for staging environment
    Задача

  • Release Notes – ROCKEN-TALENT – Release NA 05.09.2024 – Sep 5 09:16

    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:

    1. Select Edit or type e to edit this Confluence page.

    2. Select the Jira issues macro table and then select the edit icon.

    3. Select Display options to adjust the columns and number of issues that will appear in your table of issues.

    4. Select Insert to save your changes.

    Learn more about the Jira issues macro


  • Checklist template

    ID

    Summary

    Status

    Comment / Link to the bug in JIRA

    #

    Summary of verification

    Pass

    Fail

    put here a link to the bug in Jira in case of a Failed verification

  • Test Case template

    ID

    Summary

    Priority

    Component

    Description

    Documentation / Based on

    Labels

    Test Step / Activity

    Expected Result

    Verification marks or comments / Test data

    #

    Summary of test case

    Critical

    Major

    Minor

    Optional

    Short description of test case or its pre-conditions

    Optional

    Use existing labels or create any new

    Steps to execute

    Expected result after test case execution

    Test data for test case execution (optional)

  • Bug report instructions

    Bug report template

    Summary

    Rule

    Example

    Title should be self-descriptive ("What?" "How behaves?" "While what conditions?").

    [Vacancies]. Error page is displayed after visiting the Vacancy page and changing its status.

    Bug specific should be stated on first place (ex.: reproducible only on some device type, intermittent issue, environment specific, any other unique attribute).

    [Tablet] [Mobile] [RT]. Profile page is not adapting to the new layout after rotating the device.
    [Intermittent] [PROD] [Companies]. Updates are not displayed on the company preview page after clicking the “Vorchau“ button.

    Component name should be stated at the beginning of the title.

    [Applicants]. User is not shown in the Applicants tab after applying on the publication.

    Avoid using not exact phrases such as "working not appropriately", "not proper way","not per design". Try to be as specific as possible.

    [PaaS]. Report is downloaded in a not proper format.

    Description

    • Steps should be as specific as possible;

    • Examples of pages, profiles, vacancies, etc. that could be used for easier bug reproducing should be provided in any suitable form (URL, ID, etc.);

    • Actual and Expected results should be provided with appropriate screenshots, whenever applicable;

    • During bug creation, separate critical/major/minor bugs and create a separate bug for each issue;
      You can combine the bugs if they have the same priority. But if the priority is different – please create 2 or more bugs.

    • If during retesting the bug, the issues described initially are fixed, close the bug, and for all new issues that appeared after the fix and weren’t described in the bug initially create a NEW bug.

    Bug template

    Filed

    What to fill

    Project

    <Project Name>

    Issue type

    Bug

    Summary

    A brief one-line summary of the issue.
    Summary field name should be filled according template:
    [Area name] <Problem short and concrete description>

    Component

    <Component’s name> select from the dropdown. For each project, the list of components is specific.

    Description

    Description field should be filled as in following template:

    Preconditions:

    REPLACE the TEXT with needed configuration, if applicable.

    Steps to reproduce:

    1. Step_1.

    2. Step_2.

    3. Step_3.

    Actual result:

    Clear description of what actually happened.

    See attached screenshot for more details.

    <Screenshot>

    Expected result:

    Clear description of what should have been happened.

    See attached design for more details.

    <Screenshot> / <link to the design>

    Additional information:

    REPLACE the TEXT with Additional information, if applicable.

    Priority

    The degree of importance for the business to resolve the defect. It is driven
    by business value and indicates how soon the defect should be fixed.

    Labels

    Choose from the drop down. The label indicates the bug is related to some component. For each project, the list of labels is specific.

    Environment

    one of the (DEV, STG, PROD)

    Attachment

    If you can supplement your bug report with a picture that shows the
    problem, or a score that helps others reproduce, fix and verify the problem
    quickly, attach these files to the bug report. The attached files can be as
    follows: pictures, video-recording, other files types, if needed.

    Linked Issues

    <link to the related issue>

    Assignee

    The person whom the bug is assigned to (backend issues – BE/Dev Lead,
    Frontend issues – FE Lead)

    Epic Link

    Contains a link to Epic in accordance with overall structure of epics on the
    project.

    Sprint

    <sprint>

    QA Scope

    <testing scope>

    Verification statuses templates

     

     

     

    Passed

    Verification status: (синяя звезда) Passed

    Environment: <link>

    Device/Browser: Win10 + Chrome (the latest)

    Screenshot(s): <screenshot>

     

     

     Reopened

    Verification status: (синяя звезда) Reopened

    Environment: <link>

    Device/Browser: iPhone 13 Pro Max (the latest iOS + Safari)

    Actual result: <Actual result>

    Screenshot(s): <screenshot>

    Expected result: <Expected result>

     

     

    Blocked

    Verification status: (синяя звезда) Blocked

    Environment: <link>

    Device/Browser: Samsung Galaxy S22 Ultra (the latest Android + Chrome)

    Screenshot(s): <screenshot>

    Comment: <Additional info about blocking issue>