WorkingHours version: 2.8.14
OS + version: macOS 12.4
There is some strange behavior in the way that the Working Time, Start/End of Work fields update each other when their values change.
Currently, if one shrinks the timespan that's defined by the Start/End of Work fields, the Working Time field will update accordingly. However, if one expands the timespan, the Working Time field remains static.
Likewise, if one increases the Working Time value, the Start of Work field moves backwards in time in response to the greater number of hours. However, if one sets a smaller Working Time value, neither the Start nor End of Work fields respond to the change.
This may be intended behavior; however, I believe it might make more sense for all the fields to update according to each other. This then begs the question of which field should move, Start or End? While my preference is for the End to update to changes made to the Working Time field, I could see it being someone else's preference for the Start to be adjusted. At which point, it might be worth making it a user preference to specify which field changes.
Like I said, it's possible this is all intended, but I wanted to report it just in case because, as a first-time user, it did throw me off when creating work units.