Feature Request

Setup Information Feature Request

Introduction

A Feature Request is a suggestion made by a user or stakeholder for a new functionality or an enhancement to an existing system or software product.

Feature requests can come from internal teams, customers, or third-party partners, and they serve as a critical source of information for future product development.

In our system, feature requests are categorized and managed to ensure that the most relevant, valuable, and feasible features are prioritized.

Feature Request Submission

1. Login to your account.
2. Navigate to Setup Information Feature Request.
   
   
3. Click on the blue + button. When submitting a request, users need to provide:
   1. Title: A brief, descriptive name for the feature request.
   2. Description: A detailed explanation of the feature request, including its purpose and how it will benefit users or improve the system.
      
      
      
4. Let’s now take a closer look at the key features of this integration:
   
   
   
   1. Search Bar: Allows users to search for specific feature requests by name or description. This makes it easier to find relevant requests from a large pool.
   2. Filter: Help users efficiently organize and view tasks or feature requests based on specific criteria:
      1. Task Filter: Choose from All Tasks, My Tasks, or Other Tasks to focus on specific task sets.
      2. Status Filter: Allows filtering by task status: Open, Pending, In Progress, Completed, In Review, Documentation, or Accepted.
      3. Sort By: Newest First (default), Oldest First, Most Liked, Most Votes, or alphabetical sorting (A-Z or Z-A) based on task titles.
   3. Feature Request Overview:
      1. Title: The name or title of the feature request. This is a short, descriptive label for the requested feature.
      2. Description Box: This is the detailed explanation of the feature request
      3. Status: Displays the current status of the feature request. Common statuses include:
         1. Open: The feature request is currently being reviewed or is in progress.
         2. In Progress: The feature is actively being worked on or developed.
         3. Completed: The feature has been fully implemented and is live.
         4. Closed: The feature request has been resolved, but no further action is necessary.
   4. Reply: Users can add comments or feedback to the request.
   5. Like: Users can express their interest in the feature request by "liking" it. This helps prioritize the most requested features.
   6. Post Comment: After writing a comment in the "Write a comment" section, users can click this button to submit their feedback or additional information.
   7. Upvote: When a user upvotes a feature, it indicates support for the request or idea, signaling that they find it valuable or necessary.
   8. Downvote: When a user downvotes a feature, it indicates disapproval or that they do not find the request valuable.
   9. Ticket Details panel displays basic info about the feature request, including Created By, Created On, Votes, and Likes, while the Comments Section allows users to add feedback, view all comments, and engage in discussions.

Some inportant notes

1. Features with the highest number of votes will be prioritized for implementation.
2. The final decision regarding feature changes or adjustments will be made by the team.
3. All feature requests will be visible to all customers.