Update released
Japanese and other multibyte text is now handled by visible character count — and project / sprint date ranges are validated more reliably across all edit paths.
📝 Text limits now match the characters you see
Until now, Lasimban’s character limits were evaluated in bytes under the hood. That meant text rich in multibyte characters — Japanese kanji, Vietnamese diacritics, Tagalog accents — would sometimes refuse to save even though the visible character count was still under the limit. This release switches the counting to codepoints (the characters you actually see).
The documented limits themselves haven’t changed, but because each kanji now counts as one character instead of three bytes, you can comfortably write longer project names, sprint goals, and descriptions in any of our supported languages.
🗓 Stricter consistency checks for project and sprint dates
When you updated only the start date or only the end date of a project or sprint, we weren’t merging the change with the existing value before validating — so a one-sided update could quietly save a range where the end date came before the start. This release fixes that path: one-sided date updates are now validated against the existing field on the other side.
We also closed a couple of smaller gaps, such as a silent skip of ScrumTeam name length checks on certain update paths. A few previously-accepted inputs will now surface as errors, but those were the kinds of inputs that quietly broke dashboard and analytics rendering downstream — so this is a healthy correction.
📮 Contact us
If you have any questions or feedback, please don’t hesitate to reach out.
- ✉️ Email: info@on-your-side.llc