Display booked consultation hours in portfolio for other users

1 Initial Problem

Booked consultation hours are displayed in the portfolio if you are either the consultation hour provider or the one who booked the consultation hour. "This is the behaviour since 5.1 and earlier (Statement S.M."
But other people don't see that there was originally an appointment to book.
In the calendar view, however, booked appointments are still displayed, they only can no longer be booked.

We would like to streamline the behavior as the maintainer suggested in this bug report: Mantis, because users who are not members of courses are often irritated when no appointments are displayed in the portfolio. (All appointments are booked).

2 Conceptual Summary

The booked consultation hours should be displayed as in the course calendar view. There should be also an Option to show/hide booked out appointments.

3 User Interface Modifications

3.1 List of Affected Views

•  "Consultation Hours" on the portfolio page for users other than the C.H. provider and the one who booked the consultation hour.
• Portfolio --> INSERT CONSULTATION HOURS
• Portfolio --> EDIT CONSULTATION HOURS

3.2 User Interface Details

•  "Consultation Hours" on the portfolio page: same as calandar view:

Mockups

• Portfolio --> INSERT CONSULTATION HOURS & EDIT CONSULTATION HOURS: Enhancement by the option to display the booked consultation hours or not. Add:
  • Booked consultation hours are displayed to other users as booked.
  • Booked consultation hours are not displayed to other users.

Mockups

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this.}

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Strassner, Denis [dstrassner]
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• PH Freiburg

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.