Step 1

Determine if the feature request is really a new idea. The feature may already be available in a current public release of ResVu, a new upcoming release, or have been raised by someone else. The support team can confirm this for you through the chat

If you can find the feature request listed on https://roadmap.resvu.com.au/, you can leave a comment to expand on the details and/or vote for that feature to show it’s a priority for you.

Remember: When searching, commenting on and posting feature requests, be sure to use ResVu terminology.

Step 2

Can your suggestion be broken down into multiple smaller – yet beneficial – feature requests? If yes, then it is better to do this as it can make scheduling the requests easier and allows others to vote on the parts that are important to them.

You can always explain in the description the related feature requests that together provide further benefit.

Step 3

Determine the appropriate ResVu component (e.g., CommunitiLink, Company Dashboard, FMLink) to raise the feature request against. While this may be obvious in most cases, some features impact multiple ResVu components, so it is best to raise this against the component that has the administrative configuration capabilities and mention in the request details of other components impacted.

For example, any feature request for Alerts could either be for the Company Dashboard or the Admin Console. When creating the request it should go against the component that you want it changed for. If you want it changed for both components you will need to raise 2 change requests.

Note: if you have a feature request around the ResVu Feature Request system itself, please raise this direct with the third-party vendor at https://feedback.upvoty.com/b/feature-requests-1/

Step 4

When you have determined in which Board to raise the request, select that Board and you will see the widget on the left that allows you to submit a feature.

Pro tip: Whilst you can directly enter the title and details, it is highly recommend that you write the details in an application such as Microsoft Word as the user interface can be maximised.

You can then select the text in the application and copy it to the clipboard and paste it into the Title and Details fields.

Step 5

Enter a short descriptive title: start by showing the location as this help provide context when looking at a list of all features and assists with searching. Then use > as a separator before defining the goal of the feature request.

For Example if you wanted to add a feature request for Notices in the Admin console you would have "Admin Console > Communicate: Allow scheduling of Notices"

Pro tips: try to keep the word limit to a maximum of eight and avoid abbreviations.

Step 6

Enter in the details with the following headings as appropriate, and in the following order. Click here for a template you can copy directly as a starting point.

Goal

Start with a clear goal statement that expands on the abbreviated title to provide more clarity on the end goal of the feature. Reasons we recommend starting with the goal are:

• It directly relates to the title, and helps you keep the title shorter

• The reader ideally wants to be clear on your goal before they continue reading further into the request, as this will help them better understand the current limitation, examples, location, and steps, etc.

This is typically a sentence or a paragraph.

Current

Depending on the nature of your feature, it can be helpful to provide some background context on the current situation regarding limitations with an existing feature and/or reasons why the feature is needed.

Note: you may want to include examples at this point to help illustrate the limitation/reason.

Location

Providing the navigation pathway to the location of a feature can be helpful. For example:

Admin Console > Communicate > Notice > Create Notice > Visibility > Schedule

Steps / enhancements

If you can breakdown your feature request into a series of steps that you would imagine taking to action the new feature, use the STEPS heading and list them as this helps others follow your thought process with the potential solution.

Otherwise simply use the enhancement heading and describe your potential solution.

Related requests

Given there might be other related requests, this provides a way to reference those for those reading that may wish to look at any items that expand on functionality further. You can use this approach so that you keep each individual request short and relevant so that it does not grow unnecessarily and allows everyone to vote on the individual requests as is important to them.

Note: the Relates requests heading is also a good one to use in Comments, so if you read someone else’s request and want to expand on the functionality, you can raise your own that expands on it, and put in the RELATED REQUESTS as a comment on the original.

Attach any screenshots or diagrams to illustrate. Accepts gif/jpg/png 4MB maximum.

Pro tip: Write the details in an application such as Microsoft Word as the user interface can be maximised. You can then select the text in the application and copy it to the clipboard and paste it into the Details field.

Warning

Please be aware that all posts and comments to this system are visible to other members of the ResVu community. ResVu is not responsible for posts and/or comments made by ResVu community members. ResVu reserves the right to moderate and/or remove your posts and comments. All parties should ensure they abide by the data and privacy policies defined by their respective countries.

Next steps

Did this answer your question?