- Issue created by @speckles
- π¨π¦Canada speckles
Note - when I edited a Contact and tested the telephone field on it I saw the same behaviour
- πΊπΈUnited States bluegeek9
Are you using the latest dev release?
This sounds very similar to π Error prevents adding phone number to contact Active
- π¨π¦Canada speckles
No - I checked out a smoke test branch to keep things consistent while I was planning out smoke tests.
I would argue that "The telephone widget can become a second address widget if there's an error", as shown in my screenshot, counts as a new bug however. I'm okay if the resolution is Do Not Fix, but having a discussion thread someone can find if the problem pops up again because of a new error still seems worthwhile to me.
- πΊπΈUnited States bluegeek9
No - I checked out a smoke test branch to keep things consistent while I was planning out smoke tests.
You should only report bugs after you have confirmed it exists in the latest dev branch, and have not already been reported.
- π¨π¦Canada speckles
This bug would not happen in the latest branch since it's a bug in how the system responds when the form has a bug. You would have to modify the code to throw an error in the same place that was fixed to recreate the bad behaviour
Like I said before, maybe it's better to just leave the landmine in the code until the next bug happens. But it is problematic error handling behaviour.
- πΊπΈUnited States jdleonard Austin, TX, USA
When there are errors and AJAX involved, sometimes weird stuff happens. I don't think that's something that CRM can reasonably control. But certainly any bug that's caused by CRM should have an issue filed.
I'll echo @bluegeek9 that potential bugs should be verified against the latest dev branch (note that's what the Version field's "1.0.x-dev" value represents) prior to being created as an issue. This allows maintainers to focus on actionable issues.
Setting status to reflect that this can't be reproduced in the latest dev branch.