Supermedic (talk | contribs) No edit summary |
Supermedic (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
In Virginia we have adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following. | In Virginia we have adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following. | ||
==== 1 ==== | ==== Day 1 ==== | ||
Within 24 hours (1 day) after an Update Request has been submitted, an editor needs to provide a response to the Update Request to get the process started. | Within 24 hours (1 day) after an Update Request has been submitted, an editor needs to provide a response to the Update Request to get the process started. | ||
==== 4 ==== | ==== Day 4 ==== | ||
If the reporter has not commented back within the next 3 days (day 4 since submitted) a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue. | If the reporter has not commented back within the next 3 days (day 4 since submitted) a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue. | ||
"If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon" | "If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon" | ||
==== 8 ==== | ==== Day 8 ==== | ||
If the reporter still has not commented after 3 more days (8 days since submitted) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified. | If the reporter still has not commented after 3 more days (8 days since submitted) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified. | ||
"This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!" | "This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!" | ||
Revision as of 20:10, 17 January 2015
Update Requests
An Update Request (UR) is a Map Issue reported by a user from the Waze client app. It is also a layer in the Map Editor. See update requests for more information.
In Virginia we have adopted at 1/4/8 system for response to Update Requests. 1/4/8 is the short way of explaining the following.
Day 1
Within 24 hours (1 day) after an Update Request has been submitted, an editor needs to provide a response to the Update Request to get the process started.
Day 4
If the reporter has not commented back within the next 3 days (day 4 since submitted) a message should be sent reminding the reporter that we need more information about the problem they encountered to fix the issue. "If no further information is provided we will be unable to fix the issue you encountered and this report will be closed soon"
Day 8
If the reporter still has not commented after 3 more days (8 days since submitted) a message should be sent telling the reported that we were unable to fix the problem and this report is being closed. The Update Request then needs to be closed as Not Identified. "This report is being closed due to lack of information, please submit another report if the issue continues. Happy Wazing!"