To request a feature, first look at the Feature Development Queue to see if the feature has already been developed or requested. If the feature is not already available or in the development queue, then submit the feature request using the Feature Request Form. Please use a descriptive title and provide a brief explanation that includes the problem the feature is intended to solve. Please include technical requirements, examples, etc. if you have them. The feature request is saved in the UWS development queue as “pending”. UWS reviews feature requests on a weekly basis and will contact you for additional information if needed.
UWS reviews new feature requests on a weekly basis. UWS will consolidate features requests if the functionality of a new feature request overlaps with an existing request. If the feature is technical possible and hasn’t already been developed, they will change the status from “1. Proposed” to “2. In Queue”. If the feature request is considered critical, UWS will notify SDAT via email with a version release recommendation and proposed release date. If it is not critical, SDAT will prioritize features on a monthly basis.
Once a set of issues and features have been tested on the staging server and approved for the production server, the UWS Web Developer sends the Review and Release Date Communication to the SDAT Group and UWS Support Team announcing the launch date and requesting feedback within 4 days. The UWS Web Developer also schedules a meeting with the support team that day to train them on the new features.
Once the support team is familiar with the new functionality they create a print and web based training guide for each feature, craft a feature release announcement that will be sent to the UCD website users email list and posted on the UWS website that briefly explains why the features were developed, how it benefits the users and when they will be released and schedules classroom training sessions to train users on the new features.