Scheduling meetings
Find a time that suits the participants, for example for a user acceptance test session. The server proposes times and a person confirms one.
This page applies to every stage.
Page in the app: /p/{projectId}/scheduling
From request to meeting
The test cycle date follows the confirmed time.
- Request. Start it from a test cycle and name the participants.
- Search. The server reads availability and proposes up to five times.
- Confirm. A person chooses one time. Nothing is chosen for you.
- Invitation. The event goes to the calendar, or an invitation file is sent.
How to do it
- Start from the test cycle. Open an acceptance test cycle and select Schedule UAT session. Add the people who must attend.
- Read the availability. Working hours only means the calendar of that person was not read. Their busy times are not known.
- Confirm a time. Choose one of the proposed times and confirm it. If none suits, ask for new times.
- Watch for moved events. If someone moves the event in the calendar, the organiser sees the change and accepts it or not.
Good to know
- Without a connected calendar the invitation is a file. Download it and check the replies by hand.
- If this page is missing, your administrator has not switched calendar access on.
Related topics
Based on the IFS Implementation Docs Kit (IDK-01 to IDK-24), described in our own words.
Last updated: