central-queensland-uni / moodle-local_extension Goto Github PK

Currently there is a new date for an extension request that is shown on an individual status page;

This date also needs to be added to the status list page after the Request length as "New due date";

Currently it is too easy to accidentally approve or deny a request, add an intermediate confirmation page.

• Year filter
• Status filter
• Filter based on text in shortname, group by faculty.

Could we have the request length in days added to the individual request like it is shown on the extension status page.

The first 4 letters for a unit code do not make up a course. For example CG99 is a course that includes a lot of the COIT units but will also contain some units from the other unit categories. Can we have the course filter renamed to Unit Category and Unit to Unit Code.

Can we change My courses to My units.

Currently picking a new due date will validate that this date is past the original due date and is in the future.

Students can put in an extension request for the past, so this validation should only validate that the new due date is after the original.

• sort the list after the regex loop

Bonus points:

• add select optgroups grouped by the first letter

With some trigger setups there may be tiers of access between roles.

When an extension moves to the approved state, only then will the hook fire off to set the extension in the required module.

If the date has been modified post extension approval, additional triggers will be fired off based on the rules that have been configured. The module will not activate the hook to further extend, as mentioned before it is only fired in the approved state.

So as someone with the correct level of access and updating the extension length the system is to:

• Create a new state, 'Modified', when the time is changed it will be placed in this modified state.
• The extension date is not changed from if it was previously in an approved state.
• Currently the code will fire off the subscription triggers to recalculate the rules.
• So if someone cancels the modification, nothing happens. Original approval date still applies.
• If cancelled, restore previous access levels to other roles?
• If the modified state has been accepted, then apply the new extension date.

When looking at an extension request, there is no cancel button to go back to the extension status page. The only way to go back is by the breadcrumbs.

To prevent abuse limit the length that a user can make a request for.

Make sure the user provides an attachment with supporting documentation for making a request.

The comment that is recorded truncates the length to the largest unit.

An update of 1 day 1 hour will display the length is 1 day.

ie if I go to a course I am not enrolled in:

As an approver, documents cannot be added to a request. (Sometimes they need to do this on behalf of the student).

• Provide request user to cancel their own request
• Refactor state machine

• Use table_lib and make it sortable
• add course filter
• add course cateogry filter
• add text search on first name last name idnumber
• add column for course
• add column for module
• add last modified by who (got this already?)
• new capability to show all requests, not just the subscribed requests

Create three admin configuration options that when enabled can limit the scope with how requests can be made.

• Site request
• Course request
• Module request
• Implement the scoping
• Modify rendered output providing links to individual requests

You are still provided a link but instead of showing the request page you are provided a list of links to the request page for a single module.

When a user has the viewallrequests permission but is not in the subscription list by the triggers, they receive the requested file could not be found error.

This is suspected to be an issue around line 197 of the lib.php file where the permission is not taken into consideration.

Create a new template similar to {{course-role-xxxx}} that provides a list of users in the scope of that course with the role designated as xxxx.

It currently defaults to the courseid parameter that is passed to filer the table entries.
Rather it should reference the course that is associated to the request cm item.

When modifying the extension length, the cancel button does not work and only refreshes that page

See: https://docs.moodle.org/dev/Event_2

• Add the two configuration items
• Implement the content on the request page
• Implement the content on the status page

If someone is not part of the request user list, but has the capability 'local/extension:viewallrequests' after adding content to the request they will be added to the list of users.

The following check to determine their level of access will terminate loading of the page.
eg. /modify.php:52 and 60.

When adding a comment to an extension request, the profile picture looks as if it is detached from the text area (giving it the appearance it is mistakenly there)

When approving a request, the user is returned to the extension request approved instead of the extension status page

• Change Request ID => ID
• ID as first element.
• Request Date => Created Date
• Add request length.
• Add status column.
• Last updated by => Time since lastmod
• Shorten timestamps

Maybe other states too.

A possible bug has been raised.

So a request can come in for 13 days, student asks for 3 more days
Coordinator makes it 16 days (above their 14 days they can approve), but because the triggers might not happen for a few minutes, the coordinator can approve that 16 days

As a student, cancelling a request before it has been approved or denied states that they do not have permission to do it.

Interleave comments based on timestamp.

The students or staff cannot get back to their course easily as the breadcrumbs change to be the assignment extension breadcrumbs (only way back is by the browser back button)

Whenever the student creates a request, the attached file is shown twice, and there are two entries per request. Then after it is approved, the approval shows two entries about it being approved. This is a very confusing screen – can this please be simplified?

• The formatted extension policy text is not printed as HTML
  
  

• Extension policy for request is displayed when the Extension policy for status text should be