Quote template progress

The users can now add and edit quote templates and preview their quotes. Only a few more critical functions to add into this functionality before I will state it is completed. We are hoping to have this functionality completed by the weekend of the 25th.

Other functionality which we want to roll out is adding the ability for groups to have children and report to fields within them. This will allow more depth and structure to the groups within NearBeach. We are currently planning to see what works and what will cause more issues.

Please also consider donating to our patreon, every dollar does count: https://www.patreon.com/NearBeach

New month, a new development stream

“Good news, everyone!” – Professor Hubert J. Farnsworth As most of you know, the futurama character would then go on to say “The alpha development branch 0.14 has been completed.”.

0.14 branch focused heavily on stability for NearBeach, bringing it up to a minimal viable product (MVP). This is exciting news for us, as it now becomes a transition between faintly using our own product to the start of using our product to help produce our product. We are finally happy in the direction that NearBeach is taking and will be meeting over the next few weeks to discuss the features and requirements that are missing from NearBeach.

If you have any features or requirements that are missing from NearBeach, we want to hear about them. You can either respond to this post or send us a tweet @nearbeach_inc. Without your input we will not progress.

Busy sprint

So over the next couple of days I will be implementing campus’ for the customer module where customers are not connected to an organisation. This will be useful for cases where you have an independent consultant that you need to know their business location etc.

Another development will be the rollout of TinyMCE to help improve user experience and gathering of notes. TinyMCE still is in testing mode and we will be deciding whether to use the LITE or normal version.

Development Alpha-0.14.3 Release

Fixed Bugs

  • BUG350 – Failure to create new task
  • BUG329 – Deleting costs refreshed the projects page
  • BUG317 – Test Emails with customers with no orgnaisation
  • BUG305 – Chosen-js not 100% width
  • BUG347 – User not notified that fields are incorrect when creating an organisation
  • BUG345 – Menu Expansion

Visual Changes over the new 2 weeks

Just an error correction from the last post. We have released 0.14.2, we are currently working on 0.14.3. We just keep thinking we are still on the previous version.

In the next two weeks you will notice two things changing around NearBeach;

  1. All textarea’s will be changed into TinyMce’s WYSIWYG editor
  2. All date/time input’s will be changed to the jQuery datetime pickers

This is to help improve NearBeach’s user experience. These changes will occur over both releases 0.14.3 and 0.14.4. Each will be tested thoroughly before release – the 0.14 branch is meant to be a stable alpha branch. We hope you like the improvements.

What to expect in the next two weeks

The next two weeks will be busy. We have noticed a bug fix that could improve the user experience for all modules ten fold. We are planning to roll out with this change hopefully in 0.14.3. As for release 0.14.2, it is literally just around the corner. This will leave a few of the more complicated bugs in the “In Progress” status.

This is just a very quick update on the changes happening to NearBeach, we hope you enjoy the changes we are making. Another full test run will occur after the release of 0.14.3, which will give us more bugs to find and destroy.

Release 0.14.2

Good news everyone, the newest stable release Alpha-0.14.2 has just been released this morning. You will be able to find it in the usual spot on github – Alpha-0.14.2 Looking at Bugzilla we only have 12 more bugs to process before doing something we have not done before, a complete re-test of the system. Usually after so many bug fixes we just do a quick shake out before we eagerly move to the next branch (which is a development cycle). However this time we are trying to design the 0.14 branch to be NearBeach’s most stablest branch, a branch that we can recommend people to stay on. The reasoning behind this is;

  • Building a stable foundation for future improvements and enhancements
  • Start competing with what is already on the market
  • Use NearBeach to start planning it’s very own roadmap

We hope you do enjoy the new improved features in NearBeach 0.14 branch. This does come with the issue that we have extended this cycles development time by an extra month.


Bug Fixes

BUG333 – Email in plain text
BUG356 – Failure to create new Project
BUG353 – Failure to create new opportunity
BUG355 – Failure to feedback when updating.
BUG359 – Naming convention
BUG358 – No feedback when completing Project/Task creation
BUG343 – Can not create project for customer without organisation
BUG351 – Failure to create new Project


Future NearBeach

We are hoping to have a sit down meeting soon and start planning road map. There will be new requirements mapped out and we will be keeping you in the loop. If you are interested you will be able to view our JIRA account at https://nearbeach.atlassian.net.

New Site – New Future

The issue with data migrating from one server to another in the cloud space is sometimes, something has to give. It was either my sanity or the previous posts of NearBeach. I took the latter as the former had already gone years before hand.

There is good news in between all this migration, we are now hosted on Digital Ocean who were kind to us and gave us $100 credit which will help with most of the web server needs for most of the year. The other good news is that we have done a thorough bug testing and released our first stable version 0.14.0 the other day.

The bad news is that due to this data migration and a few personal things, we are going to be spending a few months on really polishing NearBeach. We want to be able to present a product that will help you, and we need to fix any and ALL bugs in the system. So for the next 6 weeks we will be on a bug fixing sprint, and then back to normal after that.