Status and Priority definitions for Feature Requests
Once you submit a Feature Request through our https://3yourmind.atlassian.net/servicedesk/customer/portal/37, a ticket will be generated into our Service Desk. In order for you to stay up to date and understand the progress of your request, Table 1 below shall explain the meaning of each status a ticket may have.
Also, tickets' priority is related to the impact a certain feature (or lack thereof) has on your intended use of the software. As such, it is important that priorities are assigned correctly, as per definitions on Table 2.
Status | Meaning |
Open | Newly submitted request. Our team has not reviewed the ticket yet. |
Investigation | Our team has started investigating the requested feature. They will evaluate potential solutions, efforts required and prioritize accordingly. Status will be updated once the investigation is completed. |
Planned | The requested feature is planned to be addressed within the existing roadmap (i.e., within this year). The ticket will provide more information about the estimated completion date. |
In Progress | The requested feature is currently under development. |
Review | The requested feature is implemented, released and available for testing. |
Closed | The requested feature has been fulfilled and completed. |
On-Hold | The requested feature is valid but cannot be prioritized in our existing roadmap (i.e., within this year). The team will reconvene before the end of the year to re-evaluate. |
Rejected | The requested feature cannot be implemented in the foreseeable future. |
Priority | Meaning |
Blocker | Current problem makes it impossible to proceed with using the software |
Critical | Incorrect functioning of a particular area of business-critical software functionality |
Major | Significant impact on an application, but other inputs and parts of the software remain functional, so it still usable |
Minor | A confusing defect that causes undesired behavior but doesn’t affect user experience significantly |