conjure-cp / nurse-rostering-demo Goto Github PK

Describe the bug
A timeout error occurs when attempting to schedule a large number of staff members simultaneously.

Possible Cause
Not sure for now

To Reproduce

1. Navigate to the scheduling page.
2. Select or input a large number of staff members for scheduling.
3. Attempt to finalize the scheduling process.
4. Observe the timeout error message or failure to complete the action.

Expected Behaviour
The system should be able to handle scheduling requests for a large number of staff members efficiently, without timing out or encountering errors.

Actual Behaviour
A timeout error occurs when dealing with bulk scheduling

Suggested Solution

1. Investigate the backend process to identify potential bottlenecks or inefficiencies causing the timeout.
2. Optimize the scheduling algorithm or process to handle larger data sets.
3. If feasible, consider introducing batch processing or staggered scheduling to alleviate the immediate system load.
4. Improve error messaging to inform users about potential limitations or suggest splitting the task into smaller chunks if the problem persists.

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the bug
At a screen width of approximately 793px -1011px, parts of the the dashboard column in the application is hided outside of the screen.

To Reproduce
Steps to reproduce the behaviour:

1. Open the application and navigate to the dashboard.
2. Adjust the browser window size to approximately 1011px width or use device emulation in the browser's developer tools.
3. Observe that the dashboard column layout becomes undesirably small.

Expected behaviour
The layout of the dashboard should be adjusted to show all four sections regardless of the screen size

Actual behaviour
The layout of the dashboard is not showing all four sections at approximately 793px -1011px

Suggested Solution
This issue likely resides in the CSS or UI framework rules governing the dashboard column. The layout might not be adjusting properly at around 793px -1011px screen width. Modifying the responsive design rules should resolve this problem.

Screenshots

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Additional notes
Tool for checking device screen sizes is mydevice.io.

See: https://github.com/conjure-cp/nurse-rostering-demo/actions/runs/6508691756/job/17678549550#step:7:39

Describe the Enhancement

• The shifts on the calendar can be listed in alphabetical order.
• Based on observations, it appears that they might be ordered by their current shift status or some other criterion.

Desired Behaviour
Shifts on the calendar should be listed in alphabetical order to facilitate easier tracking and readability.

Current Behaviour
Shifts appear to be ordered by their current shift status or some other non-alphabetical criterion.

Suggested Solution

• Look up @fullcalendar/react library
• Change the ordering setting for the FullCalendar component

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the bug

• When I click on the Enter as Admin button on the index page, it navigates to http://localhost:3000/nurse-rostering/dashboard.html. I receive a 404 error despite the project existing and running correctly.
• When I manually navigate to http://localhost:3000/nurse-rostering/dashboard, clicking any sidebar items also leads to 404 errors.

Possible Cause

• The .html extension on the Link href

To Reproduce
Steps to reproduce the behaviour:

1. Run the project locally with npm run dev.
2. Open a web browser and navigate to the index page: http://localhost:3000/.
3. Click on the Enter as Admin button.
4. Observe that you're redirected to http://localhost:3000/nurse-rostering/dashboard.html and encounter a "404 - Page Not Found" error.
5. Manually update the URL to http://localhost:3000/nurse-rostering/dashboard and press Enter.
6. Once on the dashboard page, click on any items in the sidebar.
7. Notice that clicking on sidebar items also results in 404 errors.

Expected Behaviour
I expected to navigate to the dashboard page and all the pages on the sidebar

Actual Behaviour
I received a 404 error page when navigating to the dashboard page and all the pages on the sidebar

Suggested Solution

• Ensure the Link components are correctly wrapping tags and are pointing to the right routes without file extensions (unless specifically intended).
• Restore the Line href to /dashboard as it was changed to /dashboard.html in the previous commit
• Remove .html file extension on the sidebar Links

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the bug
The block on the last column of the scheduled timetable is displayed as smaller in width compared to the blocks in other columns.

Possible Cause
Width setting for the FullCalendar component.

To Reproduce

1. Navigate to the scheduled timetable page.
2. Compare the width of the last column with the preceding ones.
3. Notice that the last column is narrower than the rest.

Expected Behaviour
All columns in the scheduled timetable should have a consistent width

Actual Behaviour
The block on the last column is distinctly narrower than the blocks on the other columns

Suggested Solution

• Look up the @fullcalendar/react module
• Update the width setting on the FullCalendar component

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

See https://github.com/conjure-cp/nurse-rostering-demo/actions/runs/6508691756/job/17729527844

Describe the bug
Oz faces this bug scheduling the timetabling when he was in Turkey. The next shift shown on the dashboard is 60+ hours I remember.

Note
This issue needs to be updated with more specific details.

Describe the bug

• When I navigate to http://localhost:3000/ in my browser, I receive a 404 error despite the existing project running correctly.
• The project is set up correctly, and the server has been started at 0.0.0.0:3000, accessible via the URL http://localhost:3000 as prompted in the terminal.

Possible Cause

• The base URL is set to /nurse-rostering for both development and deployment server

To Reproduce
Steps to reproduce the behaviour:

1. Run the project locally with npm run dev.
2. Open a web browser.
3. Navigate to http://localhost:3000/.
4. See the error "404 - Page Not Found".

Expected behaviour
Upon navigating to the root URL on localhost, the project's homepage should be displayed without any errors.

Actual behaviour
An unexpected 404 error is encountered when trying to access the root URL of the project on localhost.

Suggested Solution
See the pull request #7 for the task-allocation-demo.

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the Issue
The timetable block sporadically features a black triangle icon either on its left or right side.

Screenshot

Suggested Solution

• Look up the @fullcalendar/react module
• Ensure consistent positioning for the triangle icon unless its position (left vs. right) signifies different functionalities. In such a case, this differentiation should be made evident to users.
• Implement tooltips that appear on hover, providing a brief description of the icon's functionality and any significance its positioning might have.
• Add a legend or help section on the timetable page explaining the purpose of various icons and the importance of their positioning.

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the Enhancement
The system currently allows multiple nurses to be registered with the same name. Implementing a differentiation or prevention mechanism could prevent issues like adding the same nurse twice.

Desired Behaviour
The system should prevent the registration of nurses with identical names.

Current Behaviour
The system permits the registration of nurses with the same name without warnings or differentiation.

Suggested Solution

• Introduce a warning mechanism alerting administrators or users during attempts to register a nurse with a pre-existing name.
• Consider implementing a mandatory unique identifier for each nurse, such as an employee ID or system-generated ID.
• Permit additional details (like middle name, birthdate, or secondary ID) to distinguish between nurses with the same name.

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1

Describe the Enhancement

• Currently, after adding a new staff member, the Qualifications page resets to its default state 0.
• While this reset might be an intended feature, maintaining the current state and not resetting could improve user experience, especially when adding multiple staff members consecutively.

Desired Behaviour
After adding a new staff member, the Qualifications page should maintain its current state

Current Behaviour
After adding a new staff member, the Qualifications page resets to its default state 0

Suggested Solution

• Consider updating the page's behaviour to retain its state after adding new staff.
• If the reset is an intended feature, perhaps a toggle or setting can be added that allows users to choose between resetting and retaining the page's state.

Environment

• OS: macOS Ventura 13.2.1
• Browser: Chrome 115.0.5790.114
• Node.js version: v16.17.1