As KirstinI want to see when the last manual watering event was performed over the website
to guess when I need to perform the next watering event.
AC
I get a feeling of when I need to come back to the website to perform a new watering action.
UAT
[x] Show an icon to make clear that the following text will show the last watering action
[x] Show more that just the timestamp of the last watering action. Make it more tangible for the use. Which means show words like "recently" or minutes, hours, days or so.
[x] Set up a feature toggle to enable the feature on test but not on production but do the integration test on the production page at the same time.
[x] Set up a sub php file to catch the latest timestamp of the manual watering event and post this timestamp flat on the index page.
[x] Check how long the last watering event has been passed and distinguish between minutes, hours and days by displaying these timestamp values.
[x] Embed an icon to make the last watering event visually obvious.
[x] Add the styling of the timestamp in the table to the main stylesheet file
Refactoring tasks
[x] Create a overall php file that contains all the written texts in one file as constants to make overall changes more easy
[x] Include the background color choice in a separate php file to call it in production and test to make color changes available in test and production immediately
[x] Include the font color choice in a separate php file to call it in production and test to make the color changes available in test and production immediately
[x] Change the current php calls to php function calls to simply return the value of the function based on input data
[ ] Let the timestamp of the plantlog database table be defined by the database and not by the php insert statement
[x] Show the specific date for watering events that lay longer then one week in the past from #82
[x] Show the specific day for watering days that lay one week in the past from #81
[x] If the measure of the moisture drops it should not increase again to avoid false alarm. Sure the moisture should increase after a watering event. Maybe we can use thresholds for increased moisture from #80
The idea here is that we later want to announce somewhere that the moisture dropped below a specific value and I want to avoid that the value was reset to a point where you cannot perform a watering action when you actually look at the message that told you to water the plant.
As Kirstin I want to see when the last manual watering event was performed over the website to guess when I need to perform the next watering event.
AC I get a feeling of when I need to come back to the website to perform a new watering action.
UAT