Information Updated On: December 26, 2024
Current: 6
Scheduled: 3
Release: 0
Blocked: 0
Code Coverage Backend: 74%
Code Coverage Frontend: 35%
0.31.53 on 21st of December, 2024
As documents and files get uploaded and removed from NearBeach, the storage spaced used by your organisation increases. Though storage space is cheap, it can get expensive over time. A simple solution to this problem, is to find all documents/files that have been deleted from the system after a certain amount of time, and purge them from the S3/Blob storage. This will free up some space.
We will flag with the system that this particular document has been purged and is no longer needed on the blob storage.
Users require more information on the gantt chart when it comes to projects and tasks. Implementing a tooltip to pop up with the project/task description will help the user understand that particular object and it's relevancy to the sprint.
Understanding where an object sits in relationship to other objects are important on a gantt chart. For example a requirement item could have multiple tasks associated to it. To achieve this, we will implement the ability for objects on a Gantt chart to have children. These will appear below the parent object.
We would also like to achieve;
The NearBeach Flow is an understanding of how NearBeach works as a project management system. It describes at a helicopter level how each module of NearBeach connects and flows into the other modules.
These ideas will need to be written down in our documentation.
Documentation is extremly important to any project. We will refresh the following documents;
Whilst we need to complete the documentation for the following modules;
Currently our documentation is on Read the Docs
To open NearBeach up to other applications so they may also utilise NearBeach's functionality, we will need to implement an API. We could potentially then look at implementing plugins or extended functionality for NearBeach utilising this API.
The main blockers for this particular task at the moment, is the OAUTH/permissions. For example a dashboard will not be able to log into NearBeach, however if we have a simple token authentication (like used in OAuth), we could bypass the login screen.
We'll also need to research how a user will send form data to our backend. For example it's shape and what we are expecting.
Card202 - Implement 2FA for login
Card301 - Implement 2FA with 1Password
Like many project management systems out there, we will need to implement a way a project/task can be estimated. For example a user might use story points. We are investigating how this feature will be re-implemented back into NearBeach and what new functionality it could handle. i.e implementing an estimation feature where multiple users could supply estimations.
Card342 - Implementation of Story Points - for Job Quotation
We do not want to restrict NearBeach to English speaking users. We would like to offer NearBeach to anyone, no matter their language. Translating NearBeach into multiple different languages will open up NearBeach as a useful tool for everyone.
Currently we need to research the most effective way we can implement this, and going forward open up the doors for anyone to submit a translation into NearBeach. Following the translation of NearBeach we will also need to translate the documentation.