You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the current, policy does not dictate how long a reasonable timeframe should be on replies.
There is also a distinct lack of prior rulings and how finer processes should be done. However, these are meant to be guiding policies at the outset, and not straight up rules - though that can certainly be arranged.
The text was updated successfully, but these errors were encountered:
A reasonable time frame for replies from both the assignees & the issue raiser should be 1 working day from the time that the issue is raised.
If either side do not respond within the time frame, it is the responsibility of the other party to bump it. With this, if there is still no response, the issue will be closed, and the unresponsive party will be responsible for their actions.
If there is no bump, the issue is assumed to have been resolved.
With this requirement, clubs are also mandated to raise requests for locked rooms to be opened minimally 2 working days before the requested date.
To add on, depending on type of request, we can have the window for the room to be open varied.
For example, if the request of simply to open for retrieval of items, a time frame of 1 hour should be more than sufficient, unless there are specific reasons for the room to be open for a longer frame of time.
An example of a larger frame of time for the room to be open, would be for users to do stock take, or hand/takeover, which might require more than an hour.
At the current, policy does not dictate how long a reasonable timeframe should be on replies.
There is also a distinct lack of prior rulings and how finer processes should be done. However, these are meant to be guiding policies at the outset, and not straight up rules - though that can certainly be arranged.
The text was updated successfully, but these errors were encountered: