User feedback and ideas are crucial for improving G.J. Software for all G.J. Gardner Homes franchises. This article outlines the process for submitting feature requests directly through the application and provides tips for making requests clear and impactful.
Steps to Submit a Feature Request
Follow these steps to submit a new feature idea or vote on existing ones:
Click the Help icon within the G.J. Software application.
Click Send request to support. A new window will open.
Scroll down to the section labelled Add your voice.
Review existing requests:
The screen displays feature requests submitted by other users.
Users can filter requests by rating, status, or category (e.g., Builder Portal, Website).
Use the search bar to find specific requests.
Users can view notifications and status updates for features previously submitted or voted on.
Check for similar existing ideas:
To add a new idea, click the plus icon (+).
Select the relevant category.
Begin typing a title for the request. As the user types, the system suggests similar existing ideas.
Vote or comment on an existing idea:
If a similar idea already exists, click the vote button next to it.
Click the idea title to open it and add a comment with specific context or reasons. Adding votes and comments helps prioritize requests and ensures the user receives status updates.
Submit a new idea:
If no similar idea exists, continue creating the new request after typing the title.
Note: Submitting or commenting may require the user to log in with their Google account.
Accessing the feedback portal directly:
Once logged in, users can also view the product roadmap and feedback board directly.
The Feedback section allows users to view, filter, and search existing ideas, as well as add a new feature request using the same process described in steps 5-7.
Note: You can also view the list of requests or submit your ideas to feedback.gjgardner.com.
Tips for Effective Feature Requests
To help the development team understand and evaluate suggestions, please consider the following when submitting a request:
Be Clear and Specific: Describe exactly what is needed. Instead of general statements like "Improve reports," specify the report name and the desired change (e.g., "Add a 'Client Email' column to the 'Jobs in Progress' report"). Use examples where possible.
Explain the "Why" - Describe the Problem: Detail the problem the feature solves. Explain the pain point in the current workflow and provide context (e.g., "Manually looking up client emails for the 'Jobs in Progress' report takes significant time.").
Describe the "Who" - Who Benefits?: Indicate which role(s) (e.g., estimator, supervisor, administrator) would primarily benefit from the feature.
Highlight the Value or Benefit: Explain how the feature would help (e.g., save time, reduce errors, improve client communication, enhance financial oversight). Quantify the benefit if possible (e.g., "This could save approximately 30 minutes per day.").
Focus on One Idea Per Request: Submit multiple suggestions as separate requests for easier tracking and prioritization.
Check if it Already Exists: Before submitting, search or browse existing requests. Voting and commenting on an existing idea strengthens its visibility.
(Optional) Suggest a Solution: While users can suggest how a feature might work, the primary focus should be on the problem and the value of solving it.
Following these tips helps the team understand the impact of ideas and evaluate them for the future roadmap.
Feature Request Template
To help structure feedback, consider using the following format when adding a comment to an existing idea or submitting a new one:
Template: As a [Your Role, e.g., Estimator, Administrator, Site Supervisor], I want [Describe the action or feature needed], so that [Explain the benefit or value this provides].
Example:
Title: Add client email column to Jobs in Progress report
As an Administrator, I want to see the client's email address as a column in the 'Jobs in Progress' report grid, so that I can quickly contact clients about their jobs without having to look up their details separately, saving time and reducing potential delays.
Tips for using this format:
Role: Be specific about who primarily benefits.
Action/Goal: Clearly state the desired capability or outcome.
Benefit/Value: Explain why this is important – what problem does it solve, or what improvement does it offer?
This format helps the development team quickly understand the user's perspective and the core value of the requested feature.