Forum Discussion

tbarth's avatar
tbarth
Contributor 3
10 days ago

Why is Property Name missing in add/edit property? (It's visible in client edit view.)

When viewing a client's properties on the Client page, I noticed that the left column is oddly empty:

Clicking the + New Property button or clicking on an existing property and clicking the Edit button opens a dialog with the following fields:

However, clicking on the Edit button for the client, scrolling down to the Property address section, and clicking the Add Another Address button, a dialog opens with an additional field, Property name:

Adding a property name displays that info in the left column of the property list on the client's page:

This seems like the intended functionality because:

  • Assigning names to properties makes working with multiple properties much easier.
  • The feature is already built into the product and should be fully functional.

So, to fix the missing data field in this dialog:

  • Typing ~5 lines of existing syntax
  • 10-15 minutes of testing
  • Minimal time for code review / QA sign-off
  • Deploy in the next scheduled update

It seems extremely unlikely I am the first to report this, yet I first raised this issue nearly five months ago and was told the feature was not implemented, even though it is clearly used elsewhere, showing it is intentional and fully functional. I followed up three and a half months ago with the exact code showing how simple the fix is. From my experience across the software production cycle, this is a simple functional omission bug: a UI regression that hides an already implemented feature and disrupts user workflow. The fix is trivial and low-risk. Realistically, from checkout to review, QA sign-off, and deployment, it requires maybe 60-90 minutes of human time. Can you confirm whether this fix is scheduled to be made, and if so, when it will be applied?

Thank you.

1 Reply

  • krista's avatar
    krista
    Jobber Support Team

    Hi tbarth​,

    Thank you for taking the time to lay this out so clearly, and for documenting the workflow in detail. I can see why this feels inconsistent, especially since the Property Name field appears in one workflow but not in another. That would definitely be confusing when managing multiple properties.

    I really appreciate the thought you have put into outlining what you believe is happening and how it could be resolved. While I cannot speak to the specific development effort or timelines, I will absolutely pass this feedback along to our Product and Development teams for review. The context you provided around usability and workflow impact is especially helpful.

    I cannot confirm if or when a change would be scheduled, but feedback like this does get reviewed and helps inform prioritization decisions, and I will make sure it gets in front of the right people. 

    Thanks again for raising it and for the detailed breakdown.