instruction
stringclasses 1
value | input
stringlengths 61
6.42k
| solvability
stringclasses 2
values | output
stringlengths 60
70.4k
| text
stringlengths 715
71.3k
|
|---|---|---|---|---|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle Community Sites 3.0.3 upgrade
description: Moodle 3.0.3 scheduled release: Monday 14 March 2016
| Unsolvable | 1.summary: Upgrade moodle.org to 3.0.3
description:
2.summary: Upgrade learn.moodle.net to 3.0.3
description:
3.summary: Upgrade lang.moodle.org to 3.0.3
description:
4.summary: Upgrade school.demo.moodle.net to 3.0.3
description:
5.summary: Upgrade demo.moodle.net to 3.0.3
description:
6.summary: Upgrade dev.moodle.org to 3.0.3
description:
7.summary: Upgrade moodle.net to 3.0.3
description:
8.summary: Upgrade moodlemoot.org sites to 3.0.3
description:
9.summary: Upgrade download.moodle.org to 3.0.3
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle Community Sites 3.0.3 upgrade
description: Moodle 3.0.3 scheduled release: Monday 14 March 2016
### Response:
1.summary: Upgrade moodle.org to 3.0.3
description:
2.summary: Upgrade learn.moodle.net to 3.0.3
description:
3.summary: Upgrade lang.moodle.org to 3.0.3
description:
4.summary: Upgrade school.demo.moodle.net to 3.0.3
description:
5.summary: Upgrade demo.moodle.net to 3.0.3
description:
6.summary: Upgrade dev.moodle.org to 3.0.3
description:
7.summary: Upgrade moodle.net to 3.0.3
description:
8.summary: Upgrade moodlemoot.org sites to 3.0.3
description:
9.summary: Upgrade download.moodle.org to 3.0.3
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Moodle configurations
description: Administrators should be able to enable/disable features/plugins easily to simplify their Moodle sites. In order to achieve that, there are a few things that can be done: Switch easily between different Moodle configurations (without changing settings manually, one at a time). Reword some features, to make it easier for users to find/use them. Make "Enable xxxx" features more consistent: add them into the "Advanced features" page and then only display the Site administration menus when there are enabled. EDIT 21 Sep 2021 For new sites we should consider defaulting to the simplified Moodle configuration. We will need some sort of notification for admins (could even be a simple msg) to let them know this and that they can unlock the full feature set (with link to setting).
| Unsolvable | 1.summary: Ideas for simplifying the badge page
description: The current badge page in Moodle has a lot of unnecessary text, such as headings (Recipient details, Issuer details, Badge details, Badge expiry), subheadings (Name, Description), Users are awarded this badge... and This badge was issued for completing.... Also, Criteria and Evidence are almost the same (see attached current badge page example). How about if we simplify the page to make it more attractive and easier to read? Something like... quote . Course 101 course badge Badge name Awarded to Sam Student Issued on 15 June 2021 Badge description... Criteria Any of the following .... have to be completed: Criterion 1 Criterion 2 Issued by Issuer quote (See attached improved badge page example.) Thus we would remove headings - Recipient details, Issuer details, Badge details, Badge expiry subheadings - Name, Issuer name, Contact, Language, Description, Course, Date issued, Evidence texts Users are awarded this badge... and This badge was issued for completing... The title of the page would be Course name course badge or Site name site badge. The page would have Badge name and Criteria as subheadings. If additional badge details (version, language, image authors name etc) are supplied, the info could be displayed at the bottom of the badge page in a small font size.
2.summary: Integrate admin_presets third-party plugin in Moodle LMS
description: As an admin I want to load administration presets So I can easily switch between different configurations This feature is implemented by the third-party plugin "Admin presets": created by David Monlla and maintained by developers from Pimenko| This issue is about adapting this third-plugin for getting it integrated into Moodle LMS. . Acceptance criteria: The block should be converted from a block to an admin tool. PoC A link "Site admin presets" (pointing to 3rd-party plugin main page) should be displayed in the Site administration. The admin tool should follow the Moodle coding style and policy rules. For instance, these are some of the things to review: Some classes should have a proper namespace (for instance, the ones in the lib folder). They should also probably be moved to the classes folder. The Auto exclude sensitive settings setting should be checked by default. The tool_admin_presets setting should be reviewed to confirm it includes all the sensitive settings that have been added recently. Presets should also include plugins visibility, let admins export/preview/load the list of plugins and their visibility. Moodle LMS should include, by default, 2 different flavours in the Admin presets tool: one for "Starter" and another for "Full" --> ^preinstalled_adminpresets.png: "Starter" will disable most of the settings and plugins in order to make it easier for users to find the most common features. "Full" will include settings and plugins configuration after installing a vanilla Moodle. For new sites, we should consider defaulting to the simplified Moodle configuration. We will need some sort of notification for admins (could even be a simple msg) to let them know this and that they can unlock the full feature set (with link to setting). . Technical information The element will be added to the XML file following this format: code:java Demo preset file 1625551825 Admin User 2021070100 4.0dev (Build: 20210701) ... 5 ... 0 1 0 1 0 ... 0 0 ... 1 0 0 code The following tables should be added to store the plugins data: tool_admin_presets_plug tool_admin_presets_app_plug
3.summary: Add feature to import/export plugins visibility from Admin presets tool
description: As an admin I want to import/export plugins visibility So I can easily switch between different configurations . Acceptance criteria A new section, Modules , should be added to the form to let admins export/preview/load the list of plugins and their visibility. !modules_adminpresets_form.png|thumbnail! Admins should be able to choose the plugins they want to import/export plugins visibility (the similar as they can do right now with "Admin presets" settings). . Technical information The element will be added to the XML file following this format: code:java Demo preset file 1625551825 Admin User 2021070100 4.0dev (Build: 20210701) ... 5 ... 0 1 0 1 0 ... 0 0 ... 1 0 0 code The following tables should be added to store the plugins data: tool_admin_presets_plug tool_admin_presets_app_plug
4.summary: Include pre-installed admin presets
description: As an admin I want to change the Moodle site settings and plugins So I can easily switch between lite and full Moodle configuration . Acceptance criteria: Moodle LMS should include, by default, 2 different flavours in the Admin presets tool: one for "Lite Moodle" and another for "Full Moodle". Lite Moodle will disable most of the settings and plugins in order to make it easier for users to find the most common features. Full Moodle will include settings and plugins configuration after installing a vanilla Moodle. !preinstalled_presets.png|thumbnail!
5.summary: Rename "Miscellaneous" category to "Category 1"
description: Rename the "Miscellaneous" category to Category 1 and set the description field to HTML format (not Moodle auto format).
6.summary: Remove from Dashboard some of the current blocks
description: Remove from Dashboard for all users the following blocks: Online users Upcoming events Learning plans Recently accessed courses
7.summary: Rename "HTML block" to the more easily understood "Text block"
description: Rename the "HTML" block to something easier to understand such as "Text", "Content" or similar.
8.summary: Make Enable xxxxx features consistent (hide menus for disabled features)
description: The default behaviour for most of the advanced features (Badges, Analytics) is to display menus in Site administration only when they are enabled. However, some cases (like Competencies), have a separate menu that is displayed always (regarding the feature is enabled or not), because the setting to enable/disable it is defined there. This issue is about moving the "Enable xxxx" feature to the "Advanced features" page to guarantee the menus are only displayed when the feature is enabled.
9.summary: Simplifying the external badge page
description: This is a follow-up of , to review and simplify too the badges page for displaying external badges and making consistent both pages.
10.summary: Change default value of "Hidden sections" course format setting
description: This setting is found on "Course settings / Course format / Hidden sections" !Screenshot 2021-09-29 at 16.21.46.png|width=606,height=171! The default value for this setting is "Hidden sections are shown in collapsed form", which can be very disorienting for new users. They expect hidden sections to be completely hidden from students as the default behavior. I suggest changing the default value to "Hidden sections are completely invisible". Edited to add: In addition to changing the default, the fix for this issue also changes the wording of the option Hidden sections are completely invisible to Hidden sections are shown as not available to match 4.0 behaviour.
11.summary: Add generic enable_plugin() method in plugininfo
description: While working in to add support to bulk enable/disable plugins Ive realised there is no method in the plugininfo API to enable/disable plugins. This issue is to add the enable_plugin($pluginname, $enabled) method to core_plugininfo\base and implement it in all the plugins supporting the enabled/disabled feature.
12.summary: Add a $CFG setting to define the preset to be installed
description: Add a mechanism, such as a setting $CFG in the config.php file, to let admins define the preset to be installed by default when the installer will be executed.
13.summary: Store the latest site admin preset applied
description: As Eloy suggested in , it would be good to store the "latest/current" preset applied: both when a preset is applied to a live site and when a preset is configured for the installation. It will probably help, in the future, to add new and interesting features and improvements to the site admin preset plugin.
14.summary: Remove unused functions at adminpresets component and admin_presets admin tool
description: Reviewing we realized thanks to rezaie9 that some of the functions integrated in core are not used. In the original admin_presets plugin there was a tree-view setting list. During the integration of the plugin we decided to get rid of the tree-view for now, and add it again as a follow-up in . But some of the functions that were used to create that tree-view have been integrated into core, but never used. We probably would need to work on those functions in a different way for so those unused functions such as get_description() should be removed.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Moodle configurations
description: Administrators should be able to enable/disable features/plugins easily to simplify their Moodle sites. In order to achieve that, there are a few things that can be done: Switch easily between different Moodle configurations (without changing settings manually, one at a time). Reword some features, to make it easier for users to find/use them. Make "Enable xxxx" features more consistent: add them into the "Advanced features" page and then only display the Site administration menus when there are enabled. EDIT 21 Sep 2021 For new sites we should consider defaulting to the simplified Moodle configuration. We will need some sort of notification for admins (could even be a simple msg) to let them know this and that they can unlock the full feature set (with link to setting).
### Response:
1.summary: Ideas for simplifying the badge page
description: The current badge page in Moodle has a lot of unnecessary text, such as headings (Recipient details, Issuer details, Badge details, Badge expiry), subheadings (Name, Description), Users are awarded this badge... and This badge was issued for completing.... Also, Criteria and Evidence are almost the same (see attached current badge page example). How about if we simplify the page to make it more attractive and easier to read? Something like... quote . Course 101 course badge Badge name Awarded to Sam Student Issued on 15 June 2021 Badge description... Criteria Any of the following .... have to be completed: Criterion 1 Criterion 2 Issued by Issuer quote (See attached improved badge page example.) Thus we would remove headings - Recipient details, Issuer details, Badge details, Badge expiry subheadings - Name, Issuer name, Contact, Language, Description, Course, Date issued, Evidence texts Users are awarded this badge... and This badge was issued for completing... The title of the page would be Course name course badge or Site name site badge. The page would have Badge name and Criteria as subheadings. If additional badge details (version, language, image authors name etc) are supplied, the info could be displayed at the bottom of the badge page in a small font size.
2.summary: Integrate admin_presets third-party plugin in Moodle LMS
description: As an admin I want to load administration presets So I can easily switch between different configurations This feature is implemented by the third-party plugin "Admin presets": created by David Monlla and maintained by developers from Pimenko| This issue is about adapting this third-plugin for getting it integrated into Moodle LMS. . Acceptance criteria: The block should be converted from a block to an admin tool. PoC A link "Site admin presets" (pointing to 3rd-party plugin main page) should be displayed in the Site administration. The admin tool should follow the Moodle coding style and policy rules. For instance, these are some of the things to review: Some classes should have a proper namespace (for instance, the ones in the lib folder). They should also probably be moved to the classes folder. The Auto exclude sensitive settings setting should be checked by default. The tool_admin_presets setting should be reviewed to confirm it includes all the sensitive settings that have been added recently. Presets should also include plugins visibility, let admins export/preview/load the list of plugins and their visibility. Moodle LMS should include, by default, 2 different flavours in the Admin presets tool: one for "Starter" and another for "Full" --> ^preinstalled_adminpresets.png: "Starter" will disable most of the settings and plugins in order to make it easier for users to find the most common features. "Full" will include settings and plugins configuration after installing a vanilla Moodle. For new sites, we should consider defaulting to the simplified Moodle configuration. We will need some sort of notification for admins (could even be a simple msg) to let them know this and that they can unlock the full feature set (with link to setting). . Technical information The element will be added to the XML file following this format: code:java Demo preset file 1625551825 Admin User 2021070100 4.0dev (Build: 20210701) ... 5 ... 0 1 0 1 0 ... 0 0 ... 1 0 0 code The following tables should be added to store the plugins data: tool_admin_presets_plug tool_admin_presets_app_plug
3.summary: Add feature to import/export plugins visibility from Admin presets tool
description: As an admin I want to import/export plugins visibility So I can easily switch between different configurations . Acceptance criteria A new section, Modules , should be added to the form to let admins export/preview/load the list of plugins and their visibility. !modules_adminpresets_form.png|thumbnail! Admins should be able to choose the plugins they want to import/export plugins visibility (the similar as they can do right now with "Admin presets" settings). . Technical information The element will be added to the XML file following this format: code:java Demo preset file 1625551825 Admin User 2021070100 4.0dev (Build: 20210701) ... 5 ... 0 1 0 1 0 ... 0 0 ... 1 0 0 code The following tables should be added to store the plugins data: tool_admin_presets_plug tool_admin_presets_app_plug
4.summary: Include pre-installed admin presets
description: As an admin I want to change the Moodle site settings and plugins So I can easily switch between lite and full Moodle configuration . Acceptance criteria: Moodle LMS should include, by default, 2 different flavours in the Admin presets tool: one for "Lite Moodle" and another for "Full Moodle". Lite Moodle will disable most of the settings and plugins in order to make it easier for users to find the most common features. Full Moodle will include settings and plugins configuration after installing a vanilla Moodle. !preinstalled_presets.png|thumbnail!
5.summary: Rename "Miscellaneous" category to "Category 1"
description: Rename the "Miscellaneous" category to Category 1 and set the description field to HTML format (not Moodle auto format).
6.summary: Remove from Dashboard some of the current blocks
description: Remove from Dashboard for all users the following blocks: Online users Upcoming events Learning plans Recently accessed courses
7.summary: Rename "HTML block" to the more easily understood "Text block"
description: Rename the "HTML" block to something easier to understand such as "Text", "Content" or similar.
8.summary: Make Enable xxxxx features consistent (hide menus for disabled features)
description: The default behaviour for most of the advanced features (Badges, Analytics) is to display menus in Site administration only when they are enabled. However, some cases (like Competencies), have a separate menu that is displayed always (regarding the feature is enabled or not), because the setting to enable/disable it is defined there. This issue is about moving the "Enable xxxx" feature to the "Advanced features" page to guarantee the menus are only displayed when the feature is enabled.
9.summary: Simplifying the external badge page
description: This is a follow-up of , to review and simplify too the badges page for displaying external badges and making consistent both pages.
10.summary: Change default value of "Hidden sections" course format setting
description: This setting is found on "Course settings / Course format / Hidden sections" !Screenshot 2021-09-29 at 16.21.46.png|width=606,height=171! The default value for this setting is "Hidden sections are shown in collapsed form", which can be very disorienting for new users. They expect hidden sections to be completely hidden from students as the default behavior. I suggest changing the default value to "Hidden sections are completely invisible". Edited to add: In addition to changing the default, the fix for this issue also changes the wording of the option Hidden sections are completely invisible to Hidden sections are shown as not available to match 4.0 behaviour.
11.summary: Add generic enable_plugin() method in plugininfo
description: While working in to add support to bulk enable/disable plugins Ive realised there is no method in the plugininfo API to enable/disable plugins. This issue is to add the enable_plugin($pluginname, $enabled) method to core_plugininfo\base and implement it in all the plugins supporting the enabled/disabled feature.
12.summary: Add a $CFG setting to define the preset to be installed
description: Add a mechanism, such as a setting $CFG in the config.php file, to let admins define the preset to be installed by default when the installer will be executed.
13.summary: Store the latest site admin preset applied
description: As Eloy suggested in , it would be good to store the "latest/current" preset applied: both when a preset is applied to a live site and when a preset is configured for the installation. It will probably help, in the future, to add new and interesting features and improvements to the site admin preset plugin.
14.summary: Remove unused functions at adminpresets component and admin_presets admin tool
description: Reviewing we realized thanks to rezaie9 that some of the functions integrated in core are not used. In the original admin_presets plugin there was a tree-view setting list. During the integration of the plugin we decided to get rid of the tree-view for now, and add it again as a follow-up in . But some of the functions that were used to create that tree-view have been integrated into core, but never used. We probably would need to work on those functions in a different way for so those unused functions such as get_description() should be removed.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.4.2 upgrade
description: Moodle 3.4.2 is scheduled for release on Monday 12 March 2018.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.4.2
description:
2.summary: Upgrade learn.moodle.net to 3.4.2
description:
3.summary: Upgrade lang.moodle.org to 3.4.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.4.2
description:
5.summary: Upgrade demo.moodle.net to 3.4.2
description:
6.summary: Upgrade moodle.net to 3.4.2
description:
7.summary: Upgrade download.moodle.org to 3.4.2
description:
8.summary: Upgrade dev.moodle.org to 3.3.5
description: We still did not get to either closing, or properly upgrading the site to latest 3.4. So lets keep it at least patched for security issues.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.4.2 upgrade
description: Moodle 3.4.2 is scheduled for release on Monday 12 March 2018.
### Response:
1.summary: Upgrade moodle.org to 3.4.2
description:
2.summary: Upgrade learn.moodle.net to 3.4.2
description:
3.summary: Upgrade lang.moodle.org to 3.4.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.4.2
description:
5.summary: Upgrade demo.moodle.net to 3.4.2
description:
6.summary: Upgrade moodle.net to 3.4.2
description:
7.summary: Upgrade download.moodle.org to 3.4.2
description:
8.summary: Upgrade dev.moodle.org to 3.3.5
description: We still did not get to either closing, or properly upgrading the site to latest 3.4. So lets keep it at least patched for security issues.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Quiz Module Improvements
description: Some changes need to be focused for Quiz Activity.
| Unsolvable | 1.summary: Add palate to quiz to identify answered and unanswered questions
description: in quiz when we have to jump in any question questions are set in a single line. can it optimized like web. with palate attached. it should differentiated like color:rednot answeredcolor, answered, color:redmarkedcolor, color:14892cnot visitedcolor, color:654982marked and answeredcolor with different colors. on quiz player two options should be available in button format like color:redmark for reviewcolor, color:redsave & Nextcolor.
2.summary: each question in quiz can be commented in review
description: student can comment on questions in the quiz after quiz is completed so that he can ask his doubts at that instant. as teachers answers his question that comments will be accessible to other students. i have seen plugin like this. but the question created can not be imported or exported in this plugin. can this be included in moodle core. !q.PNG!
3.summary: Support quiz reports on the mobile app
description: it will be nice to add graphical result after quiz is completed as already implemented in Feedback module. Graphical quiz result is possible in moodle core.
4.summary: Redefine quiz navigation and quiz statistics in moodlemobile
description: If quiz is attempted ,Moodle mobile not shows skipped questions. we should able to flag question. Quiz report should show number of skipped questions , number of attmped questions. Report should contain average time to complete quiz, and accuracy percentage for attempted questions. This analysis will be very helpful to the students to perform better. Follow discussion here|
5.summary: Allow users to flag question during quiz attempt
description: Allow users to flag question during attempt so that student can flag question and review during attempt. this feature is available in moodleweb.
6.summary: Create quiz statistics for better usability
description: Show quiz statistics to user, like number of questions attempted, Number of Questions per Hour (to measure Speed) number of questons skipped, amount of time for each answer (Time Report for evry question)(on preview page) . so that user understand his weakness.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Quiz Module Improvements
description: Some changes need to be focused for Quiz Activity.
### Response:
1.summary: Add palate to quiz to identify answered and unanswered questions
description: in quiz when we have to jump in any question questions are set in a single line. can it optimized like web. with palate attached. it should differentiated like color:rednot answeredcolor, answered, color:redmarkedcolor, color:14892cnot visitedcolor, color:654982marked and answeredcolor with different colors. on quiz player two options should be available in button format like color:redmark for reviewcolor, color:redsave & Nextcolor.
2.summary: each question in quiz can be commented in review
description: student can comment on questions in the quiz after quiz is completed so that he can ask his doubts at that instant. as teachers answers his question that comments will be accessible to other students. i have seen plugin like this. but the question created can not be imported or exported in this plugin. can this be included in moodle core. !q.PNG!
3.summary: Support quiz reports on the mobile app
description: it will be nice to add graphical result after quiz is completed as already implemented in Feedback module. Graphical quiz result is possible in moodle core.
4.summary: Redefine quiz navigation and quiz statistics in moodlemobile
description: If quiz is attempted ,Moodle mobile not shows skipped questions. we should able to flag question. Quiz report should show number of skipped questions , number of attmped questions. Report should contain average time to complete quiz, and accuracy percentage for attempted questions. This analysis will be very helpful to the students to perform better. Follow discussion here|
5.summary: Allow users to flag question during quiz attempt
description: Allow users to flag question during attempt so that student can flag question and review during attempt. this feature is available in moodleweb.
6.summary: Create quiz statistics for better usability
description: Show quiz statistics to user, like number of questions attempted, Number of Questions per Hour (to measure Speed) number of questons skipped, amount of time for each answer (Time Report for evry question)(on preview page) . so that user understand his weakness.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Allow users to resize images in atto
description: Being able to resize the images from within the editor.
| Solvable | 1.summary: Atto: Allow users to resize images in atto
description: Being able to resize the images from within the editor.
2.summary: Atto: Remove atto-image-helper- class(es) when necessary.
description: One of the use of is to hide the original while resizing or add a border styling while resizing. These are accomplish by attaching classes to images (or other html elements) that is under a css rule. For instance: code:title=demo.css|borderStyle=solid atto-helper-border border: 1px solid black; code code:title=demo.html|borderStyle=solid code The problem arises when save/autosave kicks in, saving unwanted styling. For instance, the border that is only intended as a helper will be saved. To solve this, I will need to point you to the attos clean.js (found in atto javascript source files). It contains getCleanHTML which is called before save/autosave. So what needs to be done is remove all classes that starts with "atto-helper" so that styles attached to "atto-helper-" classes are not saved. This is a perfect solution since it goes with the name of the function getCleanHTML, that is, the intended html.
3.summary: Atto: Add hook to allow atto plugins to clean up after themselves.
description: The image plugin needs to clean up after itself on save. We should allow all plugins to do this by creating a generic hook that can be utilised, rather than altering core atto code for a specific plugin.
4.summary: Atto: Add hook to allow atto plugins to filter elements from being cleaned of style and class attributes
description: Currently, atto cleans all style and class attribute (from copied content) when pasting without a way of inserting exceptions.
5.summary: Atto: Move the trigger for the htmlcleaned hook
description: added a hook atto:htmlcleaned for the purpose of cleaning html during save/autosave. Save/autosave calls getCleanHTML where atto:htmlcleaned is fired. A problem occured when we want to clean up content during paste event, which doesnt call getCleanHTML. To fix this, move the firing of atto:htmlcleaned to _cleanHTML where both save/autosave and paste event calls.
6.summary: Atto: Enable image alignment using existing atto_align plugin.
description: Currently, atto_align directly writes to imgs style attribute. This is working now that we wrapped the image with 2 wrappers (one for rotate and another for crop). To fix this attach event handlers to atto_aligns buttons and handle the alignment inside atto_image.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Allow users to resize images in atto
description: Being able to resize the images from within the editor.
### Response:
1.summary: Atto: Allow users to resize images in atto
description: Being able to resize the images from within the editor.
2.summary: Atto: Remove atto-image-helper- class(es) when necessary.
description: One of the use of is to hide the original while resizing or add a border styling while resizing. These are accomplish by attaching classes to images (or other html elements) that is under a css rule. For instance: code:title=demo.css|borderStyle=solid atto-helper-border border: 1px solid black; code code:title=demo.html|borderStyle=solid code The problem arises when save/autosave kicks in, saving unwanted styling. For instance, the border that is only intended as a helper will be saved. To solve this, I will need to point you to the attos clean.js (found in atto javascript source files). It contains getCleanHTML which is called before save/autosave. So what needs to be done is remove all classes that starts with "atto-helper" so that styles attached to "atto-helper-" classes are not saved. This is a perfect solution since it goes with the name of the function getCleanHTML, that is, the intended html.
3.summary: Atto: Add hook to allow atto plugins to clean up after themselves.
description: The image plugin needs to clean up after itself on save. We should allow all plugins to do this by creating a generic hook that can be utilised, rather than altering core atto code for a specific plugin.
4.summary: Atto: Add hook to allow atto plugins to filter elements from being cleaned of style and class attributes
description: Currently, atto cleans all style and class attribute (from copied content) when pasting without a way of inserting exceptions.
5.summary: Atto: Move the trigger for the htmlcleaned hook
description: added a hook atto:htmlcleaned for the purpose of cleaning html during save/autosave. Save/autosave calls getCleanHTML where atto:htmlcleaned is fired. A problem occured when we want to clean up content during paste event, which doesnt call getCleanHTML. To fix this, move the firing of atto:htmlcleaned to _cleanHTML where both save/autosave and paste event calls.
6.summary: Atto: Enable image alignment using existing atto_align plugin.
description: Currently, atto_align directly writes to imgs style attribute. This is working now that we wrapped the image with 2 wrappers (one for rotate and another for crop). To fix this attach event handlers to atto_aligns buttons and handle the alignment inside atto_image.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Users can search across federated instances.
description: Users can search across federated instances.
| Solvable | 1.summary: Test approaches to SEO
description: This could be useful for SEO of any back-end generated pages:
2.summary: Add search box to top bar
description: The new top bar navigation should include a search box to allow users to search their own instance, but also contented from other federated instances.
3.summary: Investigate Algolia for search
description: See:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Users can search across federated instances.
description: Users can search across federated instances.
### Response:
1.summary: Test approaches to SEO
description: This could be useful for SEO of any back-end generated pages:
2.summary: Add search box to top bar
description: The new top bar navigation should include a search box to allow users to search their own instance, but also contented from other federated instances.
3.summary: Investigate Algolia for search
description: See:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.2.1 upgrade
description: Moodle 3.2.1 scheduled release date: 9 January 2017
| Unsolvable | 1.summary: Upgrade moodle.org to 3.2.1
description:
2.summary: Upgrade learn.moodle.net to 3.2.1
description:
3.summary: Upgrade lang.moodle.org to 3.2.1
description:
4.summary: Upgrade school.demo.moodle.net to 3.2.1
description:
5.summary: Upgrade demo.moodle.net to 3.2.1
description:
6.summary: Upgrade dev.moodle.org to 3.2.1
description:
7.summary: Upgrade moodle.net to 3.2.1
description:
8.summary: Upgrade download.moodle.org to 3.2.1
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.2.1 upgrade
description: Moodle 3.2.1 scheduled release date: 9 January 2017
### Response:
1.summary: Upgrade moodle.org to 3.2.1
description:
2.summary: Upgrade learn.moodle.net to 3.2.1
description:
3.summary: Upgrade lang.moodle.org to 3.2.1
description:
4.summary: Upgrade school.demo.moodle.net to 3.2.1
description:
5.summary: Upgrade demo.moodle.net to 3.2.1
description:
6.summary: Upgrade dev.moodle.org to 3.2.1
description:
7.summary: Upgrade moodle.net to 3.2.1
description:
8.summary: Upgrade download.moodle.org to 3.2.1
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: 3.11 Student activity completion follow ups
description: This epic will contain follow up issues related to the 3.11 MUA Student activity completion project|
| Unsolvable | 1.summary: Analyse 3.11 performance
description: During the code freeze for 3.11, some performance errors were raised (, ). They started when landed. Right now they are not easy to reproduce in a clean instance but a real investigation should be done to see if performance can be improved. So this issue is to compare and analyse 3.10 vs 3.11 or 2 months ago vs current as a whole thing.
2.summary: Review activity completion visualization with classic
description: Just upgraded one of my dev sites (using classic) and course page is showing as follows: !classic_before.png|thumbnail! 1) The condition texts seem too big (compared with boost). 2) The "Mark as done" dimmed elements are really annoying, almost doubling the vertical space needed, although, you know, thats a very-personal opinion. 3) Im not an activity-completion expert... so if you find any other related thing worth fixing with classic... surely this is the issue to review and fix them. Ciao :-)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: 3.11 Student activity completion follow ups
description: This epic will contain follow up issues related to the 3.11 MUA Student activity completion project|
### Response:
1.summary: Analyse 3.11 performance
description: During the code freeze for 3.11, some performance errors were raised (, ). They started when landed. Right now they are not easy to reproduce in a clean instance but a real investigation should be done to see if performance can be improved. So this issue is to compare and analyse 3.10 vs 3.11 or 2 months ago vs current as a whole thing.
2.summary: Review activity completion visualization with classic
description: Just upgraded one of my dev sites (using classic) and course page is showing as follows: !classic_before.png|thumbnail! 1) The condition texts seem too big (compared with boost). 2) The "Mark as done" dimmed elements are really annoying, almost doubling the vertical space needed, although, you know, thats a very-personal opinion. 3) Im not an activity-completion expert... so if you find any other related thing worth fixing with classic... surely this is the issue to review and fix them. Ciao :-)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Forum Accessibility issues.
description: This epic is related to accessibility issues in the Forum activity.
| Unsolvable | 1.summary: Forum: Improve structure of forum post HTML
description: HTML structure of a forum post can be improved. Improvements: 1. Use tag to mark it correctly. 2. Use tag to include the real datetime information. 3. Use tag to specify who and when the post came from. 4. Use heading level tags to mark the subject of each post. 5. Properly nest reply posts within their parent 6. Use a header tab for each article to split the metadata from the content. 7. Use CSS to separate links, not text content.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Forum Accessibility issues.
description: This epic is related to accessibility issues in the Forum activity.
### Response:
1.summary: Forum: Improve structure of forum post HTML
description: HTML structure of a forum post can be improved. Improvements: 1. Use tag to mark it correctly. 2. Use tag to include the real datetime information. 3. Use tag to specify who and when the post came from. 4. Use heading level tags to mark the subject of each post. 5. Properly nest reply posts within their parent 6. Use a header tab for each article to split the metadata from the content. 7. Use CSS to separate links, not text content.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: New Report builder reports for 4.3
description: Collect together any new report sources and/or system reports for Moodle 4.3 See previous epic for 4.2 () - we have a lot of custom reports and entities that should make conversion of some existing reports to system reports very straight forward Those entities can also be re-used in existing custom reports to give more indepth reports to users
| Unsolvable | 1.summary: Create a custom report filter on context level
description: Allow for custom reports to filter by contextlevel, for those reports that include context data (e.g. comments| files| tags| One use case would be to allow a report to be created to list all files at a certain level, e.g. in any user context, and allow for reporting on that To avoid copying around the same solution in each report source, create a new context entity type and deprecate existing columns in lieu of the new entity (requires to be implemented to allow for deprecation) The new entity will also provide the base for additional context data (path/parent), which will enhance the files report source later in
2.summary: Implement columns for completion criterias
description: As noted by ilyatregubov in : "Still looking into a code, but just following tests instruction make me wonder if having just Required course grade column will confuse teachers. I.e. a course have prerequisite to complete assignment and get 80 grades. So on the current implementation we can have a student who achieved required Course grade but wont complete a course and there wont be a way to know from report why he hasnt complete it. May be we need to either show all conditions or not showing Required course grade column at all?" And also subsequent comments from Paul and Helen.
3.summary: Add tag support to badges custom report source
description: Once lands, update the badges custom report sources ( & ) to support tag data (as per user/course reports in )
4.summary: Implement default report sorting in all report sources
description: Use new API from , to implement the same in all existing report sources (only a few were updated as part of that task) Ensure that the default sorting for each is appropriate, and accompanying unit tests also take it into account. We can also remove code blocks such as this| that account for undefined sorting of default reports during tests Also linking to in order to add sorting to existing stress tests
5.summary: Create a report builder filter for "enrolment name"
description: In the report builder Id like the option to create a condition/filter where I can see the custom name of the enrolment instance. This is really convenient when working with a lot of LTI consumers. You can easily create reports for the consumer with only their users.
6.summary: Separate course participant enrol/role elements to new report entities
description: The course participants report source () introduced some new entities, one of which was the enrolment entity| The entity refers to "User enrolment" data, but also squashes in some elements that really belong in their own entities: Enrolment method column| and filter| should both belong to an enrol entity; Role column| should belong to a role entity - this would also normalize the JOINs on this column and remove redundancy/duplication on the context table In doing so, well create clearer reporting with more in-depth data on both enrolment methods and/or roles. The role entity specifically is required for . Columns Enrolment method Plugin Name Enabled Duration Start End Role Name Short name Description . Filters/Conditions Enrolment method Plugin Enabled Duration Start End Role Name Note that this issue should also introduce an API to allow for old report elements (columns, filters) to be deprecated Existing elements already present should display in the report as normal, and emit debugging; They should not be listed in the report editor to allow for selection in new reports Also discovered while looking at this - setting it as blocker because itll make the debugging less noisy and allow for easier debug assertions in tests
7.summary: Create "Course categories" custom report source
description: This is similar to the original "Courses" report source from , but the primary table will be the categories table and itll report on data specific to them . Columns Course category Course count Course Cohort Role (see ) User . Filters Course category Course Cohort Role User . Conditions Course category Course Cohort Role User
8.summary: Include custom fields in cohort report entity
description: See - once this is landed, ensure that custom fields for cohorts are available for reporting !Screenshot 2023-04-06 at 17-02-58 Cohort (Custom fields).png!
9.summary: Include user in custom report for comments on blog entries
description: As noted when testing the 4.1 improvements for report builder - if you make a report on blog entries, with associated comments, you can include the blog posters name and the time the entry was created. But for any comments, you can only include the time created and not the name of the person who wrote the comment. However - the users name does appear if you simply run a report on all comments. Pinging pholden to whom I mentioned this.
10.summary: Expose contenthash value in files report entity
description: Improve the files report source () to allow reporting/filtering on the file contenthash property, in order to allow for the detection of multiple uses of the same file across the site Currently we can report and aggregate on all file data, but it doesnt account for the fact that the Files API de-duplicates files| when they are uploaded to multiple contexts/components (causing them to be counted multiple times in custom reports). The contenthash value (both as a column and filter) will aid reporting for administrators
11.summary: Allow reporting/filtering on context path and parent
description: Once we have landed, and we have a dedicated entity for context data, we should expand that to allow reporting on: Path (Column/Filter) Parent (Column) This will enhance the _Files_ report source, and allow for the creation of reports that can go towards answering the question "How much disk space does my course take up?" This appears to be a popular request:
12.summary: Course participants report source should show active enrolments by default
description: The course participant report source should by default show _participants_ (hence the name) - we can improve the default state by adding the following condition: Enrolment > Status = Active The default report created by the report will therefore show only courses and active user enrolments (instead of listing all enrolment methods present in the course, regardless of whether they have any related user enrolments) We can also improve the report source by implementing default sorting
13.summary: Support "not" / inversion of category conditions in report builder
description: At present the custom report builder allows for the selection of a category, but it does not support a mechanism to select course that are not in the selected category (and sub-categories), which would be helpful as the condition also does not support the selection of multiple categories.
14.summary: Add search and filter function in Manage Badges page
description: We work with alot of SystemBadges. Currently we have created and published 500 unique badges. Managing that many badges is not very user friendly in Moodle. Reason /badges/index.php?type=1 Gives only filter on NUMBER of total pages. Suggestion / Improvement Search field for badges Filter on LETTER Filter on STATUS (lets you select out of the availible statusses)
15.summary: Include custom fields in report group/grouping entities
description: See - once this is landed, ensure that custom fields for both groups and groupings are available for reporting Much like we did with cohorts recently ()
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: New Report builder reports for 4.3
description: Collect together any new report sources and/or system reports for Moodle 4.3 See previous epic for 4.2 () - we have a lot of custom reports and entities that should make conversion of some existing reports to system reports very straight forward Those entities can also be re-used in existing custom reports to give more indepth reports to users
### Response:
1.summary: Create a custom report filter on context level
description: Allow for custom reports to filter by contextlevel, for those reports that include context data (e.g. comments| files| tags| One use case would be to allow a report to be created to list all files at a certain level, e.g. in any user context, and allow for reporting on that To avoid copying around the same solution in each report source, create a new context entity type and deprecate existing columns in lieu of the new entity (requires to be implemented to allow for deprecation) The new entity will also provide the base for additional context data (path/parent), which will enhance the files report source later in
2.summary: Implement columns for completion criterias
description: As noted by ilyatregubov in : "Still looking into a code, but just following tests instruction make me wonder if having just Required course grade column will confuse teachers. I.e. a course have prerequisite to complete assignment and get 80 grades. So on the current implementation we can have a student who achieved required Course grade but wont complete a course and there wont be a way to know from report why he hasnt complete it. May be we need to either show all conditions or not showing Required course grade column at all?" And also subsequent comments from Paul and Helen.
3.summary: Add tag support to badges custom report source
description: Once lands, update the badges custom report sources ( & ) to support tag data (as per user/course reports in )
4.summary: Implement default report sorting in all report sources
description: Use new API from , to implement the same in all existing report sources (only a few were updated as part of that task) Ensure that the default sorting for each is appropriate, and accompanying unit tests also take it into account. We can also remove code blocks such as this| that account for undefined sorting of default reports during tests Also linking to in order to add sorting to existing stress tests
5.summary: Create a report builder filter for "enrolment name"
description: In the report builder Id like the option to create a condition/filter where I can see the custom name of the enrolment instance. This is really convenient when working with a lot of LTI consumers. You can easily create reports for the consumer with only their users.
6.summary: Separate course participant enrol/role elements to new report entities
description: The course participants report source () introduced some new entities, one of which was the enrolment entity| The entity refers to "User enrolment" data, but also squashes in some elements that really belong in their own entities: Enrolment method column| and filter| should both belong to an enrol entity; Role column| should belong to a role entity - this would also normalize the JOINs on this column and remove redundancy/duplication on the context table In doing so, well create clearer reporting with more in-depth data on both enrolment methods and/or roles. The role entity specifically is required for . Columns Enrolment method Plugin Name Enabled Duration Start End Role Name Short name Description . Filters/Conditions Enrolment method Plugin Enabled Duration Start End Role Name Note that this issue should also introduce an API to allow for old report elements (columns, filters) to be deprecated Existing elements already present should display in the report as normal, and emit debugging; They should not be listed in the report editor to allow for selection in new reports Also discovered while looking at this - setting it as blocker because itll make the debugging less noisy and allow for easier debug assertions in tests
7.summary: Create "Course categories" custom report source
description: This is similar to the original "Courses" report source from , but the primary table will be the categories table and itll report on data specific to them . Columns Course category Course count Course Cohort Role (see ) User . Filters Course category Course Cohort Role User . Conditions Course category Course Cohort Role User
8.summary: Include custom fields in cohort report entity
description: See - once this is landed, ensure that custom fields for cohorts are available for reporting !Screenshot 2023-04-06 at 17-02-58 Cohort (Custom fields).png!
9.summary: Include user in custom report for comments on blog entries
description: As noted when testing the 4.1 improvements for report builder - if you make a report on blog entries, with associated comments, you can include the blog posters name and the time the entry was created. But for any comments, you can only include the time created and not the name of the person who wrote the comment. However - the users name does appear if you simply run a report on all comments. Pinging pholden to whom I mentioned this.
10.summary: Expose contenthash value in files report entity
description: Improve the files report source () to allow reporting/filtering on the file contenthash property, in order to allow for the detection of multiple uses of the same file across the site Currently we can report and aggregate on all file data, but it doesnt account for the fact that the Files API de-duplicates files| when they are uploaded to multiple contexts/components (causing them to be counted multiple times in custom reports). The contenthash value (both as a column and filter) will aid reporting for administrators
11.summary: Allow reporting/filtering on context path and parent
description: Once we have landed, and we have a dedicated entity for context data, we should expand that to allow reporting on: Path (Column/Filter) Parent (Column) This will enhance the _Files_ report source, and allow for the creation of reports that can go towards answering the question "How much disk space does my course take up?" This appears to be a popular request:
12.summary: Course participants report source should show active enrolments by default
description: The course participant report source should by default show _participants_ (hence the name) - we can improve the default state by adding the following condition: Enrolment > Status = Active The default report created by the report will therefore show only courses and active user enrolments (instead of listing all enrolment methods present in the course, regardless of whether they have any related user enrolments) We can also improve the report source by implementing default sorting
13.summary: Support "not" / inversion of category conditions in report builder
description: At present the custom report builder allows for the selection of a category, but it does not support a mechanism to select course that are not in the selected category (and sub-categories), which would be helpful as the condition also does not support the selection of multiple categories.
14.summary: Add search and filter function in Manage Badges page
description: We work with alot of SystemBadges. Currently we have created and published 500 unique badges. Managing that many badges is not very user friendly in Moodle. Reason /badges/index.php?type=1 Gives only filter on NUMBER of total pages. Suggestion / Improvement Search field for badges Filter on LETTER Filter on STATUS (lets you select out of the availible statusses)
15.summary: Include custom fields in report group/grouping entities
description: See - once this is landed, ensure that custom fields for both groups and groupings are available for reporting Much like we did with cohorts recently ()
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: BigBlueButton New Features and Improvements for 4.1
description: There are several new features and improvements that were postponed after BBB was integrated into core. This is the follow-up issue for tracking all the development looking forward to Moodle 4.1.
| Unsolvable | 1.summary: New capability to hide statistics from students
description: Hey jfederico! It would be great if the plugin had a moodle native capability to suppress the statistics function from a role.
2.summary: Provide a way for teachers to invite external participants (guests)
description: It would be nice for Teachers to be able to invite external teachers. The Best way would be to implement it like in greenlight: You enable the link in the module settings. If you are a teacher you get an invite link on the module page you can simply copy.
3.summary: Pick BBB UI language from Moodle user profile language instead of preferred browser language 205
description: In reference to GitHub issue 205| Reported as: According to the BBB documentation and according to my tests, the BBB UI language is chosen based on the preferred browser language. For the Moodle integration of BBB, I would like to propose to pick the BBB UI language based on the Moodle user profile language instead. This will help users who are working on a computer which does not have their main language as browser language set, but who have set the right language in their Moodle user profile. As always, this should be configurable with an admin setting to support the existing as well as the new behaviour. Development notes: As it is right now, the BBB API does not support language overriding. See GitHub Issue 10085| Once that is implemented this new feature would be tribial as we would only need to pass a lang parameter on join.
4.summary: Close meetings when removing BBB activity
description: Im not sure if this is really desirable, or open meetings should go on running although the BBB activity is deleted. bigbluebuttonbn_delete_instance (mod/bigbluebuttonbn/lib.php) loops over the course groups to delete a possible existing meeting for each group. It uses the groups_get_course_group function which only returns the active group, not all groups in the course.
5.summary: Add role parameter, phase out moderatorPW and attendeePW from create, and password from join
description: Since version 2.4, BBB can use a parameter that defines the role to be used in the BBB session instead of the so called password with is problematic with modern browsers. To give a bit of context, the so called `password` used in the URL in plain text is not a real password, but a token or identifier to be used to define the role a user should have in a meeting. The URLs used by BBB are in some way protected by a hash calculated using a shared secret. Therefore, `password` would not (should not and could not) be used for authenticating the user. The idea is that - create would no longer include modPW nor viewerPW, - join will use instead of password the designated role, such as role=moderator|viewer See We will not be removing the password currently, but only adding the role parameter. Phasing out of password use will most likely take place in BBB v2.6
6.summary: Add a way to filter out special formats other than statistics
description: . Special formats in the newest version. What are they? Special formats are recording formats that are produced in BBB for being shared differently. The best example is statistics, a format that should only be accessed by the Teacher because it comes with all the details of usage in the meeting. There are however other formats offered by custom BBB deployments (BBB recordings are meant to be extended by community). In fact, any other format could (and should) be treated as an special case in some cases. What is the problem? Only statistics is considered an special format and it is hard-coded. Who can access them? Users who have the capability mod/bigbluebuttonbn:managerecordings will be the only ones who can see it. By default only Editing Teachers and Admins do. How was done before? In previous versions, there was a setting to define what formats should be ruled out from Teachers, and also a setting to define the roles that would have access to them. How should it be? Since this is an authorisation, using the mod/bigbluebuttonbn:managerecordings makes sense. So admins and any other role or user with this capability enabled should be able to access "Special formats" But, there should be a way to define which are those special formats. Either through settings or env variable. But it should never be hard-coded. An alternative is to use the same payload to differentiate which ones are special and which ones are not. Although this is not an standard characteristic of BBB recordings.
7.summary: Add a parameter to set the polling value for the live session/wait for moderator
description: When the user waits for another to join the session or the session is opened from another user, then in the meantime we have to poll BBB server to retrieve its status. Best here would be to have a setting that can be changed and allow to poll more or less frequently (and lower the server load for example). To make it more parameterised (from 5 to 10) Maybe add some sort of visual information so the user know that something is happening (a countdown ?).
8.summary: Add role parameter, phase out moderatorPW and attendeePW from create, and password from join in 4.0
description: Since version 2.4, BBB can use a parameter that defines the role to be used in the BBB session instead of the so called password with is problematic with modern browsers. To give a bit of context, the so called `password` used in the URL in plain text is not a real password, but a token or identifier to be used to define the role a user should have in a meeting. The URLs used by BBB are in some way protected by a hash calculated using a shared secret. Therefore, `password` would not (should not and could not) be used for authenticating the user. The idea is that - create would no longer include modPW nor viewerPW, - join will use instead of password the designated role, such as role=moderator|viewer See We will not be removing the password currently, but only adding the role parameter. Phasing out of password use will most likely take place in BBB v2.6
9.summary: BigluebuttonBN outline display is a bit too verbose
description: During the development of the fix for we noticed that the outline report for user activity is a bit too verbose for the module. The aim of this ticket is to find a way to display all necessary information to the user without being too detailed.
10.summary: Remove the lockonjoin settings
description: As per , we decided to: 1. To remove the setting "lock on join" so it is not optional, 2. And to hard-code the lockonjoin=true parameter on create when any of the lock settings is used. Background information: The issue turned out to be the user missing to check the "lock on join" box. When that happens, the lockonjoin value assumed by BBB will be whatever value the BBB server has by default, in this case false. This means that the locks are applied in the meeting but not to all the users on join. We (the integrators) are still not clear what is the intention for that in BBB, but for the purposes of the Moodle user experience, because the use case.
11.summary: Recordings synchronisation : warn user when cron is disabled or not working
description: We are seeing more an more complains about the recordings not showing up because cron is disabled. It is OK, we knew that and the documentation is already there. BUT, chatting with other folks from the BBB community, one suggested to warn system administrators if cron is not enabled. Two directions : some sort of state (perhaps the status itself), passing from AWAITING to PROCESSING when the task is scheduled, and only passing it to PROCESSED when it finishes. As per the cron not enabled, there is a warning on the notification page when it has not run for more than x minutes, we might be able to replicate this.
12.summary: Provide a way for teachers to add external participants to BigBlueButton calls
description: Provide a way for teachers to add external participants to BigBlueButton calls. Link to related issue:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: BigBlueButton New Features and Improvements for 4.1
description: There are several new features and improvements that were postponed after BBB was integrated into core. This is the follow-up issue for tracking all the development looking forward to Moodle 4.1.
### Response:
1.summary: New capability to hide statistics from students
description: Hey jfederico! It would be great if the plugin had a moodle native capability to suppress the statistics function from a role.
2.summary: Provide a way for teachers to invite external participants (guests)
description: It would be nice for Teachers to be able to invite external teachers. The Best way would be to implement it like in greenlight: You enable the link in the module settings. If you are a teacher you get an invite link on the module page you can simply copy.
3.summary: Pick BBB UI language from Moodle user profile language instead of preferred browser language 205
description: In reference to GitHub issue 205| Reported as: According to the BBB documentation and according to my tests, the BBB UI language is chosen based on the preferred browser language. For the Moodle integration of BBB, I would like to propose to pick the BBB UI language based on the Moodle user profile language instead. This will help users who are working on a computer which does not have their main language as browser language set, but who have set the right language in their Moodle user profile. As always, this should be configurable with an admin setting to support the existing as well as the new behaviour. Development notes: As it is right now, the BBB API does not support language overriding. See GitHub Issue 10085| Once that is implemented this new feature would be tribial as we would only need to pass a lang parameter on join.
4.summary: Close meetings when removing BBB activity
description: Im not sure if this is really desirable, or open meetings should go on running although the BBB activity is deleted. bigbluebuttonbn_delete_instance (mod/bigbluebuttonbn/lib.php) loops over the course groups to delete a possible existing meeting for each group. It uses the groups_get_course_group function which only returns the active group, not all groups in the course.
5.summary: Add role parameter, phase out moderatorPW and attendeePW from create, and password from join
description: Since version 2.4, BBB can use a parameter that defines the role to be used in the BBB session instead of the so called password with is problematic with modern browsers. To give a bit of context, the so called `password` used in the URL in plain text is not a real password, but a token or identifier to be used to define the role a user should have in a meeting. The URLs used by BBB are in some way protected by a hash calculated using a shared secret. Therefore, `password` would not (should not and could not) be used for authenticating the user. The idea is that - create would no longer include modPW nor viewerPW, - join will use instead of password the designated role, such as role=moderator|viewer See We will not be removing the password currently, but only adding the role parameter. Phasing out of password use will most likely take place in BBB v2.6
6.summary: Add a way to filter out special formats other than statistics
description: . Special formats in the newest version. What are they? Special formats are recording formats that are produced in BBB for being shared differently. The best example is statistics, a format that should only be accessed by the Teacher because it comes with all the details of usage in the meeting. There are however other formats offered by custom BBB deployments (BBB recordings are meant to be extended by community). In fact, any other format could (and should) be treated as an special case in some cases. What is the problem? Only statistics is considered an special format and it is hard-coded. Who can access them? Users who have the capability mod/bigbluebuttonbn:managerecordings will be the only ones who can see it. By default only Editing Teachers and Admins do. How was done before? In previous versions, there was a setting to define what formats should be ruled out from Teachers, and also a setting to define the roles that would have access to them. How should it be? Since this is an authorisation, using the mod/bigbluebuttonbn:managerecordings makes sense. So admins and any other role or user with this capability enabled should be able to access "Special formats" But, there should be a way to define which are those special formats. Either through settings or env variable. But it should never be hard-coded. An alternative is to use the same payload to differentiate which ones are special and which ones are not. Although this is not an standard characteristic of BBB recordings.
7.summary: Add a parameter to set the polling value for the live session/wait for moderator
description: When the user waits for another to join the session or the session is opened from another user, then in the meantime we have to poll BBB server to retrieve its status. Best here would be to have a setting that can be changed and allow to poll more or less frequently (and lower the server load for example). To make it more parameterised (from 5 to 10) Maybe add some sort of visual information so the user know that something is happening (a countdown ?).
8.summary: Add role parameter, phase out moderatorPW and attendeePW from create, and password from join in 4.0
description: Since version 2.4, BBB can use a parameter that defines the role to be used in the BBB session instead of the so called password with is problematic with modern browsers. To give a bit of context, the so called `password` used in the URL in plain text is not a real password, but a token or identifier to be used to define the role a user should have in a meeting. The URLs used by BBB are in some way protected by a hash calculated using a shared secret. Therefore, `password` would not (should not and could not) be used for authenticating the user. The idea is that - create would no longer include modPW nor viewerPW, - join will use instead of password the designated role, such as role=moderator|viewer See We will not be removing the password currently, but only adding the role parameter. Phasing out of password use will most likely take place in BBB v2.6
9.summary: BigluebuttonBN outline display is a bit too verbose
description: During the development of the fix for we noticed that the outline report for user activity is a bit too verbose for the module. The aim of this ticket is to find a way to display all necessary information to the user without being too detailed.
10.summary: Remove the lockonjoin settings
description: As per , we decided to: 1. To remove the setting "lock on join" so it is not optional, 2. And to hard-code the lockonjoin=true parameter on create when any of the lock settings is used. Background information: The issue turned out to be the user missing to check the "lock on join" box. When that happens, the lockonjoin value assumed by BBB will be whatever value the BBB server has by default, in this case false. This means that the locks are applied in the meeting but not to all the users on join. We (the integrators) are still not clear what is the intention for that in BBB, but for the purposes of the Moodle user experience, because the use case.
11.summary: Recordings synchronisation : warn user when cron is disabled or not working
description: We are seeing more an more complains about the recordings not showing up because cron is disabled. It is OK, we knew that and the documentation is already there. BUT, chatting with other folks from the BBB community, one suggested to warn system administrators if cron is not enabled. Two directions : some sort of state (perhaps the status itself), passing from AWAITING to PROCESSING when the task is scheduled, and only passing it to PROCESSED when it finishes. As per the cron not enabled, there is a warning on the notification page when it has not run for more than x minutes, we might be able to replicate this.
12.summary: Provide a way for teachers to add external participants to BigBlueButton calls
description: Provide a way for teachers to add external participants to BigBlueButton calls. Link to related issue:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Forum "Timed posts" improvements
description: Collecting together issues relating to Timed forum posts.
| Unsolvable | 1.summary: Forum timed posts: display period not displayed
description: When the forum timed posts feature is enabled, users can see their own timed posts even when they are not yet due to appear. This is probably correct but there should be some display indicating that a post is not visible to ordinary users and showing the dates that it will be available.
2.summary: Timed posts should not be marked as experimental
description: Setting to enable in admin console suggests they are. Needs updating if all OK with this feature.
3.summary: Allow timed forum post to have time, not just date
description: For timed forum posts you can only specify the date that the forum post will be shown, but not the time. We also want to specify the time as well.
4.summary: Timed discussions are not displayed to students in a logical order
description: With forum_enabletimedposts enabled, when viewing a table of discussion topics within a forum (or the Latest News block), the user is presented a list of discussions in the order they were created (due to ORDER BY timemodified DESC: This can become confusing for students (or cause students to miss discussions altogether) in an active forum as it means when a timed posts becomes available, it will appear below any more recently created posts. This becomes more apparent when utilising the Latest News block as a discussion with a timestart date could never be shown in the block due to the posts being ordered by timemodified. It would seem to make sense to override the timemodified field with the timestart field (if set) in all areas to ensure discussions are displayed in the order they are made available to students.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Forum "Timed posts" improvements
description: Collecting together issues relating to Timed forum posts.
### Response:
1.summary: Forum timed posts: display period not displayed
description: When the forum timed posts feature is enabled, users can see their own timed posts even when they are not yet due to appear. This is probably correct but there should be some display indicating that a post is not visible to ordinary users and showing the dates that it will be available.
2.summary: Timed posts should not be marked as experimental
description: Setting to enable in admin console suggests they are. Needs updating if all OK with this feature.
3.summary: Allow timed forum post to have time, not just date
description: For timed forum posts you can only specify the date that the forum post will be shown, but not the time. We also want to specify the time as well.
4.summary: Timed discussions are not displayed to students in a logical order
description: With forum_enabletimedposts enabled, when viewing a table of discussion topics within a forum (or the Latest News block), the user is presented a list of discussions in the order they were created (due to ORDER BY timemodified DESC: This can become confusing for students (or cause students to miss discussions altogether) in an active forum as it means when a timed posts becomes available, it will appear below any more recently created posts. This becomes more apparent when utilising the Latest News block as a discussion with a timestart date could never be shown in the block due to the posts being ordered by timemodified. It would seem to make sense to override the timemodified field with the timestart field (if set) in all areas to ensure discussions are displayed in the order they are made available to students.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Moodle 4.1 Database project - user experience improvements for teacher and students
description: This project arises from the deep study and analysis carried out by MUA () and UX of the Database activity. Therefore, it aims to modernise Moodle s database interface, improve the existing workflows and make its usage a more intuitive and user-friendly experience. There are two main goals, the first it makes it easy for teachers to create new database activities, providing a new set of presets and preview mode. Second, it is to improve the student experience by providing a better experience with the existing views in his journey. MVP The key tasks related to the teacher persona are: Provide "zero state" information to point teachers in the right direction. Especially to use presets. Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate. Add a new set of useful presets. New preset management page providing preview mode. Teacher journey prototype| The key tasks related to the student persona relate to simplifying and modernising the list and simple view layout so the database entries are easier to find and understand, by providing: Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate. Minor style adjustments to add entry database interface. Student journey prototype| Future work / out of scope There are some out-of-scope goals for teachers that may be aimed at a 4.2 release, including: Modernize and improve the add fields workflow. Improve the template section to make it easy to use. Preview mode. Automatically add fields to templates when creating a new field. Providing new actions like duplicating or fixing/hiding the view layout. Add new views like grid or table layout. Allow the teacher to change the view name. Some admin actions like enabled/disabled/delete admin presets to site level. Its important to notice that all the prototypes are in working in progress and open to new changes. Epic Issue Integration order: We would like to explain what we think is a proper order to integrate the issues of the epic because there are some parts of the code that some issues share. The code of the module database is old and to work properly we need to refactor some parts and create new classes, mustaches, tests and improve other parts of the code. The following issues should be integrated in this order: Create a new id tag to use in Database activity templates Select/Unselect all options should be visible when there is a delete checkbox on database activity List template only Improve Presets management list page for Database activity Add description to Database activity presets Edit Database activity presets name and description Add "Export" preset feature to presets list Redesign the zero state page for Database activity module Move "Delete" preset confirmation to a modal Create a new preview page for Database activity Presets add sticky footer to mod_data pages Create new dropdown kebab menu tag with all the actions for the "List view" and "Single view" templates Improve Image gallery preset templates Create a new preset for Journal Create a new preset for Resources Create a new preset for Proposals Update default layouts for the new database templates Display approval status in the database entries Adjust presets and default templates to meet the prototype Skip fields mappings form if there are not fields created Move "Import" preset form to a modal Improve mapping workflow when importing or using a preset Implement the prototyped navigation changes in database activity Reset all templates in one go Zero state on fields and templates when there is no field created on the Database Improve zero state images for database activity
| Unsolvable | 1.summary: Create a new preset for Journal
description: Following the prototype| we will create a new Journal preset. List view: !reflections_listview.png! Single view: !reflections_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
2.summary: Create a new preset for Resources
description: Following the prototype| we will create a new Resources preset. List view: !readinglist_listview_table.png! Single view: !readinglist_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
3.summary: Add "Export" preset feature to presets list
description: A new option to Export presets from the presets list page has been added to the Figma prototype| !prototype_export.png|width=807,height=151! Currently, only the current activity configuration can be exported as a preset (so presets cant be exported). This issue is to add support for the "Export" preset feature and should implement the "Export" action to any of the saved presets in the list (plugin presets will be ignored, at least for now).
4.summary: Create a new preset for Proposals
description: Following the prototype| we will create a new Proposals preset. List view: !proposals_listview.png! Single view: !proposals_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
5.summary: Improve Image gallery preset templates
description: Following prototype| improve Image gallery preset templates. List view: !imagegallery_listview.png! Single view: !image-2022-07-19-18-16-00-278.png|width=615,height=407! Add entry (note: dont worry about image file picker style, is not part of this issue. And the Caption field is missing in this prototype image) !imagegallery_addentry.png!
6.summary: Add sticky footer to the mod_data pages
description: As a teacher I want to have a sticky footer always present in the database activity so I have a quick access to the main page options As designed by UX, the database activity will be the first plugin in moodle to implement the new sticky footer concept. However, the implementation will be used in other future developments. The technical specs and the starting code of that issue can be found in . This issue is part of the Moodle 4.1 database module project. All the related code to this issue that does not follow the current coding style or presents maintenance problems will be refactored. In this case, the refactored areas are focused on 3 main areas: - View entries - Templates - Presets - Fields The latest the database activity UX prototype| has as new visual element called "sticky footer" that contains the main actions (paginations, action buttons...) of the current page. In the current version, the pages where sticky footer is present are: - Database tab: -- The list view has the select all/delete buttons, the pagination, and the add entry button -- The single view has the pagination and the add entry button -- The add entry form has a save/cancel buttons (the "Save and add another" button is not present in the prototype but for now it will be kept in the sticky footer because the main goal of the issue is to move the current functionalities, not to reimplement them) - Templates -- The template editor has the "reset template", "Save template" buttons, and the "use editor" checkbox - Presets -- The main preset page has the "Use this preset" button -- The preset preview page has a "use this preset" button -- The field mapping form has cancel and continue buttons - Fields -- The main fields list page has a "View Templates" link -- The create field form has the save and cancel buttons
7.summary: Create a new preview page for Database activity Presets
description: As a teacher I want to preview the presets so I can choose the right one for my Database activity In the Presets management list page we would add a link on the preset name that will redirect the user to a preset preview page. The new Preview page will be based on the templates that will be created in further issues, so for now we could work using the existing Image gallery core preset. In this issue we should work on the following tasks: Decide how we are going to store the fake data we would need to render on the preview. Create the link on the presets management list page (on the name of the preset). Create mustache templates for preview following prototype| Tertiary navigation elements are moved to the right. The user could choose between List view and Single view. Preset name and description are shown etc. !image-2022-07-05-20-08-05-296.png!
8.summary: Move "Delete" preset confirmation to a modal
description: When the user clicks on the "Delete" action in the presets list page, the confirmation message should be triggered in a modal instead of on a new page.
9.summary: Use default templates in mod_data if the templates are not created.
description: The current database activity requires the user to create the templates or, at least, access the templates tab (which will create them without the users knowledge). This restriction is completely unnecessary as the activity is capable of generating default templates in real-time if the stored template is null. It is especially important in the add entry form because the default template is generated and stored in the database without asking the user and, if the user creates a new field, it will be appended at the end of the template, no matter what content the template has. The template generator is the data_generate_default_template function and has one param called $update to decide if the template is stored in the DB or not. This issue includes: Review all uses of data_generate_default_template with $update=true (the default value) and remove it from the code except the places when the user explicitly saves a template. Check whenever an entry is printed (even the add entry form) and validate that the $manager->get_template is used (that method returns the default template is there is none in the database). Remove any error or alert displayed when the user does not have the templates stored in the DB. Tey wont be necessary anymore now they will be auto-generated in real time (until the user defines its own or apply a preset).
10.summary: Create new dropdown kebab menu tag with all the actions for the "List view" and "Single view" templates
description: As a teacher I want to add a single element to the List view/Single view templates so users can see all the actions in one place instead of adding them separately with icons A new actionsmenu tag will be added to templates so the users and the new presets could use it to display a kebab menu action with all the actions the user has access to. Database project prototype| !actionmenutag.png|width=456,height=311!!actionmenutag_singleview.png|width=428,height=235!
11.summary: Zero state on fields and templates when there is no field created on the Database
description: As a teacher I want to be aware of the need of creating fields before working on templates or any other database sections so I can be guided on the right workflow to create a Database activity The teacher should create fields manually or using a preset before navigating/working with templates or entries. Following prototype| we could implement a new zero state page for this case to help and guide the teacher on the process. We should change the Fields page when there is no field created: !image-2022-09-13-16-07-48-407.png|width=767,height=568! We should change the Templates page when there is no field created and guide the user as in the main database page: !image-2022-07-29-12-27-05-433.png|width=763,height=499! We should change the existing Create a new field drop-down component on Fields page to use the same as in the zero state. !image-2022-09-13-16-10-32-177.png|width=763,height=384!
12.summary: Update default layouts for the new database templates
description: Following the prototype| improve the default preset templates. For instance, these are some of the changes to consider The List view and the Single view should replace current icons for the new actionsmenu created in . The Add entry template should display the form names and fields in different lines (instead of doing it in the same row). The advanced search template should follow the design of the form. Attention: This is still being reviewed; it can be skipped here if there is no final template for the advanced search when this issue is implemented because there is an issue for dealing with advanced search. Note: This issue is only for improving the default templates, so it shouldnt include any other change. !latest_default_addentry.png|thumbnail!!latest_default_listview.png|thumbnail!!latest_default_search.png|thumbnail!!latest_default_singleview.png|thumbnail!
13.summary: Reset all templates in one go
description: As a teacher I want to reset and save all templates in one go to make it easier to reset templates every time I add a new field The reset all templates can be done in 2 different ways in the templates tab: Click the "reset all templates" action in the tertiary navigation Click the "reset template" button and check the "reset all templates" checkbox in the appearing modal. The first approach for this improvement was to implement a new Reset and save all templates feature to reset and save all templates in one click (it can be found in the prototype| !image-2022-08-09-18-34-48-349.png|width=820,height=351! The user will be asked to confirm the action before proceeding to reset templates. !image-2022-08-09-18-35-30-967.png! However, while reviewing , a new proposal was raised and approved by the UX and PX teams: add a checkbox "Reset all templates" in the new modal that has been added in this issue, unchecked by default, to let users reset all templates in one go: !resetalltemplates.png!
14.summary: Review the page layout for the database activity
description: Following the prototype| the page layout for the database activity should be reviewed. Right now, the layouts for the list view, single view and add entry templates are full-width but looking at the Figma prototypes, they are smaller: !database_pagelayout.png!
15.summary: Adjust presets and default templates to meet the prototype
description: After working on the presets and the default templates, a few points were raised and discussed with the UX and the PX teams| This issue is for reviewing and improving these details: Replace the cog icon with a pencil. Make all the icons be displayed in black colour (instead of the current blue). Remove the "Single view" and "List view" headings from the Single view and List view pages. The accessibility team has confirmed that, as long as the heading structure is okay, I guess thats fine. e.g. no skipped headings > > ... > ... Add the "First name" and "Last name" fields at the beginning of the advanced search template. Apart from adding them, they must be renamed from "Author first name" and "Author surname" to "First name" and "Last name". Review that all the presets have the following metadata (displayed at the top of the entry with the design in the prototype| user dateadded datemodified The dates will be displayed in a shorter format: "22 Jun, 2022". And, if possible, the whole date (with week day and hour) will be displayed too on hover. For the "Journal" preset: Add a link on each card entry title, to open the Single view. Remove the "Reflections" heading from the Single view. For the "Resources" preset: Rename "Author" to "Author of resource" and "Description" to "Content". Check the default templates and presets are displayed properly in the mobile version. As raised in , the Type and Author fields will be removed from the List view for small devices.
16.summary: Improve navigation in database activity
description: Following the prototype| improve the navigation. For instance, these are some of the changes to consider: Reorder the tabs for the secondary navigation, to display Presets before Fields and Templates. On the Database page: Move the Import entries, Export entries and Export to portfolio to the Actions menu in the tertiary navigation dropdown. Remove the List/Single view heading. When the advanced search is enabled, remove the Save settings button near the Advanced search checkbox. "No records found" and "Found records" shouldnt be displayed as notifications. On the Presets page: Add Import, Export and Save as preset to a tertiary navigation dropdown (and rename Saves as preset to Publish preset on this site). Remove the Action column heading. On the Presets preview page: Add the preset name to the tertiary navigation heading (Preview of xxxx), and remove the current preset name from the page. Align the List/single template menu to the right. Remove the preset description. Make primary the "Use this preset" button. On the Fields page: Remove the "Use a preset" option. Remove Export and Save as preset to a tertiary navigation dropdown. -Remove import- (done in ) Align Create a field to the right. Add a description at the top of the page. Remove the Action column heading. Move action icons to ellipsis. On the Templates page: Move Export and Save as preset to a tertiary navigation dropdown (and rename Saves as preset to Publish preset on this site). Move the templates list to a tertiary_navigation_selector and remove the template heading (to not duplicate information). Reorder the templates list to follow the prototype: Add entry template Single view template List view template Advanced search template CSS template Javascript template RSS template Rename "Enable editor" to "Enable code editor" -Move "Enable code editor" to the tertiary navigation- (it will be done in ).
17.summary: Select/Unselect all options should be visible when there is a delete checkbox on database activity List template only
description: As a teacher I want to be able to select/unselect all entries when there is a checkbox that marks the selection only so I could better understand what I am selecting/unselecting Currently, Select all button is always visible in the list view, whether the Bulk delete checkbox (delcheck) has been added to the List template or not. The goal of this issue is to show that button when the Bulk delete checkbox is present and visible on the List view only. Acceptance criteria: List view template with no Bulk delete checkbox element There is no Select all, Unselect all and/or Delete selected button visible List view template with Bulk delete checkbox element (per current behavior, to be discussed) When there is no entry selected There is an enable Select all button visible There is no Unselect all button visible There is a disable Delete selected button visible When any of the entries are selected (one or more, but not all) There is an enable Select all button visible There is no Unselect all button visible There is an enable Delete selected button visible When all the entries are selected There is no Select all button visible There is an enable Unselect all button visible There is an enable Delete selected button visible
18.summary: Investigate the technical feasibility of multilingual presets on the database activity
description: Teachers can save database activity configuration and templates as reusable templates called presets. Those presets are stored as moodle files and all strings are hardcoded without using any lang files. The use of langs is especially important in the core presets because they are meant to be used by the teacher directly and having them only in English is a problem for other language courses. The starting point of this evaluation could be to imitate what user tours do as the context is similar. Both user tours steps and database presets are stored in a static form (json or files) but tours allow get the strings from a lang file. In the case of the tours the system checks if the string matches the following regexp: |^(a-zA-Za-zA-Z0-9\.:/_-),(a-zA-Za-zA-Z0-9\.:/_-)$| In that case the string is considered a lang string (string identifier, plugin frankenlstyle). Otherwise it is a non-translatable text.
19.summary: Redesign database activity view page
description: Following the prototype| we should redesign the view page skeleton: Search element ( and ) Sorting options () Filtering (related to ) Tertiary navigation: Entries and Views action menus. () Show all/Entries per page element () Paging () Select all/Unselect all (per current behavior. This behavior will be improved in ) Add entry button position. () _Note: This issue is not about making the footer sticky, so the elements will be added to non-sticky layers._
20.summary: Edit Database activity presets name and description
description: As a teacher I want to edit the name and description of my Database activity presets so I could fix errors or improve the description of the presets A few things to consider: Core presets shouldnt be editable. Only presets added by users will be edited. The "save as preset" modal should be updated to meet the prototype|
21.summary: Investigate the technical feasibility of implementing a sticky footer on the settings and view page
description: The UX roadmap includes a sticky footer with the buttons on the edit activity form. and we need to investigate the technical implications to understand if we can do it for 4.1 or 4.2. Some related aspects to evaluate that task: Evaluate if the sticky footers can be added to any pages quickform or if it is only applicable to specific cases like the activity/course settings. Evaluate the feasibility of using a quickform group for that sticky footer to customize the options. Define if by default the save and cancel standard options shall be part of that sticky footer (when the quick form specifies that uses the sticky footer).
22.summary: Skip fields mappings form if there are not fields created
description: A mapping form is displayed whenever a teacher applies a preset to a database activity, even if the database does not have any created field yet. The mappings form has 3 mains functions: Define mappings from the current database field to the preset ones A checkbox to remove all fields that has no mapping in the preset A checkbox (not present yet) to override the activity settings to match the preset ones. This task should avoid the mappings form when no field has been created.
23.summary: Redesign the zero state page for Database activity module
description: As a teacher I want to get all important links and option when my database activity module has no fields created yet so I can easily use presets, import presets or create new fields. !image-2022-07-05-15-12-51-122.png|width=540,height=353! As a student I want to be advice that the database activity is not ready to be used so I dont try to add a new entry !image-2022-07-05-15-12-19-632.png|width=531,height=369! As a student or teacher I want to be advice that there is no entry in the database activity yet so I can find the link to add new entries in a easier way !image-2022-07-05-15-11-51-477.png|width=540,height=399! !image-2022-07-14-16-02-42-207.png|width=539,height=398! As designed by UX, database activity view page should be change to show different information for different case and have a more clear zero state. For teachers, will show quick options to Import presets, Create fields and Use presets. For students, will show a message when there is no field created yet notifying the activity is still under construction, and a quick option to Add entries where fields are already created but there is no entry yet. No changes will be applied to view page on this issue for the rest of cases. _Note_: Database activity view page should use templates to make rendering information easier to change and maintain. Prototype:
24.summary: Improve Presets management list page for Database activity
description: An improved Presets list should be implemented following the prototype: Some of the improvements need to be done: Add a new help text Add captions to table columns Move the Import button to the right Add an action menu for each presets based on the users capabilities. New actions will be added in separate issues: Export: Edit: CSS improvements We agreed with the UX team that the action menu will be displayed always, not just on hover as displayed in the current prototype (to avoid accessibility issues and for consistency with other similar places, like the main course page). Use preset button will be enabled when a preset is selected only. Note: Dont add the Use preset button as a sticky footer because it will be decided on !image-2022-07-05-19-48-36-891.png|width=679,height=500!
25.summary: Create a new id tag to use in Database activity templates
description: As a teacher I want to identify an element by a unique id on a Database template so I can apply styling and behavior to the element For some of the new templates defined on the Database project prototype we need some elements to be collapsable. To implement this accordion behavior in an easy way, we need to identify the elements by the id. A new id tag will be added to templates so the users and the new presets could use to implement the behavior they need. Prototype: This issue is part of the Moodle 4.1 database module project. All the related code to this issue that does not follow the current coding style or present maintenance problems will be refactored. In this case, the refactored areas are focused in 3 main areas: Create a generic mod_data\manager class for the mod_data (similar to the one used in mod_pactivity) Refactor the template editor to use output classes and mustache files (the functionality will remain the same) Refactor the print entry parser into its own class mod_data\template and use it instead of the current global function
26.summary: Investigate the technical feasibility of editing the name of a preset in the database module
description: Teachers can save database activity configuration and templates as reusable templates called presets. Those presets are stored as moodle files and cannot be edited once created. It could be good to give the opportunity to the teacher to edit the name of the preset once the preset has been created. We need to investigate how this affects the existing preset, files, and database tables... and the implications of doing this. Furthermore, admins can also create global presets so the edit options should be limited. Apart, some of the presets are hardcoded as database preset plugins.
27.summary: Add description to Database activity presets
description: As a teacher I want to add a description to my Database activity presets so I could describe better the purpose or use case or the preset We should add some description information to the preset setup (probably to preset.xml, but it needs some research) to make the preset easier to understand and describe the purpose of the preset and the proposed use cases. This new description shouldnt be required because the existing third-party database preset plugins and saved presets dont have it. The description couldnt contain HTML code.
28.summary: Differentiate plugin presets from presets added by users
description: As an admin I want to know which presets are plugins and which are created by users so the plugin presets cant be deleted or edited Right now we only have one plugin preset called Image gallery that cant be deleted because the name of the preset is hardcoded. But we are adding many new plugin presets to core, so we need a better way to differentiate plugin and user presets. Plugin presets cant be deleted Presets saved as by users can be deleted
29.summary: Create a prototype to close the course index when adding/editing a new activity
description: Close the course index when you are adding/editing a new activity. Same, across all the activities, same behavior. We need to create a prototype applying this behavior to let the people play with it and understand more about this proposal.
30.summary: Use standard Moodle notification when saving a preset on Database
description: For consistency, we should use Moodle standard notifications that dont disappear automatically for the Save as preset workflow on Database activity. Apart from that, we should review the format of this notification to meet the prototype:| !saveaspresetnotification.png|width=545,height=232!
31.summary: Improve mapping workflow when using a preset
description: Following prototype| we should add a new modal dialogue when using a preset from Presets and Preset preview pages that needs to perform some changes on the database fields. !image-2022-08-16-13-05-02-993.png! Apply preset button should apply the default mapping without asking. Map fields button should redirect user to the currently existing mapping page for them to be able to change default values. Cancel button should cancel the import/use preset process. The mapping workflow for databases with no entries has been already changed on .
32.summary: Improve zero state images for database activity
description: On and the images used for zero state has been default images because the final images were decided on . Now that we have the final images to use as database activity for zero state, we should change the images.
33.summary: Move "Import" preset form to a modal
description: When the user clicks on the "Import" action, the form to upload the file should be triggered in a modal instead of on a new page.
34.summary: Add shadow to sticky footer
description: During the user testing, some users experience difficulties finding the new sticky footer component. The general consensus is that the component will be more obvious by applying a shadow to the element. the proposed shadow is the standard bootstrap shadow color and length (length=1rem color=rgba($black, .15)). However, we cannot use the "shadow" class because the bootstrap shadow is not centered on the element but a bit below. The solution is to add this rule directly into the .stickyfooter SCSS: code:javabox-shadow: 0 0 1rem rgba($black, .15);code
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Moodle 4.1 Database project - user experience improvements for teacher and students
description: This project arises from the deep study and analysis carried out by MUA () and UX of the Database activity. Therefore, it aims to modernise Moodle s database interface, improve the existing workflows and make its usage a more intuitive and user-friendly experience. There are two main goals, the first it makes it easy for teachers to create new database activities, providing a new set of presets and preview mode. Second, it is to improve the student experience by providing a better experience with the existing views in his journey. MVP The key tasks related to the teacher persona are: Provide "zero state" information to point teachers in the right direction. Especially to use presets. Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate. Add a new set of useful presets. New preset management page providing preview mode. Teacher journey prototype| The key tasks related to the student persona relate to simplifying and modernising the list and simple view layout so the database entries are easier to find and understand, by providing: Revamp the list and simple view page styling with a more modern design and make it easier to use and navigate. Minor style adjustments to add entry database interface. Student journey prototype| Future work / out of scope There are some out-of-scope goals for teachers that may be aimed at a 4.2 release, including: Modernize and improve the add fields workflow. Improve the template section to make it easy to use. Preview mode. Automatically add fields to templates when creating a new field. Providing new actions like duplicating or fixing/hiding the view layout. Add new views like grid or table layout. Allow the teacher to change the view name. Some admin actions like enabled/disabled/delete admin presets to site level. Its important to notice that all the prototypes are in working in progress and open to new changes. Epic Issue Integration order: We would like to explain what we think is a proper order to integrate the issues of the epic because there are some parts of the code that some issues share. The code of the module database is old and to work properly we need to refactor some parts and create new classes, mustaches, tests and improve other parts of the code. The following issues should be integrated in this order: Create a new id tag to use in Database activity templates Select/Unselect all options should be visible when there is a delete checkbox on database activity List template only Improve Presets management list page for Database activity Add description to Database activity presets Edit Database activity presets name and description Add "Export" preset feature to presets list Redesign the zero state page for Database activity module Move "Delete" preset confirmation to a modal Create a new preview page for Database activity Presets add sticky footer to mod_data pages Create new dropdown kebab menu tag with all the actions for the "List view" and "Single view" templates Improve Image gallery preset templates Create a new preset for Journal Create a new preset for Resources Create a new preset for Proposals Update default layouts for the new database templates Display approval status in the database entries Adjust presets and default templates to meet the prototype Skip fields mappings form if there are not fields created Move "Import" preset form to a modal Improve mapping workflow when importing or using a preset Implement the prototyped navigation changes in database activity Reset all templates in one go Zero state on fields and templates when there is no field created on the Database Improve zero state images for database activity
### Response:
1.summary: Create a new preset for Journal
description: Following the prototype| we will create a new Journal preset. List view: !reflections_listview.png! Single view: !reflections_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
2.summary: Create a new preset for Resources
description: Following the prototype| we will create a new Resources preset. List view: !readinglist_listview_table.png! Single view: !readinglist_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
3.summary: Add "Export" preset feature to presets list
description: A new option to Export presets from the presets list page has been added to the Figma prototype| !prototype_export.png|width=807,height=151! Currently, only the current activity configuration can be exported as a preset (so presets cant be exported). This issue is to add support for the "Export" preset feature and should implement the "Export" action to any of the saved presets in the list (plugin presets will be ignored, at least for now).
4.summary: Create a new preset for Proposals
description: Following the prototype| we will create a new Proposals preset. List view: !proposals_listview.png! Single view: !proposals_singleview.png! The fields and other information for this preset can be found in the document| created by the Product Experience team.
5.summary: Improve Image gallery preset templates
description: Following prototype| improve Image gallery preset templates. List view: !imagegallery_listview.png! Single view: !image-2022-07-19-18-16-00-278.png|width=615,height=407! Add entry (note: dont worry about image file picker style, is not part of this issue. And the Caption field is missing in this prototype image) !imagegallery_addentry.png!
6.summary: Add sticky footer to the mod_data pages
description: As a teacher I want to have a sticky footer always present in the database activity so I have a quick access to the main page options As designed by UX, the database activity will be the first plugin in moodle to implement the new sticky footer concept. However, the implementation will be used in other future developments. The technical specs and the starting code of that issue can be found in . This issue is part of the Moodle 4.1 database module project. All the related code to this issue that does not follow the current coding style or presents maintenance problems will be refactored. In this case, the refactored areas are focused on 3 main areas: - View entries - Templates - Presets - Fields The latest the database activity UX prototype| has as new visual element called "sticky footer" that contains the main actions (paginations, action buttons...) of the current page. In the current version, the pages where sticky footer is present are: - Database tab: -- The list view has the select all/delete buttons, the pagination, and the add entry button -- The single view has the pagination and the add entry button -- The add entry form has a save/cancel buttons (the "Save and add another" button is not present in the prototype but for now it will be kept in the sticky footer because the main goal of the issue is to move the current functionalities, not to reimplement them) - Templates -- The template editor has the "reset template", "Save template" buttons, and the "use editor" checkbox - Presets -- The main preset page has the "Use this preset" button -- The preset preview page has a "use this preset" button -- The field mapping form has cancel and continue buttons - Fields -- The main fields list page has a "View Templates" link -- The create field form has the save and cancel buttons
7.summary: Create a new preview page for Database activity Presets
description: As a teacher I want to preview the presets so I can choose the right one for my Database activity In the Presets management list page we would add a link on the preset name that will redirect the user to a preset preview page. The new Preview page will be based on the templates that will be created in further issues, so for now we could work using the existing Image gallery core preset. In this issue we should work on the following tasks: Decide how we are going to store the fake data we would need to render on the preview. Create the link on the presets management list page (on the name of the preset). Create mustache templates for preview following prototype| Tertiary navigation elements are moved to the right. The user could choose between List view and Single view. Preset name and description are shown etc. !image-2022-07-05-20-08-05-296.png!
8.summary: Move "Delete" preset confirmation to a modal
description: When the user clicks on the "Delete" action in the presets list page, the confirmation message should be triggered in a modal instead of on a new page.
9.summary: Use default templates in mod_data if the templates are not created.
description: The current database activity requires the user to create the templates or, at least, access the templates tab (which will create them without the users knowledge). This restriction is completely unnecessary as the activity is capable of generating default templates in real-time if the stored template is null. It is especially important in the add entry form because the default template is generated and stored in the database without asking the user and, if the user creates a new field, it will be appended at the end of the template, no matter what content the template has. The template generator is the data_generate_default_template function and has one param called $update to decide if the template is stored in the DB or not. This issue includes: Review all uses of data_generate_default_template with $update=true (the default value) and remove it from the code except the places when the user explicitly saves a template. Check whenever an entry is printed (even the add entry form) and validate that the $manager->get_template is used (that method returns the default template is there is none in the database). Remove any error or alert displayed when the user does not have the templates stored in the DB. Tey wont be necessary anymore now they will be auto-generated in real time (until the user defines its own or apply a preset).
10.summary: Create new dropdown kebab menu tag with all the actions for the "List view" and "Single view" templates
description: As a teacher I want to add a single element to the List view/Single view templates so users can see all the actions in one place instead of adding them separately with icons A new actionsmenu tag will be added to templates so the users and the new presets could use it to display a kebab menu action with all the actions the user has access to. Database project prototype| !actionmenutag.png|width=456,height=311!!actionmenutag_singleview.png|width=428,height=235!
11.summary: Zero state on fields and templates when there is no field created on the Database
description: As a teacher I want to be aware of the need of creating fields before working on templates or any other database sections so I can be guided on the right workflow to create a Database activity The teacher should create fields manually or using a preset before navigating/working with templates or entries. Following prototype| we could implement a new zero state page for this case to help and guide the teacher on the process. We should change the Fields page when there is no field created: !image-2022-09-13-16-07-48-407.png|width=767,height=568! We should change the Templates page when there is no field created and guide the user as in the main database page: !image-2022-07-29-12-27-05-433.png|width=763,height=499! We should change the existing Create a new field drop-down component on Fields page to use the same as in the zero state. !image-2022-09-13-16-10-32-177.png|width=763,height=384!
12.summary: Update default layouts for the new database templates
description: Following the prototype| improve the default preset templates. For instance, these are some of the changes to consider The List view and the Single view should replace current icons for the new actionsmenu created in . The Add entry template should display the form names and fields in different lines (instead of doing it in the same row). The advanced search template should follow the design of the form. Attention: This is still being reviewed; it can be skipped here if there is no final template for the advanced search when this issue is implemented because there is an issue for dealing with advanced search. Note: This issue is only for improving the default templates, so it shouldnt include any other change. !latest_default_addentry.png|thumbnail!!latest_default_listview.png|thumbnail!!latest_default_search.png|thumbnail!!latest_default_singleview.png|thumbnail!
13.summary: Reset all templates in one go
description: As a teacher I want to reset and save all templates in one go to make it easier to reset templates every time I add a new field The reset all templates can be done in 2 different ways in the templates tab: Click the "reset all templates" action in the tertiary navigation Click the "reset template" button and check the "reset all templates" checkbox in the appearing modal. The first approach for this improvement was to implement a new Reset and save all templates feature to reset and save all templates in one click (it can be found in the prototype| !image-2022-08-09-18-34-48-349.png|width=820,height=351! The user will be asked to confirm the action before proceeding to reset templates. !image-2022-08-09-18-35-30-967.png! However, while reviewing , a new proposal was raised and approved by the UX and PX teams: add a checkbox "Reset all templates" in the new modal that has been added in this issue, unchecked by default, to let users reset all templates in one go: !resetalltemplates.png!
14.summary: Review the page layout for the database activity
description: Following the prototype| the page layout for the database activity should be reviewed. Right now, the layouts for the list view, single view and add entry templates are full-width but looking at the Figma prototypes, they are smaller: !database_pagelayout.png!
15.summary: Adjust presets and default templates to meet the prototype
description: After working on the presets and the default templates, a few points were raised and discussed with the UX and the PX teams| This issue is for reviewing and improving these details: Replace the cog icon with a pencil. Make all the icons be displayed in black colour (instead of the current blue). Remove the "Single view" and "List view" headings from the Single view and List view pages. The accessibility team has confirmed that, as long as the heading structure is okay, I guess thats fine. e.g. no skipped headings > > ... > ... Add the "First name" and "Last name" fields at the beginning of the advanced search template. Apart from adding them, they must be renamed from "Author first name" and "Author surname" to "First name" and "Last name". Review that all the presets have the following metadata (displayed at the top of the entry with the design in the prototype| user dateadded datemodified The dates will be displayed in a shorter format: "22 Jun, 2022". And, if possible, the whole date (with week day and hour) will be displayed too on hover. For the "Journal" preset: Add a link on each card entry title, to open the Single view. Remove the "Reflections" heading from the Single view. For the "Resources" preset: Rename "Author" to "Author of resource" and "Description" to "Content". Check the default templates and presets are displayed properly in the mobile version. As raised in , the Type and Author fields will be removed from the List view for small devices.
16.summary: Improve navigation in database activity
description: Following the prototype| improve the navigation. For instance, these are some of the changes to consider: Reorder the tabs for the secondary navigation, to display Presets before Fields and Templates. On the Database page: Move the Import entries, Export entries and Export to portfolio to the Actions menu in the tertiary navigation dropdown. Remove the List/Single view heading. When the advanced search is enabled, remove the Save settings button near the Advanced search checkbox. "No records found" and "Found records" shouldnt be displayed as notifications. On the Presets page: Add Import, Export and Save as preset to a tertiary navigation dropdown (and rename Saves as preset to Publish preset on this site). Remove the Action column heading. On the Presets preview page: Add the preset name to the tertiary navigation heading (Preview of xxxx), and remove the current preset name from the page. Align the List/single template menu to the right. Remove the preset description. Make primary the "Use this preset" button. On the Fields page: Remove the "Use a preset" option. Remove Export and Save as preset to a tertiary navigation dropdown. -Remove import- (done in ) Align Create a field to the right. Add a description at the top of the page. Remove the Action column heading. Move action icons to ellipsis. On the Templates page: Move Export and Save as preset to a tertiary navigation dropdown (and rename Saves as preset to Publish preset on this site). Move the templates list to a tertiary_navigation_selector and remove the template heading (to not duplicate information). Reorder the templates list to follow the prototype: Add entry template Single view template List view template Advanced search template CSS template Javascript template RSS template Rename "Enable editor" to "Enable code editor" -Move "Enable code editor" to the tertiary navigation- (it will be done in ).
17.summary: Select/Unselect all options should be visible when there is a delete checkbox on database activity List template only
description: As a teacher I want to be able to select/unselect all entries when there is a checkbox that marks the selection only so I could better understand what I am selecting/unselecting Currently, Select all button is always visible in the list view, whether the Bulk delete checkbox (delcheck) has been added to the List template or not. The goal of this issue is to show that button when the Bulk delete checkbox is present and visible on the List view only. Acceptance criteria: List view template with no Bulk delete checkbox element There is no Select all, Unselect all and/or Delete selected button visible List view template with Bulk delete checkbox element (per current behavior, to be discussed) When there is no entry selected There is an enable Select all button visible There is no Unselect all button visible There is a disable Delete selected button visible When any of the entries are selected (one or more, but not all) There is an enable Select all button visible There is no Unselect all button visible There is an enable Delete selected button visible When all the entries are selected There is no Select all button visible There is an enable Unselect all button visible There is an enable Delete selected button visible
18.summary: Investigate the technical feasibility of multilingual presets on the database activity
description: Teachers can save database activity configuration and templates as reusable templates called presets. Those presets are stored as moodle files and all strings are hardcoded without using any lang files. The use of langs is especially important in the core presets because they are meant to be used by the teacher directly and having them only in English is a problem for other language courses. The starting point of this evaluation could be to imitate what user tours do as the context is similar. Both user tours steps and database presets are stored in a static form (json or files) but tours allow get the strings from a lang file. In the case of the tours the system checks if the string matches the following regexp: |^(a-zA-Za-zA-Z0-9\.:/_-),(a-zA-Za-zA-Z0-9\.:/_-)$| In that case the string is considered a lang string (string identifier, plugin frankenlstyle). Otherwise it is a non-translatable text.
19.summary: Redesign database activity view page
description: Following the prototype| we should redesign the view page skeleton: Search element ( and ) Sorting options () Filtering (related to ) Tertiary navigation: Entries and Views action menus. () Show all/Entries per page element () Paging () Select all/Unselect all (per current behavior. This behavior will be improved in ) Add entry button position. () _Note: This issue is not about making the footer sticky, so the elements will be added to non-sticky layers._
20.summary: Edit Database activity presets name and description
description: As a teacher I want to edit the name and description of my Database activity presets so I could fix errors or improve the description of the presets A few things to consider: Core presets shouldnt be editable. Only presets added by users will be edited. The "save as preset" modal should be updated to meet the prototype|
21.summary: Investigate the technical feasibility of implementing a sticky footer on the settings and view page
description: The UX roadmap includes a sticky footer with the buttons on the edit activity form. and we need to investigate the technical implications to understand if we can do it for 4.1 or 4.2. Some related aspects to evaluate that task: Evaluate if the sticky footers can be added to any pages quickform or if it is only applicable to specific cases like the activity/course settings. Evaluate the feasibility of using a quickform group for that sticky footer to customize the options. Define if by default the save and cancel standard options shall be part of that sticky footer (when the quick form specifies that uses the sticky footer).
22.summary: Skip fields mappings form if there are not fields created
description: A mapping form is displayed whenever a teacher applies a preset to a database activity, even if the database does not have any created field yet. The mappings form has 3 mains functions: Define mappings from the current database field to the preset ones A checkbox to remove all fields that has no mapping in the preset A checkbox (not present yet) to override the activity settings to match the preset ones. This task should avoid the mappings form when no field has been created.
23.summary: Redesign the zero state page for Database activity module
description: As a teacher I want to get all important links and option when my database activity module has no fields created yet so I can easily use presets, import presets or create new fields. !image-2022-07-05-15-12-51-122.png|width=540,height=353! As a student I want to be advice that the database activity is not ready to be used so I dont try to add a new entry !image-2022-07-05-15-12-19-632.png|width=531,height=369! As a student or teacher I want to be advice that there is no entry in the database activity yet so I can find the link to add new entries in a easier way !image-2022-07-05-15-11-51-477.png|width=540,height=399! !image-2022-07-14-16-02-42-207.png|width=539,height=398! As designed by UX, database activity view page should be change to show different information for different case and have a more clear zero state. For teachers, will show quick options to Import presets, Create fields and Use presets. For students, will show a message when there is no field created yet notifying the activity is still under construction, and a quick option to Add entries where fields are already created but there is no entry yet. No changes will be applied to view page on this issue for the rest of cases. _Note_: Database activity view page should use templates to make rendering information easier to change and maintain. Prototype:
24.summary: Improve Presets management list page for Database activity
description: An improved Presets list should be implemented following the prototype: Some of the improvements need to be done: Add a new help text Add captions to table columns Move the Import button to the right Add an action menu for each presets based on the users capabilities. New actions will be added in separate issues: Export: Edit: CSS improvements We agreed with the UX team that the action menu will be displayed always, not just on hover as displayed in the current prototype (to avoid accessibility issues and for consistency with other similar places, like the main course page). Use preset button will be enabled when a preset is selected only. Note: Dont add the Use preset button as a sticky footer because it will be decided on !image-2022-07-05-19-48-36-891.png|width=679,height=500!
25.summary: Create a new id tag to use in Database activity templates
description: As a teacher I want to identify an element by a unique id on a Database template so I can apply styling and behavior to the element For some of the new templates defined on the Database project prototype we need some elements to be collapsable. To implement this accordion behavior in an easy way, we need to identify the elements by the id. A new id tag will be added to templates so the users and the new presets could use to implement the behavior they need. Prototype: This issue is part of the Moodle 4.1 database module project. All the related code to this issue that does not follow the current coding style or present maintenance problems will be refactored. In this case, the refactored areas are focused in 3 main areas: Create a generic mod_data\manager class for the mod_data (similar to the one used in mod_pactivity) Refactor the template editor to use output classes and mustache files (the functionality will remain the same) Refactor the print entry parser into its own class mod_data\template and use it instead of the current global function
26.summary: Investigate the technical feasibility of editing the name of a preset in the database module
description: Teachers can save database activity configuration and templates as reusable templates called presets. Those presets are stored as moodle files and cannot be edited once created. It could be good to give the opportunity to the teacher to edit the name of the preset once the preset has been created. We need to investigate how this affects the existing preset, files, and database tables... and the implications of doing this. Furthermore, admins can also create global presets so the edit options should be limited. Apart, some of the presets are hardcoded as database preset plugins.
27.summary: Add description to Database activity presets
description: As a teacher I want to add a description to my Database activity presets so I could describe better the purpose or use case or the preset We should add some description information to the preset setup (probably to preset.xml, but it needs some research) to make the preset easier to understand and describe the purpose of the preset and the proposed use cases. This new description shouldnt be required because the existing third-party database preset plugins and saved presets dont have it. The description couldnt contain HTML code.
28.summary: Differentiate plugin presets from presets added by users
description: As an admin I want to know which presets are plugins and which are created by users so the plugin presets cant be deleted or edited Right now we only have one plugin preset called Image gallery that cant be deleted because the name of the preset is hardcoded. But we are adding many new plugin presets to core, so we need a better way to differentiate plugin and user presets. Plugin presets cant be deleted Presets saved as by users can be deleted
29.summary: Create a prototype to close the course index when adding/editing a new activity
description: Close the course index when you are adding/editing a new activity. Same, across all the activities, same behavior. We need to create a prototype applying this behavior to let the people play with it and understand more about this proposal.
30.summary: Use standard Moodle notification when saving a preset on Database
description: For consistency, we should use Moodle standard notifications that dont disappear automatically for the Save as preset workflow on Database activity. Apart from that, we should review the format of this notification to meet the prototype:| !saveaspresetnotification.png|width=545,height=232!
31.summary: Improve mapping workflow when using a preset
description: Following prototype| we should add a new modal dialogue when using a preset from Presets and Preset preview pages that needs to perform some changes on the database fields. !image-2022-08-16-13-05-02-993.png! Apply preset button should apply the default mapping without asking. Map fields button should redirect user to the currently existing mapping page for them to be able to change default values. Cancel button should cancel the import/use preset process. The mapping workflow for databases with no entries has been already changed on .
32.summary: Improve zero state images for database activity
description: On and the images used for zero state has been default images because the final images were decided on . Now that we have the final images to use as database activity for zero state, we should change the images.
33.summary: Move "Import" preset form to a modal
description: When the user clicks on the "Import" action, the form to upload the file should be triggered in a modal instead of on a new page.
34.summary: Add shadow to sticky footer
description: During the user testing, some users experience difficulties finding the new sticky footer component. The general consensus is that the component will be more obvious by applying a shadow to the element. the proposed shadow is the standard bootstrap shadow color and length (length=1rem color=rgba($black, .15)). However, we cannot use the "shadow" class because the bootstrap shadow is not centered on the element but a bit below. The solution is to add this rule directly into the .stickyfooter SCSS: code:javabox-shadow: 0 0 1rem rgba($black, .15);code
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle sites 2.7.2 upgrade
description: Moodle 2.7.2 scheduled release: Monday 8 September 2014 Target completion date of this epic: Friday 5 September 2014
| Unsolvable | 1.summary: Upgrade moodle.org to 2.7.2
description:
2.summary: Upgrade demo.moodle.net to 2.7.2
description:
3.summary: Upgrade school.demo.moodle.net to 2.7.2
description:
4.summary: Upgrade moodle.net to 2.7.2
description:
5.summary: Upgrade dev.moodle.org to 2.7.2
description:
6.summary: Upgrade research.moodle.net to 2.7.2
description:
7.summary: Upgrade download.moodle.org to 2.7.2
description:
8.summary: Upgrade lang.moodle.org to 2.7.2
description:
9.summary: Upgrade learn.moodle.net to 2.5.8
description:
10.summary: Upgrade mootau15.moodlemoot.org to 2.7.2
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle sites 2.7.2 upgrade
description: Moodle 2.7.2 scheduled release: Monday 8 September 2014 Target completion date of this epic: Friday 5 September 2014
### Response:
1.summary: Upgrade moodle.org to 2.7.2
description:
2.summary: Upgrade demo.moodle.net to 2.7.2
description:
3.summary: Upgrade school.demo.moodle.net to 2.7.2
description:
4.summary: Upgrade moodle.net to 2.7.2
description:
5.summary: Upgrade dev.moodle.org to 2.7.2
description:
6.summary: Upgrade research.moodle.net to 2.7.2
description:
7.summary: Upgrade download.moodle.org to 2.7.2
description:
8.summary: Upgrade lang.moodle.org to 2.7.2
description:
9.summary: Upgrade learn.moodle.net to 2.5.8
description:
10.summary: Upgrade mootau15.moodlemoot.org to 2.7.2
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle Community Sites 4.2 upgrade
description: This is an epic for all the 4.2 upgrade. Please create tasks and subtasks for all the sites upgrade, within this epic moodle.org lang.moodle.org school.moodledemo.net sandbox.moodledemo.net stats.moodle.org -moodleassociation.org- (the MUA are remaining on Moodle 3.11 for now?)
| Unsolvable | 1.summary: Upgrade moodle.org to 4.2
description: Ill leave it to mudrd8mz to create the sub-tasks needed (for all the branches upgrades) for this.
2.summary: Content translation plugin update on moodle.org
description: Update the translation plugin on moodle.org to have the latest update by Rajneel ( to add a generate new hash button in the Atto editor) so we can utilise this new feature whenever we totally change the content on the front page in any content area. This will break the link to the old translations and mean they will display in English until translated. Check with Rajneel re update of the plugin.
3.summary: Upgrade lang.moodle.org to 4.2
description:
4.summary: Upgrade school.moodledemo.net to 4.2
description:
5.summary: Upgrade sandbox.moodledemo.net to 4.2
description:
6.summary: Upgrade stats.moodle.org to 4.2
description:
7.summary: Upgrade moodle.org to stable 4.2
description:
8.summary: English and German 4.2 docs set up
description: During the week starting 3rd April: Create the 402/en and 402/de wikis by cloning the 401/en and 401/de wiki databases Disable email notification of watched pages Many thanks in advance. _________________________________ from : Once the clone docs are created, next step (Mary/Aurelie), in new version wiki: (/) Edit MediaWiki:MoodleDocsVersionLinks (/) Edit Main_page (/) Add message to MediaWiki:Sitenotice (/) Remove new features template from all pages in Category:New_features (/) Edit Template:New_features and Category:New_feature (/) (Go through tracker issues with the docs_required label and the release notes for the upcoming release and add documentation on new features plus the new features template (/) Create Upgrading_to_Moodle_x.y and redirect to Upgrading (/) Update version number in Template:Version and Template:Version2 and Git for Administrators (x) Review Special:WantedPages (x) Review Special:LonelyPages (/) Review instances of "(new in x.y)" text (not always necessary to remove them) (/) Add link to new version wiki to ________________________________ Legend: (x) - not done (!) - work in progress (?) - waiting for testing (y) - tested fine, ready to be deployed (/) - done
9.summary: Final checks for user docs 4.2 ready for release
description: w/c 17 April 2023, follow the following steps as per for the user docs for 4.2. (prepared in | ) In new wiki: Remove message in MediaWiki:Sitenotice Check (and update if needed) Upgrading and Upgrade overview pages In all older version wikis: Edit to add the new version and remove older versions (though keeping LTS releases| . Day of release | Request for the new version wiki to be made default and email notification of watched pages to be enabled. In previous latest version wiki: Edit to make it like Edit to make it like Go through Special:RecentChanges in the previous most recent version wiki and add relevant changes to the new version wiki Edit and add redirect en( so it redirects to the latest version of the page Edit and add redirect en( so it redirects to the latest version of the page For no longer supported versions, create MediaWiki:Sitenotice by copying content from . Final checks | Email notification of watched pages enabled Links without version number, for example , redirect to the new version wiki Docs links from a dev site, such as the QA testing site, redirect to the correct page in the new version wiki New version wiki listed in
10.summary: User docs: create the New Features pages for Moodle LMS 4.2
description: Gather the new features and other issues labelled docs_required, to create the page.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle Community Sites 4.2 upgrade
description: This is an epic for all the 4.2 upgrade. Please create tasks and subtasks for all the sites upgrade, within this epic moodle.org lang.moodle.org school.moodledemo.net sandbox.moodledemo.net stats.moodle.org -moodleassociation.org- (the MUA are remaining on Moodle 3.11 for now?)
### Response:
1.summary: Upgrade moodle.org to 4.2
description: Ill leave it to mudrd8mz to create the sub-tasks needed (for all the branches upgrades) for this.
2.summary: Content translation plugin update on moodle.org
description: Update the translation plugin on moodle.org to have the latest update by Rajneel ( to add a generate new hash button in the Atto editor) so we can utilise this new feature whenever we totally change the content on the front page in any content area. This will break the link to the old translations and mean they will display in English until translated. Check with Rajneel re update of the plugin.
3.summary: Upgrade lang.moodle.org to 4.2
description:
4.summary: Upgrade school.moodledemo.net to 4.2
description:
5.summary: Upgrade sandbox.moodledemo.net to 4.2
description:
6.summary: Upgrade stats.moodle.org to 4.2
description:
7.summary: Upgrade moodle.org to stable 4.2
description:
8.summary: English and German 4.2 docs set up
description: During the week starting 3rd April: Create the 402/en and 402/de wikis by cloning the 401/en and 401/de wiki databases Disable email notification of watched pages Many thanks in advance. _________________________________ from : Once the clone docs are created, next step (Mary/Aurelie), in new version wiki: (/) Edit MediaWiki:MoodleDocsVersionLinks (/) Edit Main_page (/) Add message to MediaWiki:Sitenotice (/) Remove new features template from all pages in Category:New_features (/) Edit Template:New_features and Category:New_feature (/) (Go through tracker issues with the docs_required label and the release notes for the upcoming release and add documentation on new features plus the new features template (/) Create Upgrading_to_Moodle_x.y and redirect to Upgrading (/) Update version number in Template:Version and Template:Version2 and Git for Administrators (x) Review Special:WantedPages (x) Review Special:LonelyPages (/) Review instances of "(new in x.y)" text (not always necessary to remove them) (/) Add link to new version wiki to ________________________________ Legend: (x) - not done (!) - work in progress (?) - waiting for testing (y) - tested fine, ready to be deployed (/) - done
9.summary: Final checks for user docs 4.2 ready for release
description: w/c 17 April 2023, follow the following steps as per for the user docs for 4.2. (prepared in | ) In new wiki: Remove message in MediaWiki:Sitenotice Check (and update if needed) Upgrading and Upgrade overview pages In all older version wikis: Edit to add the new version and remove older versions (though keeping LTS releases| . Day of release | Request for the new version wiki to be made default and email notification of watched pages to be enabled. In previous latest version wiki: Edit to make it like Edit to make it like Go through Special:RecentChanges in the previous most recent version wiki and add relevant changes to the new version wiki Edit and add redirect en( so it redirects to the latest version of the page Edit and add redirect en( so it redirects to the latest version of the page For no longer supported versions, create MediaWiki:Sitenotice by copying content from . Final checks | Email notification of watched pages enabled Links without version number, for example , redirect to the new version wiki Docs links from a dev site, such as the QA testing site, redirect to the correct page in the new version wiki New version wiki listed in
10.summary: User docs: create the New Features pages for Moodle LMS 4.2
description: Gather the new features and other issues labelled docs_required, to create the page.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Improve Grader report user interface
description: This issue is a large one focussed on improving usability and accessibility for teachers using Moodle gradebook (Grader report) on all browsers including touch screens and screen readers. The Moodle Gradebook Working Group met in June 2014 and determined a number of key required features, which are detailed on the specification at (still being finished). In a nutshell expect: Full screen spreadsheet-like display that scrolls well but has static headers and footers. Filters to quickly reduce the information being dealt with. Links to row/column editors for speed and affordances.
| Unsolvable | 1.summary: Gradebook table uses complex tables that are not accessible
description: Issue Teacher: Gradebook uses complex tables that are not accessible. Row headers are incorrect so the user thinks they are in a different row than they actually are. Student: Screen reader is incorrectly reading the wrong row header data because of the blank cell in the top left corner of the table. Standard Level WCAG 2 1.3.1 (A) Impact Critical Example Link Test Steps Login as teacher navigate to CF101 Click grades link Try to navigate the grades table. Recommendations Reduce complexity of grade editing tables or provide an alternative, accessible interface. Correct the structure of this complex table to ensure the row headers line up in the correct row. Test with a variety of screen readers. Explicitly set each table data cells row and column headers. edit 28/Aug/2014: Unable to reproduce identified behaviour now that the UCLA code has been integrated. Some improvements to accessibility have been implemented under this issue, namely: Top left cell(s) have been replaced with a single cell with rowspan that contains a label only visible to screen readers, namely get_string(participants); scope has been set to col to make it relate to the three or more columns it sits above. Header attributes removed from grade report cell and email cell; the only "header" for a row is the participants name cell. This results in better behaviour; when prompted about a given cell, a screen reader reads first the column information (category / course, then activity title), followed by row information (users name only), followed by the contents of the cell. Given that the floating user panel only contains the users name, this should be an acceptable tradeoff. Note that a lot of elements within these cells do not yet have their appropriate ARIA attributes (e.g. the user picture); this will be addressed in . Changes, mostly to "left" cells generated by get_left_rows(): Top-left filler cells Amended logic to generate a single big filler cell using rowspan, instead of multiple stacked filler cells. Set scope attribute to target columns below. Added a span to hold a label for said columns, using lang string participants. User rows Moved header class onto first column Added rowheader class to first column Changed all other columns to be td s rather than th s so screen readers dont count them as "row headers" Hid user avatars from screen readers Activity headers Hid activity icons from screen readers
2.summary: Accessibility improvements for gradereport course header and aggregation controls.
description: Provide accessibility improvements on the gradereport for screen readers. Specifically label-hides for the course header to indicate what is currently being displayed by the gradereport and altering the alt-text for the aggregation icon to better indicate its functionality.
3.summary: Prepare and integrate grader code from UCLA
description: UCLA have submitted some code for an updated view of the gradebook and it looks that we may accept this into core. It still needs a little bit of work as part of this issue including: Merge existing commits where relevant Update to meet coding style guidelines (Primarily JS) Move hardcoded styles to css Check SASS and produce a definitive CSS/Less set (as appropriate) and remove SASS files again There may be more...
4.summary: Correct existing behat tests, and write additional tests
description: For the new JS-focused functioanlity, we need to ensure that appropriate functional tests are in place.
5.summary: Activity name in grader report should be shown vertically
description: Activity names are displayed horizontally in grader report, which causes following problem: Varying column width; if activity name is small, then column is small. Column width is too big to show truncated activity name. We should consider doing following: Column width should be of equal size If activities dont fit in page; then rotate activity names and reduce column width to fit as many activities as we can.
6.summary: Improve behaviour of grader header, footer and sidebar on iOS 8 + IE
description: This issue relates to jankiness of the grader report on IE and iOS 8 Beta 4 (Safari). In iOS versions < 8, the scroll event is only fired at the end of the action, and not throughout so this is not an issue. From iOS 8 (tested with beta 4 on Safari), the scroll event is fired throughout. However, it is not fired frequently enough, resulting in a stuttering feeling. IE just sucks at tables and with a large table in the DOM, it stutters without any javascript at all. Adding the floating headers makes this more apparent for the same reason that iOS 8 appears to stutter - the scroll event is not called frequently enough, and it looks like its stuttering as a result. Weve tried several fixes for this already, and at present the code is highly optimised so that the fewest number of calculations occurs. The code also batches UI changes to reduce layout thrashing. In one sense, it would be nice to use a position of fixed, but this has its own issues too: iOS has a long-standing known issue where fixed items gradually disappear off the screen. As far as I can tell, there is no known fix for the iOS fixed issue, so to keep it from disappearing off screen, we would have to maintain the current solution of relative positioned elements. Maintaining two methods for this is not an ideal situation - especially just for a single ecosystem.
7.summary: Review and move AJAX grading code to YUI module
description: We have an AJAX interface for updating grades in the gradebook, but its off by default and its also pretty buggy. johno has started looking at it, the issues currently surrounding it, and is trying establish whether we want to enable this by default and move it into the YUI module. This is currently exploratory work and well need to discuss whether this is something we want enabled by default, or whether it will lead to overridden grades too frequently.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Improve Grader report user interface
description: This issue is a large one focussed on improving usability and accessibility for teachers using Moodle gradebook (Grader report) on all browsers including touch screens and screen readers. The Moodle Gradebook Working Group met in June 2014 and determined a number of key required features, which are detailed on the specification at (still being finished). In a nutshell expect: Full screen spreadsheet-like display that scrolls well but has static headers and footers. Filters to quickly reduce the information being dealt with. Links to row/column editors for speed and affordances.
### Response:
1.summary: Gradebook table uses complex tables that are not accessible
description: Issue Teacher: Gradebook uses complex tables that are not accessible. Row headers are incorrect so the user thinks they are in a different row than they actually are. Student: Screen reader is incorrectly reading the wrong row header data because of the blank cell in the top left corner of the table. Standard Level WCAG 2 1.3.1 (A) Impact Critical Example Link Test Steps Login as teacher navigate to CF101 Click grades link Try to navigate the grades table. Recommendations Reduce complexity of grade editing tables or provide an alternative, accessible interface. Correct the structure of this complex table to ensure the row headers line up in the correct row. Test with a variety of screen readers. Explicitly set each table data cells row and column headers. edit 28/Aug/2014: Unable to reproduce identified behaviour now that the UCLA code has been integrated. Some improvements to accessibility have been implemented under this issue, namely: Top left cell(s) have been replaced with a single cell with rowspan that contains a label only visible to screen readers, namely get_string(participants); scope has been set to col to make it relate to the three or more columns it sits above. Header attributes removed from grade report cell and email cell; the only "header" for a row is the participants name cell. This results in better behaviour; when prompted about a given cell, a screen reader reads first the column information (category / course, then activity title), followed by row information (users name only), followed by the contents of the cell. Given that the floating user panel only contains the users name, this should be an acceptable tradeoff. Note that a lot of elements within these cells do not yet have their appropriate ARIA attributes (e.g. the user picture); this will be addressed in . Changes, mostly to "left" cells generated by get_left_rows(): Top-left filler cells Amended logic to generate a single big filler cell using rowspan, instead of multiple stacked filler cells. Set scope attribute to target columns below. Added a span to hold a label for said columns, using lang string participants. User rows Moved header class onto first column Added rowheader class to first column Changed all other columns to be td s rather than th s so screen readers dont count them as "row headers" Hid user avatars from screen readers Activity headers Hid activity icons from screen readers
2.summary: Accessibility improvements for gradereport course header and aggregation controls.
description: Provide accessibility improvements on the gradereport for screen readers. Specifically label-hides for the course header to indicate what is currently being displayed by the gradereport and altering the alt-text for the aggregation icon to better indicate its functionality.
3.summary: Prepare and integrate grader code from UCLA
description: UCLA have submitted some code for an updated view of the gradebook and it looks that we may accept this into core. It still needs a little bit of work as part of this issue including: Merge existing commits where relevant Update to meet coding style guidelines (Primarily JS) Move hardcoded styles to css Check SASS and produce a definitive CSS/Less set (as appropriate) and remove SASS files again There may be more...
4.summary: Correct existing behat tests, and write additional tests
description: For the new JS-focused functioanlity, we need to ensure that appropriate functional tests are in place.
5.summary: Activity name in grader report should be shown vertically
description: Activity names are displayed horizontally in grader report, which causes following problem: Varying column width; if activity name is small, then column is small. Column width is too big to show truncated activity name. We should consider doing following: Column width should be of equal size If activities dont fit in page; then rotate activity names and reduce column width to fit as many activities as we can.
6.summary: Improve behaviour of grader header, footer and sidebar on iOS 8 + IE
description: This issue relates to jankiness of the grader report on IE and iOS 8 Beta 4 (Safari). In iOS versions < 8, the scroll event is only fired at the end of the action, and not throughout so this is not an issue. From iOS 8 (tested with beta 4 on Safari), the scroll event is fired throughout. However, it is not fired frequently enough, resulting in a stuttering feeling. IE just sucks at tables and with a large table in the DOM, it stutters without any javascript at all. Adding the floating headers makes this more apparent for the same reason that iOS 8 appears to stutter - the scroll event is not called frequently enough, and it looks like its stuttering as a result. Weve tried several fixes for this already, and at present the code is highly optimised so that the fewest number of calculations occurs. The code also batches UI changes to reduce layout thrashing. In one sense, it would be nice to use a position of fixed, but this has its own issues too: iOS has a long-standing known issue where fixed items gradually disappear off the screen. As far as I can tell, there is no known fix for the iOS fixed issue, so to keep it from disappearing off screen, we would have to maintain the current solution of relative positioned elements. Maintaining two methods for this is not an ideal situation - especially just for a single ecosystem.
7.summary: Review and move AJAX grading code to YUI module
description: We have an AJAX interface for updating grades in the gradebook, but its off by default and its also pretty buggy. johno has started looking at it, the issues currently surrounding it, and is trying establish whether we want to enable this by default and move it into the YUI module. This is currently exploratory work and well need to discuss whether this is something we want enabled by default, or whether it will lead to overridden grades too frequently.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Prepare Moodle for PHP 7.4
description: !taken_on_close.png! _(image taken on close, the jobs running those tests have been already removed)_ Accumulative branches (with all the pending stuff still not upstream) are: - master: (deleted) - 38_STABLE: (deleted) An, hopefully, small epic to turn Moodle ready for PHP 7.4 (end of 2019). When: Being cristal clear (aka transparent), the ideal target release for this is Moodle 3.8.0 (aka, supported since the very beginning of the branch), but be warned that full support may arrive later in any Moodle 3.8.x minor release in the branch, depending of a number of factors (extensions availability and bugs, 3rd part libraries, last minute surprises...). Some initial links: - Main changes explained: - Changes detailed: - Accepted RFCs: - Deprecations: Some basic requirements for this: - get unit and acceptance tests passing against all databases. - check all the changes details| have been reviewed and fixed (attached file). - ensure older versions of Moodle dont work with PHP 7.4 () - get travis| working with the new php version () - get moodle-php-apache| docker images working with the new php version - Update docs| (and others, see testing instructions) once this is ready. - ... All the issues belonging to this epic should be pulled into both MOODLE_38_STABLE and master (unless they are bug fixes requiring patching older, still supported, branches)
| Unsolvable | 1.summary: Update composer to get it working with phpunit >= 7.5.15
description: Right now we are using phpunit 7.5.14 The 7.x branch of phpunit only supports (officially) php71, php72 and php73. The 8.x branch of phpunit only supports php72, php73 and php74. Moodle 3.8.x is expected to support php71, php72, php73 and php74. The 8.x phpunit branch cannot be used for php71 (the min php72 requirement is locked). The 7.5 phpunit branch can be used for php74, if some changes are applied to it. This 7.5 phpunit PR has been accepted, enabling our tests to run without problem (other than the problems that will be fixed in the 7.4 epic: This issue is about to: 1) Wait till a new phpunit 7.5.15 is released. 2) composer update core to get the php 7.4 fix applied to our runs. 3) test moodle with php74 normally. Related topics: A) Surely for Moodle 3.9 release, that will support php72, php73 and php74... well have to bump to phpunit 8.x (because it matches the php versions 100). This is a recurring tasks to be performed yearly, for all the May releases. B) Trick: Until phpunit 7.5.15 is released anybody wanting to run unit tests agains php74 can apply for it by changing our composer.json this way (and then execute a composer update): code diff --git a/composer.json b/composer.json index 5a86efa985..5f8231ba5b 100644 --- a/composer.json +++ b/composer.json -11,7 +11,7 , "require-dev": - "phpunit/phpunit": "7.5.", + "phpunit/phpunit": "7.5.x-dev", "phpunit/dbunit": "4.0.", "moodlehq/behat-extension": "3.38.1", "mikey179/vfsstream": "^1.6", code
2.summary: Hodgepodge TODOs & mysteries related with php74 support
description: Hodgepodge issue to annotate all the incidences found while testing (manual or automated), inspecting logs... that still havent been investigated or are true mysteries needing some research. Of course, 7.4 related only. Will be adding them here, in the description, numbered, for further discussion. Once under control, they will be moved to a proper issue and documented here. A) line 255 of /backup/util/ui/backup_ui_setting.class.php throwing different, non-sense, errors. See . Requires investigation. B)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Prepare Moodle for PHP 7.4
description: !taken_on_close.png! _(image taken on close, the jobs running those tests have been already removed)_ Accumulative branches (with all the pending stuff still not upstream) are: - master: (deleted) - 38_STABLE: (deleted) An, hopefully, small epic to turn Moodle ready for PHP 7.4 (end of 2019). When: Being cristal clear (aka transparent), the ideal target release for this is Moodle 3.8.0 (aka, supported since the very beginning of the branch), but be warned that full support may arrive later in any Moodle 3.8.x minor release in the branch, depending of a number of factors (extensions availability and bugs, 3rd part libraries, last minute surprises...). Some initial links: - Main changes explained: - Changes detailed: - Accepted RFCs: - Deprecations: Some basic requirements for this: - get unit and acceptance tests passing against all databases. - check all the changes details| have been reviewed and fixed (attached file). - ensure older versions of Moodle dont work with PHP 7.4 () - get travis| working with the new php version () - get moodle-php-apache| docker images working with the new php version - Update docs| (and others, see testing instructions) once this is ready. - ... All the issues belonging to this epic should be pulled into both MOODLE_38_STABLE and master (unless they are bug fixes requiring patching older, still supported, branches)
### Response:
1.summary: Update composer to get it working with phpunit >= 7.5.15
description: Right now we are using phpunit 7.5.14 The 7.x branch of phpunit only supports (officially) php71, php72 and php73. The 8.x branch of phpunit only supports php72, php73 and php74. Moodle 3.8.x is expected to support php71, php72, php73 and php74. The 8.x phpunit branch cannot be used for php71 (the min php72 requirement is locked). The 7.5 phpunit branch can be used for php74, if some changes are applied to it. This 7.5 phpunit PR has been accepted, enabling our tests to run without problem (other than the problems that will be fixed in the 7.4 epic: This issue is about to: 1) Wait till a new phpunit 7.5.15 is released. 2) composer update core to get the php 7.4 fix applied to our runs. 3) test moodle with php74 normally. Related topics: A) Surely for Moodle 3.9 release, that will support php72, php73 and php74... well have to bump to phpunit 8.x (because it matches the php versions 100). This is a recurring tasks to be performed yearly, for all the May releases. B) Trick: Until phpunit 7.5.15 is released anybody wanting to run unit tests agains php74 can apply for it by changing our composer.json this way (and then execute a composer update): code diff --git a/composer.json b/composer.json index 5a86efa985..5f8231ba5b 100644 --- a/composer.json +++ b/composer.json -11,7 +11,7 , "require-dev": - "phpunit/phpunit": "7.5.", + "phpunit/phpunit": "7.5.x-dev", "phpunit/dbunit": "4.0.", "moodlehq/behat-extension": "3.38.1", "mikey179/vfsstream": "^1.6", code
2.summary: Hodgepodge TODOs & mysteries related with php74 support
description: Hodgepodge issue to annotate all the incidences found while testing (manual or automated), inspecting logs... that still havent been investigated or are true mysteries needing some research. Of course, 7.4 related only. Will be adding them here, in the description, numbered, for further discussion. Once under control, they will be moved to a proper issue and documented here. A) line 255 of /backup/util/ui/backup_ui_setting.class.php throwing different, non-sense, errors. See . Requires investigation. B)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: MUA-32: MUA project for Moodle 3.5 (Question Bank)
description: This epic is for MUA-32, to improve question bank functionality. Details of the user stories can be found in , and individual tasks within this epic should be linked to the relevant task in .
| Unsolvable | 1.summary: Create a "top" category in question bank
description: Currently there is a "fake" question category for each context. It does not exist in the database, but in places in the UI it is shown as a "fake" question category named top. We need to turn this into a real question category in the database, and enforce some validation rules to prevent modifying it, adding questions to it, or adding new questions categories as siblings of it. This allows us to (for example) add questions from any category in this course that have the label "midterm4" (because all categories will be a child of this top question category). We will need to modify import/restore to auto-create this top level category for backups older than $versionnumber (and enforce the other validation rules).
2.summary: Create new modal for tag add/edit/remove
description: We need to create a new modal to help with CRUD of question tags.
3.summary: Add WS for CRUD of tag and category fields
description: We need a WS to handle CRUD of the tag dialogue in .
4.summary: Add a tag filter to the "Add from question bank" dialogue
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a dropdown. The list fo tags should provide suggestions based on the tag containers for both the question tags and course question tags
5.summary: Update tag modal to allow managing of question and course context level tag instances
description: The same requirements as but for the tag modal added in .
6.summary: Add a tag filter to the "Add a random question" dialogue
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a dropdown. The list fo tags should provide suggestions based on the tag containers for both the question tags and course question tags
7.summary: Backup / restore of quiz should read/write some data from/into quiz_slots
description: should include tags data should read/write from/to quiz_slots.questioncategoryid, quiz_slots.includingsubcategories and quiz_slots.tags
8.summary: Add list of questions to the "Add a random question" dialog
description: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible. I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
9.summary: Add a section to the edit questions mform to allow managing the course context question tags
description: Currently the "tags" section of the edit question form will only add tags to the context that question exists in. E.g. If the question is a course category level question the tag instances will be added to the course category context. If its a course level question then the tag instances will be added to the course context. We need the ability to add both course context tag instances and course category context tag instances when editing a course category level question in the course context. Phew, that is confusing. What does this mean in practice? Background We have 2 teachers, t1 and t2 We have a course (c1) that exists in a course category (cat1). We have a course (c2) that exists in cat1 t1 and t2 are teachers in exactly 1 course each, c1 and c2 respectively. There is a question bank question (q1) that exists at the course category (cat1) level. The question q1 can be used by any course within cat1s context (both c1 and c2) Use case t1 logs in and views the question bank in c1. They change the category filter to see questions from cat1 which shows q1. They decide to edit q1. Currently, without any changes, t1 will see a single "tags" section in the edit form. Changes here will only add tag instances to the cat1 context which make them available to all courses in belonging to cat1, i.e. c1 and c2. However, t1 may want to add a tag instance that is specific to their course, c1, which shouldnt be visible to c2 or any other course. In order to solve that we can add a second "tags" section to the edit form which allows for managing tag instances at the c1 context level. Both tag sections will need to be named appropriately to reflect what context they are being applied to. Confirmations from As a teacher in a course who can edit a question from the course, I can add/modify/remove tags directly on the question, in the edit question form which will apply when the question is searched for in this course As a user who can edit questions outside of a course (belonging to the course category or site context), I can add/modify/remove tags directly on the question edit form, which will apply in all contexts the question can be used All teachers in a course can see the full list of tags either directly attached to the question from the question bank, or only attached to the question in this course Question tags are not specific to a single user (not private) Course backups should contain course level question tags A course restored from a backup should contain the same set of course level question tags pointing to the correct questions in all cases (same site, new site etc).
10.summary: I should be able to add random question by tag from course context or question context
description: Make sure that adding a random question by tag allows questions to be added by tag from the course context and the question context.
11.summary: I should be able to filter by tags in the course and question context in the question bank
description: Make sure that the tags filter in the question bank (both the question bank page and the "add from question bank" modal in a quiz activity) allows filtering of the questions by both the tag instances in the course context and question context.
12.summary: Backup / restore of questions should include all tags on all contexts
description: Make sure that backup and restore of questions includes tags in both the question context and the course context (if they differ).
13.summary: As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context
description: As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context Make sure the correct capability is being checked when managing tags in a course category (or above) context for the question bank.
14.summary: As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context.
description: As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context. Make sure were checking the correct capability when managing tags at the course context in the question bank.
15.summary: Add a tag filter to the "Question bank" page
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when editing questions from the Question Bank page. The list of tags should provide suggestions based on the tag containers for both the question tags and course question tags
16.summary: Display the count of questions on the "Add a random question" dialog
description: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible. I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
17.summary: Move tag data from quiz_slots table into its own table structure
description: As part of we added a "tags" column to the quiz_slots table which stores a JSON serialised list of tags for use when adding a random question by tag. It was discussed and raised that it would be better to have this data more formally structured in its own table that references the quiz_slots table rather than as a JSON string. While this wont represent any functional improvement for the user it should make the data more maintainable for the future so its worth doing. See this| comment for more details around the requirements of the tags stuff.
18.summary: Remove the Random question using a new category section from the Add a random question dialogue
description: As a teacher, I can add a random question to my quiz where the question is taken from a question category (optionally including sub categories) with optional filtering by tags. You will no longer be able to add a new question category at the same time as creating a random question (there is not enough room to display a preview of the search as well as this create new question category option).
19.summary: Create prototype site and setup initial example data
description: Create prototype site and setup initial example data.
20.summary: Allow quizzes to have random questions by tag
description: This is to allow having random question by tag, without doing quiz refactoring. At the moment, when adding a random question, an entry is created in the \question table. category is the category that the random question will be picked from questiontext is either 0 which means not to pick questions from subcategories or 1 which means picking questions from subcategories aswell We will use the questiontext field to store a json string that contains data about tag(s) as well. The category field will be 0 if the random question is a "random question by tag".
21.summary: Add support for course level tags when importing and exporting question
description: As required by MUA Question Bank project works, we need to support tags when importing and exporting questions.
22.summary: Improve performance of get_tags_by_area_in_contexts SQL query
description: Tim noticed while reviewing that the query for get_tags_by_area_in_contexts will not be very performant. It can easily be re-written to perform better. Andrew suggested something along the lines of: noformat select distinct t. from mdl_tag t inner join mdl_tag_instance ti on t.id = ti.tagid where component = abc and itemtype = def and contextid in (1,2,3,4,5); noformat
23.summary: Consolidate custom_view and fragment_view in quiz
description: Tim mentioned in his review of that the custom_view is no longer used since the old YUI dialogue has been removed so instead of having a new fragment_view we should just change the existing custom_view to work for the fragment and remove the fragment_view.
24.summary: Improve name of question_build_display_preference and question_build_edit_resources
description: Tim mentioned on that he doesnt like the names of the question_build_display_preference and question_build_edit_resources functions. Try to think of more appropriate names for the functions.
25.summary: Add new question tags capabilities and replace existing checks
description: At the moment we use question edit capabilities to check whether the user can tag a question or not. This issue is about create two new capabities moodle/question:tagall and moodle/question:tagmine and replace existing question capabilities checks for tagging.
26.summary: when searching for questions to add to a random question I see the question with its context clearly visible
description: Issue from I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
27.summary: Top category naming improvement (accessibility)
description: At the moment, "Top" categories are being displayed as "Top". It might improve accessibility to display them like "Top for xyz"
28.summary: Add unit tests for new functions introduced by
description: Add unit tests for quiz_build_random_question_tag_json quiz_extract_random_question_tags quiz_extract_random_question_tag_ids
29.summary: Show tag suggestions in tag modal fields
description: As reported by joeythibault on MUA-32| the tag modal fields are not displaying tag suggestions.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: MUA-32: MUA project for Moodle 3.5 (Question Bank)
description: This epic is for MUA-32, to improve question bank functionality. Details of the user stories can be found in , and individual tasks within this epic should be linked to the relevant task in .
### Response:
1.summary: Create a "top" category in question bank
description: Currently there is a "fake" question category for each context. It does not exist in the database, but in places in the UI it is shown as a "fake" question category named top. We need to turn this into a real question category in the database, and enforce some validation rules to prevent modifying it, adding questions to it, or adding new questions categories as siblings of it. This allows us to (for example) add questions from any category in this course that have the label "midterm4" (because all categories will be a child of this top question category). We will need to modify import/restore to auto-create this top level category for backups older than $versionnumber (and enforce the other validation rules).
2.summary: Create new modal for tag add/edit/remove
description: We need to create a new modal to help with CRUD of question tags.
3.summary: Add WS for CRUD of tag and category fields
description: We need a WS to handle CRUD of the tag dialogue in .
4.summary: Add a tag filter to the "Add from question bank" dialogue
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a dropdown. The list fo tags should provide suggestions based on the tag containers for both the question tags and course question tags
5.summary: Update tag modal to allow managing of question and course context level tag instances
description: The same requirements as but for the tag modal added in .
6.summary: Add a tag filter to the "Add a random question" dialogue
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a dropdown. The list fo tags should provide suggestions based on the tag containers for both the question tags and course question tags
7.summary: Backup / restore of quiz should read/write some data from/into quiz_slots
description: should include tags data should read/write from/to quiz_slots.questioncategoryid, quiz_slots.includingsubcategories and quiz_slots.tags
8.summary: Add list of questions to the "Add a random question" dialog
description: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible. I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
9.summary: Add a section to the edit questions mform to allow managing the course context question tags
description: Currently the "tags" section of the edit question form will only add tags to the context that question exists in. E.g. If the question is a course category level question the tag instances will be added to the course category context. If its a course level question then the tag instances will be added to the course context. We need the ability to add both course context tag instances and course category context tag instances when editing a course category level question in the course context. Phew, that is confusing. What does this mean in practice? Background We have 2 teachers, t1 and t2 We have a course (c1) that exists in a course category (cat1). We have a course (c2) that exists in cat1 t1 and t2 are teachers in exactly 1 course each, c1 and c2 respectively. There is a question bank question (q1) that exists at the course category (cat1) level. The question q1 can be used by any course within cat1s context (both c1 and c2) Use case t1 logs in and views the question bank in c1. They change the category filter to see questions from cat1 which shows q1. They decide to edit q1. Currently, without any changes, t1 will see a single "tags" section in the edit form. Changes here will only add tag instances to the cat1 context which make them available to all courses in belonging to cat1, i.e. c1 and c2. However, t1 may want to add a tag instance that is specific to their course, c1, which shouldnt be visible to c2 or any other course. In order to solve that we can add a second "tags" section to the edit form which allows for managing tag instances at the c1 context level. Both tag sections will need to be named appropriately to reflect what context they are being applied to. Confirmations from As a teacher in a course who can edit a question from the course, I can add/modify/remove tags directly on the question, in the edit question form which will apply when the question is searched for in this course As a user who can edit questions outside of a course (belonging to the course category or site context), I can add/modify/remove tags directly on the question edit form, which will apply in all contexts the question can be used All teachers in a course can see the full list of tags either directly attached to the question from the question bank, or only attached to the question in this course Question tags are not specific to a single user (not private) Course backups should contain course level question tags A course restored from a backup should contain the same set of course level question tags pointing to the correct questions in all cases (same site, new site etc).
10.summary: I should be able to add random question by tag from course context or question context
description: Make sure that adding a random question by tag allows questions to be added by tag from the course context and the question context.
11.summary: I should be able to filter by tags in the course and question context in the question bank
description: Make sure that the tags filter in the question bank (both the question bank page and the "add from question bank" modal in a quiz activity) allows filtering of the questions by both the tag instances in the course context and question context.
12.summary: Backup / restore of questions should include all tags on all contexts
description: Make sure that backup and restore of questions includes tags in both the question context and the course context (if they differ).
13.summary: As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context
description: As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context Make sure the correct capability is being checked when managing tags in a course category (or above) context for the question bank.
14.summary: As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context.
description: As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context. Make sure were checking the correct capability when managing tags at the course context in the question bank.
15.summary: Add a tag filter to the "Question bank" page
description: As a teacher, I can filter my question in courses based on tags. I should be able to filter by tag when editing questions from the Question Bank page. The list of tags should provide suggestions based on the tag containers for both the question tags and course question tags
16.summary: Display the count of questions on the "Add a random question" dialog
description: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible. I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
17.summary: Move tag data from quiz_slots table into its own table structure
description: As part of we added a "tags" column to the quiz_slots table which stores a JSON serialised list of tags for use when adding a random question by tag. It was discussed and raised that it would be better to have this data more formally structured in its own table that references the quiz_slots table rather than as a JSON string. While this wont represent any functional improvement for the user it should make the data more maintainable for the future so its worth doing. See this| comment for more details around the requirements of the tags stuff.
18.summary: Remove the Random question using a new category section from the Add a random question dialogue
description: As a teacher, I can add a random question to my quiz where the question is taken from a question category (optionally including sub categories) with optional filtering by tags. You will no longer be able to add a new question category at the same time as creating a random question (there is not enough room to display a preview of the search as well as this create new question category option).
19.summary: Create prototype site and setup initial example data
description: Create prototype site and setup initial example data.
20.summary: Allow quizzes to have random questions by tag
description: This is to allow having random question by tag, without doing quiz refactoring. At the moment, when adding a random question, an entry is created in the \question table. category is the category that the random question will be picked from questiontext is either 0 which means not to pick questions from subcategories or 1 which means picking questions from subcategories aswell We will use the questiontext field to store a json string that contains data about tag(s) as well. The category field will be 0 if the random question is a "random question by tag".
21.summary: Add support for course level tags when importing and exporting question
description: As required by MUA Question Bank project works, we need to support tags when importing and exporting questions.
22.summary: Improve performance of get_tags_by_area_in_contexts SQL query
description: Tim noticed while reviewing that the query for get_tags_by_area_in_contexts will not be very performant. It can easily be re-written to perform better. Andrew suggested something along the lines of: noformat select distinct t. from mdl_tag t inner join mdl_tag_instance ti on t.id = ti.tagid where component = abc and itemtype = def and contextid in (1,2,3,4,5); noformat
23.summary: Consolidate custom_view and fragment_view in quiz
description: Tim mentioned in his review of that the custom_view is no longer used since the old YUI dialogue has been removed so instead of having a new fragment_view we should just change the existing custom_view to work for the fragment and remove the fragment_view.
24.summary: Improve name of question_build_display_preference and question_build_edit_resources
description: Tim mentioned on that he doesnt like the names of the question_build_display_preference and question_build_edit_resources functions. Try to think of more appropriate names for the functions.
25.summary: Add new question tags capabilities and replace existing checks
description: At the moment we use question edit capabilities to check whether the user can tag a question or not. This issue is about create two new capabities moodle/question:tagall and moodle/question:tagmine and replace existing question capabilities checks for tagging.
26.summary: when searching for questions to add to a random question I see the question with its context clearly visible
description: Issue from I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
27.summary: Top category naming improvement (accessibility)
description: At the moment, "Top" categories are being displayed as "Top". It might improve accessibility to display them like "Top for xyz"
28.summary: Add unit tests for new functions introduced by
description: Add unit tests for quiz_build_random_question_tag_json quiz_extract_random_question_tags quiz_extract_random_question_tag_ids
29.summary: Show tag suggestions in tag modal fields
description: As reported by joeythibault on MUA-32| the tag modal fields are not displaying tag suggestions.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Core plugins review for removal
description: Plugins for removal from Moodle LMS and, if appropriate, adding to the plugins directory. For more details, please see the project page Core plugins review|
| Unsolvable | 1.summary: Set tool_replace maturity
description: Since the night of the times we have both tool_health and tool_replace in core. And they both are MATURITY_ALPHA, and we keep the same maturity on every stable release. IMO thats incorrect, if they are not ready, they should not be bundled. And if they are ready, they should not be alpha. This issue is about to decide about that detail and clean the non-sense (in any direction). Ciao :-)
2.summary: Remove picasa repository and portfolio from core
description: Picasa is abandonware from Google ( - we should remove portfolio and repository from Moodle.
3.summary: Remove Picasa portfolio from core
description: Picasa is discontinued since 2016 so it should be removed from core Moodle.
4.summary: Jabber should be removed as a standard notification plugin
description: As commented by mudrd8mz in , Jabber is not widely used these days so it would make sense to remove it as a standard notification plugin and add it to the Moodle plugins directory.
5.summary: WebCT question import format should be removed from core
description: WebCT was acquired by Blackboard in 2006, so I think we can safely remove the WebCT question import format from core.
6.summary: The Flash animation media player should be removed from core
description: The Flash Player was deprecated in 2017 and officially discontinued on 31 December 2020, so I suggest that media_swf is removed from core.
7.summary: Remove Word censorship filter (filter_censor) from core
description: Remove filter_censor from core and add it to the plugins directory. Eloy discovered that its not working as expected from, at least, 3.9 onwards: . And Helen mentioned that, even when it was working pre-3.9, it didnt work well (e.g. ).
8.summary: Remove Microsoft OneDrive (legacy) repository (repository_skydrive) from core
description: In Moodle 3.3, the skydrive repository was renamed to "Microsoft OneDrive (legacy)" because the API used by this repository plugin was deprecated by Microsoft. Users were encouraged to migrate to the new OneDrive repository right away some years ago (which is using oAut) so this repository_skydrive repository can be completely removed from Moodle core.
9.summary: Remove Quiz results block from core
description: The Quiz results block is hidden by default since Moodle 2.9. It is recommended to use the Activity results block instead, which works with any type of activity (not just quizzes). This issue is to remove block_quiz_results as a standard plugin and add it to the Moodle plugins directory.
10.summary: Remove tool_health from core
description: Remove tool_health and add it to the plugins directory. When moving it to the plugins directory, it would be nice to change the maturity from ALPHA to STABLE as mentioned in .
11.summary: The VideoJS Flash plugin should be removed from core
description: As mentioned by kabalin in a comment in we should remove the videojs flash plugin and all related code (loader, etc.) - including the VideoJS player settings RTMP streams (media_videojs | rtmp) and Use Flash fallback (media_videojs | useflash) and the references to Flash fallback in the strings configaudioextensions and configvideoextensions
12.summary: Remove Boxnet plugins from core
description: Boxnet is not widely used these days so it would make sense to remove them as standard plugins and add them to the Moodle plugins directory: repository_boxnet portfolio_boxnet
13.summary: Examview question import format should be removed from core
description: Examview question import format (qformat_examview) doesnt seem to be used any more. The last posts in are from over 10 years ago and there are no moodle.org discussions about Examview in the last 10 years. Thus, lets remove it from core! Nobody has mentioned Examview in any of the Moodle community discussions asking for feedback, so there doesnt seem any point in adding it to the plugins directory.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Core plugins review for removal
description: Plugins for removal from Moodle LMS and, if appropriate, adding to the plugins directory. For more details, please see the project page Core plugins review|
### Response:
1.summary: Set tool_replace maturity
description: Since the night of the times we have both tool_health and tool_replace in core. And they both are MATURITY_ALPHA, and we keep the same maturity on every stable release. IMO thats incorrect, if they are not ready, they should not be bundled. And if they are ready, they should not be alpha. This issue is about to decide about that detail and clean the non-sense (in any direction). Ciao :-)
2.summary: Remove picasa repository and portfolio from core
description: Picasa is abandonware from Google ( - we should remove portfolio and repository from Moodle.
3.summary: Remove Picasa portfolio from core
description: Picasa is discontinued since 2016 so it should be removed from core Moodle.
4.summary: Jabber should be removed as a standard notification plugin
description: As commented by mudrd8mz in , Jabber is not widely used these days so it would make sense to remove it as a standard notification plugin and add it to the Moodle plugins directory.
5.summary: WebCT question import format should be removed from core
description: WebCT was acquired by Blackboard in 2006, so I think we can safely remove the WebCT question import format from core.
6.summary: The Flash animation media player should be removed from core
description: The Flash Player was deprecated in 2017 and officially discontinued on 31 December 2020, so I suggest that media_swf is removed from core.
7.summary: Remove Word censorship filter (filter_censor) from core
description: Remove filter_censor from core and add it to the plugins directory. Eloy discovered that its not working as expected from, at least, 3.9 onwards: . And Helen mentioned that, even when it was working pre-3.9, it didnt work well (e.g. ).
8.summary: Remove Microsoft OneDrive (legacy) repository (repository_skydrive) from core
description: In Moodle 3.3, the skydrive repository was renamed to "Microsoft OneDrive (legacy)" because the API used by this repository plugin was deprecated by Microsoft. Users were encouraged to migrate to the new OneDrive repository right away some years ago (which is using oAut) so this repository_skydrive repository can be completely removed from Moodle core.
9.summary: Remove Quiz results block from core
description: The Quiz results block is hidden by default since Moodle 2.9. It is recommended to use the Activity results block instead, which works with any type of activity (not just quizzes). This issue is to remove block_quiz_results as a standard plugin and add it to the Moodle plugins directory.
10.summary: Remove tool_health from core
description: Remove tool_health and add it to the plugins directory. When moving it to the plugins directory, it would be nice to change the maturity from ALPHA to STABLE as mentioned in .
11.summary: The VideoJS Flash plugin should be removed from core
description: As mentioned by kabalin in a comment in we should remove the videojs flash plugin and all related code (loader, etc.) - including the VideoJS player settings RTMP streams (media_videojs | rtmp) and Use Flash fallback (media_videojs | useflash) and the references to Flash fallback in the strings configaudioextensions and configvideoextensions
12.summary: Remove Boxnet plugins from core
description: Boxnet is not widely used these days so it would make sense to remove them as standard plugins and add them to the Moodle plugins directory: repository_boxnet portfolio_boxnet
13.summary: Examview question import format should be removed from core
description: Examview question import format (qformat_examview) doesnt seem to be used any more. The last posts in are from over 10 years ago and there are no moodle.org discussions about Examview in the last 10 years. Thus, lets remove it from core! Nobody has mentioned Examview in any of the Moodle community discussions asking for feedback, so there doesnt seem any point in adding it to the plugins directory.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Standardise Bootstrapbase font-sizes
description: This is for Bootstrapbase font related issues
| Solvable | 1.summary: Add option to Scorm setting to display or hide activity name
description: From the discussion on , we are allowing to have option to display or hide the activity name. Currently, theres no option to do this in Scorm. This option could be used to prevent duplication of heading display on the page as mentioned in discussion also occurs in A draw back for implementing this is the possibility of losing the page hierarchy level for heading. Some user with screen reader or assistive technology use these header levels as page structure to navigate the web page. I also created a forum discussion to get feedback from the community
2.summary: META: Rescale the fonts in Bootstrapbase using px units so they are all at a reasonable size.
description: H1 and other headers are too big, and need to be rescaled. Other fontsizes will need to be checked. We need a baseline for different areas to use as a guideline too.
3.summary: META: Add/rescale headings for activities and resources page
description: Some activities and resources have headings while others do not. It should have to indicate clearly which activity/resource you are currently in. Please refer to the screenshot for reference. Activities that need headings particularly : Book Choice Forum Glossary Survey Wiki ... All headings should be at the top most of the content page. Please note: this meta is only focusing on adding/fixing the heading level and layout for the page. Other issues such as block header, contents font size, layout, positioning, etc. will not be fixed through this meta. We (Barbara and I) have plan to address those issues right after we are done fixing the page heading. For now, we are only focusing on heading. Thanks. Documentation page for HTML Guidelines:
4.summary: Remove classname from level 1 heading
description: Remove classname from level 1 heading as stated on the Moodle HTML guidelines ( Side note for splash theme, the page layout for this theme is set differently from other themes. For examaple in splash, site name is set to use instead of . The in splash is used to display the user name. This issue will removed the classname for , regardless where it used.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Standardise Bootstrapbase font-sizes
description: This is for Bootstrapbase font related issues
### Response:
1.summary: Add option to Scorm setting to display or hide activity name
description: From the discussion on , we are allowing to have option to display or hide the activity name. Currently, theres no option to do this in Scorm. This option could be used to prevent duplication of heading display on the page as mentioned in discussion also occurs in A draw back for implementing this is the possibility of losing the page hierarchy level for heading. Some user with screen reader or assistive technology use these header levels as page structure to navigate the web page. I also created a forum discussion to get feedback from the community
2.summary: META: Rescale the fonts in Bootstrapbase using px units so they are all at a reasonable size.
description: H1 and other headers are too big, and need to be rescaled. Other fontsizes will need to be checked. We need a baseline for different areas to use as a guideline too.
3.summary: META: Add/rescale headings for activities and resources page
description: Some activities and resources have headings while others do not. It should have to indicate clearly which activity/resource you are currently in. Please refer to the screenshot for reference. Activities that need headings particularly : Book Choice Forum Glossary Survey Wiki ... All headings should be at the top most of the content page. Please note: this meta is only focusing on adding/fixing the heading level and layout for the page. Other issues such as block header, contents font size, layout, positioning, etc. will not be fixed through this meta. We (Barbara and I) have plan to address those issues right after we are done fixing the page heading. For now, we are only focusing on heading. Thanks. Documentation page for HTML Guidelines:
4.summary: Remove classname from level 1 heading
description: Remove classname from level 1 heading as stated on the Moodle HTML guidelines ( Side note for splash theme, the page layout for this theme is set differently from other themes. For examaple in splash, site name is set to use instead of . The in splash is used to display the user name. This issue will removed the classname for , regardless where it used.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.7
description: In 3.7 we can remove functionality that was deprecated in 3.3 or earlier (see ) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
| Unsolvable | 1.summary: Deprecate the old lib/recaptchalib.php and its strings
description: In we switched over to the new recaptcha version. We should deprecate the old lib/recaptchalib.php and all the strings it uses such as "incorrectpleasetryagain" or "enterthewordsabove".
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.7
description: In 3.7 we can remove functionality that was deprecated in 3.3 or earlier (see ) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
### Response:
1.summary: Deprecate the old lib/recaptchalib.php and its strings
description: In we switched over to the new recaptcha version. We should deprecate the old lib/recaptchalib.php and all the strings it uses such as "incorrectpleasetryagain" or "enterthewordsabove".
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Chat issues
description: A list of improvements for the chat module.
| Unsolvable | 1.summary: Theres no whisper functionality in the chat.
description: Theres no whisper functionality in the chat. This is good if you want to stay in the group chat but have a parallel private dialogue.
2.summary: In the chat, and option to show the previous n messages, or n minutes, when you join.
description: Jabber plays back the previous 200 messages when you join a room, and it is really helpful. I have been missing this in the chat rooms at the iMoot.
3.summary: Chat: moderation and other features
description: Several people have asked at one point or another for moderation features in chat (e.g. to handle abusive students). There are also other features we might borrow from chat systems that could be very useful in Moodle. For now, this bug is here so that we remember...
4.summary: Add ability to restrict chat times
description: Often we are trying to encourage kids to join moodle - we would like to give them the opportunity to chat in a closed environment and in Moodle so that they get use to logging in and out. We decided to encourage them to have a go at Moodle and to encourage them we opened a chat room that we can monitor. The only problem is that you have to manually shut it down. If we could open it every day at lunch they teach others to join and then we are saving ourselves a lot of teaching time at joining and behavioural isues.The kidst become efficient at logging in and asking others to join the moodle group. Then later after they become efficient. We are goiing to turn on the modules and assessments but we need to restrict the chat times to closing.??
5.summary: Pop up box alerting to a new message in the chat activity
description: We urgently need a pop up facility adding to chat. We are in a very large department with no sound cards so the beep is no use at all to us. We really need a pop up to appear (similar to outlook when you get a new message?) when a new message is entered on to the chat. It is used to ask questions and we all contribute to the answers, so need to be alerted when a new question is entered.
6.summary: Show the number of participants in a chat on the course page.
description: In the same way you can see on the course page the number of messages pending to read in the forum rounded by (), some teachers demand the same utility next to the chat name. This will help the students to enter in the chat if they see there is somebody in the room.
7.summary: Autofocus at basic gui input text
description: I was asked by a customer to add focus to the input text in the basic gui each time the page loads. Its a great improvement in terms of accessibility. To accomplish this, you just need to add the attribute autofocus to the input.
8.summary: The chat module should not ignore the group mode
description: Regardless of the group mode set, all users end up joining the same chat room.
9.summary: User "is typing" indicator in Chat module
description: Just as any modern chat enabled application, Moodle should have the ability to indicate to users of the chat room that other users are typing. This would help to improve the communication flow of the chat room as users would now know when other users are in the process of giving feedback.
10.summary: Support image attachments to chat activity
description: Many times user want to send images in a chat activity but due to limitations they cant do it. User should send image through chat activity
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Chat issues
description: A list of improvements for the chat module.
### Response:
1.summary: Theres no whisper functionality in the chat.
description: Theres no whisper functionality in the chat. This is good if you want to stay in the group chat but have a parallel private dialogue.
2.summary: In the chat, and option to show the previous n messages, or n minutes, when you join.
description: Jabber plays back the previous 200 messages when you join a room, and it is really helpful. I have been missing this in the chat rooms at the iMoot.
3.summary: Chat: moderation and other features
description: Several people have asked at one point or another for moderation features in chat (e.g. to handle abusive students). There are also other features we might borrow from chat systems that could be very useful in Moodle. For now, this bug is here so that we remember...
4.summary: Add ability to restrict chat times
description: Often we are trying to encourage kids to join moodle - we would like to give them the opportunity to chat in a closed environment and in Moodle so that they get use to logging in and out. We decided to encourage them to have a go at Moodle and to encourage them we opened a chat room that we can monitor. The only problem is that you have to manually shut it down. If we could open it every day at lunch they teach others to join and then we are saving ourselves a lot of teaching time at joining and behavioural isues.The kidst become efficient at logging in and asking others to join the moodle group. Then later after they become efficient. We are goiing to turn on the modules and assessments but we need to restrict the chat times to closing.??
5.summary: Pop up box alerting to a new message in the chat activity
description: We urgently need a pop up facility adding to chat. We are in a very large department with no sound cards so the beep is no use at all to us. We really need a pop up to appear (similar to outlook when you get a new message?) when a new message is entered on to the chat. It is used to ask questions and we all contribute to the answers, so need to be alerted when a new question is entered.
6.summary: Show the number of participants in a chat on the course page.
description: In the same way you can see on the course page the number of messages pending to read in the forum rounded by (), some teachers demand the same utility next to the chat name. This will help the students to enter in the chat if they see there is somebody in the room.
7.summary: Autofocus at basic gui input text
description: I was asked by a customer to add focus to the input text in the basic gui each time the page loads. Its a great improvement in terms of accessibility. To accomplish this, you just need to add the attribute autofocus to the input.
8.summary: The chat module should not ignore the group mode
description: Regardless of the group mode set, all users end up joining the same chat room.
9.summary: User "is typing" indicator in Chat module
description: Just as any modern chat enabled application, Moodle should have the ability to indicate to users of the chat room that other users are typing. This would help to improve the communication flow of the chat room as users would now know when other users are in the process of giving feedback.
10.summary: Support image attachments to chat activity
description: Many times user want to send images in a chat activity but due to limitations they cant do it. User should send image through chat activity
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Pre-fetch support for existing modules
description: We must support pre-fetch for existing modules: Choice Glossary Survey Forum (investigate pre-fetch, probably 20 first discussions)
| Solvable | 1.summary: Prefetch choice
description: We should allow prefetching a choice. This prefetch should try to download the list of options, the selected option(s) and the results for offline usage.
2.summary: Prefetch survey
description: We should allow prefetching a survey. This prefetch should try to download the list of questions.
3.summary: Prefetch forum
description: We should improve forum prefetch. Right now, when a user loads a list of discussions we prefetch the posts of those discussions. Now we should disable that and implement a prefetch like in other modules. Since the amount of data can be really high, we should prefetch only the first 20 discussions (2 pages). Also, we should prefetch the embedded files and the attached files.
4.summary: Prefetch glossary
description: We should allow prefetching a glossary. We should prefetch all the possible filters (except search) and the entries. We need to check if we can also prefetch the required data to make auto-linking work too. We should try to prefetch embedded files too, although the WebService doesnt return data about those files. The main problem here is that we have no way to calculate the size of the download. The WebService already return the entries contents, and we dont have a WS to get the attached files. Ideally the WebService should return the list of files in each entry, and also accept a parameter to determine if we want the entries contents or not. Each entry should have the content size (without files) too.
5.summary: Decrease usage of getFiles in prefetch delegate
description: Right now the function getFiles is called in several places, and that can affect the apps performance since that function can perform several WebService calls. We can decrease the usage with some changes: In _getModuleStatus_, we should only call _getFiles_ if its really needed (_getRevision_ or _getTimemodified_ not implemented). In _getModuleDownloadedSize_ we could use a new handler function, _getDownloadedFiles_. If the handler uses component and componentId as it should, it should be able to retrieve the downloaded files without calling any WebService. In _removeModuleFiles_ we could use the same function as the previous point.
6.summary: Prefetch description files and embedded files - refactoring the existing prefetch
description: Right now in some modules we arent downloading description files (introfiles) and files embedded in content when we prefetch them, and we should do it. Embedded files dont have a file size, the only way to calculate it is to perform a head request. We decided that, if we detect there are embedded files in description/content and we dont have WS data for them, well show the "cannot calculate" message. In the future well receive embedded files from the WS. Also, in this issue we should check if invalidate files is really needed for the prefetched modules. Until now we used to invalidate all files when the user clicked refresh, but that can increase the network usage a lot for some activities.
7.summary: Improve "cannot calculate size" handling
description: Right now we use 0 as "cannot calculate", we should use -1. It would be nice to use a constant for this. Also, in course/section prefetch we should show the warning if any of the modules cant be calculated. Finally, for modules/sections where we can calculate some of the size but not all of them, it would be nice to show a message like "at least X MB".
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Pre-fetch support for existing modules
description: We must support pre-fetch for existing modules: Choice Glossary Survey Forum (investigate pre-fetch, probably 20 first discussions)
### Response:
1.summary: Prefetch choice
description: We should allow prefetching a choice. This prefetch should try to download the list of options, the selected option(s) and the results for offline usage.
2.summary: Prefetch survey
description: We should allow prefetching a survey. This prefetch should try to download the list of questions.
3.summary: Prefetch forum
description: We should improve forum prefetch. Right now, when a user loads a list of discussions we prefetch the posts of those discussions. Now we should disable that and implement a prefetch like in other modules. Since the amount of data can be really high, we should prefetch only the first 20 discussions (2 pages). Also, we should prefetch the embedded files and the attached files.
4.summary: Prefetch glossary
description: We should allow prefetching a glossary. We should prefetch all the possible filters (except search) and the entries. We need to check if we can also prefetch the required data to make auto-linking work too. We should try to prefetch embedded files too, although the WebService doesnt return data about those files. The main problem here is that we have no way to calculate the size of the download. The WebService already return the entries contents, and we dont have a WS to get the attached files. Ideally the WebService should return the list of files in each entry, and also accept a parameter to determine if we want the entries contents or not. Each entry should have the content size (without files) too.
5.summary: Decrease usage of getFiles in prefetch delegate
description: Right now the function getFiles is called in several places, and that can affect the apps performance since that function can perform several WebService calls. We can decrease the usage with some changes: In _getModuleStatus_, we should only call _getFiles_ if its really needed (_getRevision_ or _getTimemodified_ not implemented). In _getModuleDownloadedSize_ we could use a new handler function, _getDownloadedFiles_. If the handler uses component and componentId as it should, it should be able to retrieve the downloaded files without calling any WebService. In _removeModuleFiles_ we could use the same function as the previous point.
6.summary: Prefetch description files and embedded files - refactoring the existing prefetch
description: Right now in some modules we arent downloading description files (introfiles) and files embedded in content when we prefetch them, and we should do it. Embedded files dont have a file size, the only way to calculate it is to perform a head request. We decided that, if we detect there are embedded files in description/content and we dont have WS data for them, well show the "cannot calculate" message. In the future well receive embedded files from the WS. Also, in this issue we should check if invalidate files is really needed for the prefetched modules. Until now we used to invalidate all files when the user clicked refresh, but that can increase the network usage a lot for some activities.
7.summary: Improve "cannot calculate size" handling
description: Right now we use 0 as "cannot calculate", we should use -1. It would be nice to use a constant for this. Also, in course/section prefetch we should show the warning if any of the modules cant be calculated. Finally, for modules/sections where we can calculate some of the size but not all of them, it would be nice to show a message like "at least X MB".
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Remaining Moodle 4.0 release issues
description: This epic is to merge all current issues that are still open or in development for the Moodle 4.0 release. This will give us just one place to check our progress to releasing 4.0. For convenience, this search shows issues in this epic which are not yet finished| This may be easier than the list below.
| Unsolvable | 1.summary: Add information in relevant upgrade.txt files
description: Given all of the new navigation code coming in / landed (primary & secondary navigation) we should make heavy mention of how to use it within appropriate upgrade.txt files. As it currently stands the general structure is solidified but minor changes are still happening in the original epic as of MDL creation. Adrian edit All of this information should be in the developer docs. So in addition to adding comments on the new methods for developers to use, we need to create the documentation that outlines the new classes and how the developers can interact with them with their own plugins.
2.summary: Quiz and question bank tertiary navigation followup
description: Given the following designs on figma we need to implement the tertiary navigation for the Quiz module and Question Bank: Teacher view: Student view: Some of this work was done in , but it was agreed to revert all commits related to Quiz and Question bank and reintroduce the code separated in logical commits. This is a list of the issues/regressions that needs to be addressed and included to the general tertiary navigation changes: The dropdown selection does not get preserved when a validation error happens. To reproduce: As a teacher, go to the Question bank. Select Export Press "Export questions to file" without selecting a File format Validation fails Expected: The dropdown will show "Export" as selected. Actual: The dropdown selects the first item on the list (Questions) instead of the "Export" menu item. This behavior is also noticed with import. For instance in step 2 select "Import" and then in the following page, click "Import" button at the bottom. You would see validation fails and user sees "Question" instead of "Import" in the menu item. Students are presented with the option to re-attempt the quiz regardless of the enforced delay between attempts (Identified in , ). Login as a teacher, edit the settings for the quiz and set an enforced delay between 1st and 2nd attempts of 1 minute and an enforced delay between later attempts of 30 seconds. Login as a student and attempt the quiz. Go back to the Quiz. Expected: you should not have an option to re-attempt the quiz until the time delay between attempts has passed. There should be a text notifying the user that he must wait until can re-attempt the quiz Actual: there is an option to attempt quiz which triggers an error. And, more generally, the button to start/continue a quiz attempt/preview should have an appropriate button lable at all times. That is, initially the button is Attempt quiz, but if you leave in the middle of a quiz attempt, and come back later, it will say Continue the last attempt, etc. Basically, the logic that was there before was right, and should not have been changed. The access message for the quiz is shown at the bottom, instead it should be shown after the tertiary nav. Update the heading text to "User overrides"/"Group overrides" in the user/group override pages and move it under the tertiary navigation. Move the Add category section (Question bank > Categories) to its own page and add a button (primary) "Add category" in the Question bank > Categories tertiary navigation which redirects to this page. Remove the cog icon from the quiz activity. When the quiz has a time limit, there needs to be some spacing between that and any other information such as the grading method. We should either display these paragraphs in separate lines as the original behavior or display them on the same line with some responsive spacing. Also, we should move them just below the tertiary navigation buttons. The Edit quiz button should be removed from the tertiary navigation and new item Questions (linking to this page) should be added to the secondary navigation instead. The Attempt quiz button should be primary for students. NOTE: I wasnt able to replicate this on the QA site, but it would be good to double check whether there are any existing scenarios where this button is displayed as secondary. The default visible items in the secondary navigation should be organized in the following order: Quiz, Settings, Questions, Results, Question bank. The secondary navigation item Overrides should be renamed to Settings overrides and placed in the secondary more menu by default. When a student starts an attempt in a quiz with a set time limit, a modal should be displayed notifying the student about the time limit restrictions as in 3.11. As a student, in the quiz summary page the Submit all and finish button should be primary The review quiz page should be max-width.
3.summary: Page tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Page activity. Identified issues: -The heading should be removed in the page activity (view page)- -The activity setting "Display page name" doesnt do anything in Boost which is a confusing. We should try to find a way to hide this option if secondary navigation is present.- Edit: As per Sanders comment| it was decided within the team to opt instead to remove the setting altogether.
4.summary: Scorm tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the SCORM activity. Identified issues: The Preview and Enter buttons and the content should be aligned to the left in the SCORM view page as presented in the design prototype When "Display course structure on entry page" is set to "yes" the content structure needs to be aligned correctly in the page. Align the Download dropdown button properly to the right (remove right margins) in the Reports page Add headings in every Reports page Update the redirect back flow in the Track details page to properly redirect to the previous page as presented in the design prototype Add headings in the pages under Attempts (Learning objects, Interaction) The Exit activity button should be moved from the header to the tertiary navigation in the scorm player, -renamed to Exit- and it should redirect back to the course homepage, Site homepage, or scorm view page depending on course format (single activity) and skipview settings within the scorm. The Enter button is not available when Disable preview mode is enabled. This seems to be a regression. The Display activity name is only applicable to classic at the moment. In boost the activity name is not displayed in the page content in the scorm player page. We should either consider hiding this setting when using boost or update the description and note that this setting does not affect boost related themes. - Edit: Remove the setting based on Remove the activity description and completion data from the SCORM player page. Remove the activity description and completion data from the pages under Attempts (Learning objects, Interactions) Remove the activity description and completion data from the Track details page. When the scorm attempt is in preview or review mode, the text that appears above the player stating that is in review or preview mode is a bit small/lost - it should be a lot more prominent as if in preview mode - no attempt data will be stored, and if in review mode it wont always update an existing score. Remove hard-coded styling in The exit button should not exist when viewing the scorm in a new window
5.summary: Update My Overview block styling
description: Given the supplied below we need to do the following: Remove the text from the dropdowns Update the styles & templates to better reflect the template in the list view i.e. adding the course image Make the summary display mode look like the list view with the exception it also contains the course description Edit: Updated figma design -
6.summary: Further improve login page
description: Im going to suggest that we further simplify the design of the login page as there are a number of UI features which belong in the previous century, and the design is still slightly too cluttered. In short, Im going to suggest that we should consider some more drastic changes: Remove the Footer entirely - especially when it is empty, but also consider hiding the performance info (collapse it perhaps) when stats are shown Make the login region wider. For some reason it appears narrower now than it does on the screenshots from when Angelia tested - considerably narrower. Remove the Cookies warning - we should only show information about this when a login fails because cookies are not enabled. Its a standard feature of browsers and very very few people disable cookies. Logins are too prevalent these days to consider disabling them entirely. Reword the "Forgotten your username or password?" link to simply "Forgot password?" Remove the "Remember username" checkbox entirely. This should be the default. I quite like what Chrome have done whereby they show information on how to open a private browsing window if you _do not_ want your login to be remembered. This is a much safer and more user-friendly approach. Make the username and password fields _taller_. At the moment theyre really short but they are the main focus of this page. We should make the area that users are expected to interact with more prominent. Equally we can increase the padding around them to make the area clearer. Move the Language selection to beneath the username and password fields. The Username field should be the first field in the tab order The "Username / email" placeholder text should read "Username or email" rather than having a slash (not very user friendly) Id like to suggest that we move the Cookie warning, to a new page which opens in a popup. It can also have the information on starting a private browsing session, and any other help we need to show in future (i.e. password recovery for admin, etc.). Comparing a number of other big login screens, none of them has the "Remember" or Cookie warnings. . Mockups Current: !Current without debug footer.png|thumbnail! Minimum width: !Current but wider (380px min).png|thumbnail! Simplified by removing Cookies prompt, and replacing "Remember username" with instructions for private browsing !With private browsing prompt.png|thumbnail!
7.summary: Update the secondary navigation for single activity course format
description: When using single activity format in a course, the secondary navigation only shows the navigation items related to the activity (module context) while the course related navigation items are missing on the page. Currently, the only way to access these course administration items is through the administration block. Therefore we need to update the secondary navigation and also include the course administration items as proposed on the following figma prototype The secondary navigation menu for a single activity course: should contain two items: Course and Activity both items should display dropdown menus on click the Course dropdown menu should contain the navigation items related to the course administration (Settings, Participants, Grades, Reports, ...) The Activity dropdown menu should contain the navigation items related to the activity administration (Link to the activity view page, Settings, Advanced grading, Permissions, ...) once a given navigation link has been accessed from the secondary navigation dropdowns or any other nested link within, the appropriate secondary navigation item should be still highlighted.
8.summary: Book tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Book activity. Identified issues: Print book and Print this chapter should be opened in a new window after clicking on the links. Highlight Book in the secondary navigation once the user is on the Add new chapter page (currently nothing is highlighted) In zero state (the book does not have any content yet), when students accesses the Book activity, they should be able to see the books description and a notification (info), stating that the book activity is empty.
9.summary: The Overrides secondary navigation item should be placed into the more menu by default
description: We should place the Overrides secondary navigation item in the more menu by default. For consistency reasons this change should be generally applied to every module (Assignment, Quiz, Lesson) that has this item in the secondary navigation. Additionally, the link attached to this node should redirect to the User overrides page by default instead of Group overrides Behat tests will have to be updated with default landing page change
10.summary: Arrange blocks between My courses & My dashboard
description: -Confirm and alter the block ordering within the dashboard & my courses pages currently defaults are being set within but we need UX to confirm exactly which blocks should appear where and when i.e. recently accessed courses added to the my courses page during installation and what blocks should be relocated during site upgrade.- -EDIT: Summary from UX discussion- -For a new site, dashboard should have:- -Timeline block (main region)- -Calendar block (main region)- -Recently accessed items (block drawer, this one needs confirming still)- -For an existing site, during upgrade, dashboard should retain all blocks the site has there currently, but the course overview block is no longer required since the courses are now displayed in the my courses page. So the course overview block should be removed from the dashboard.- -EDIT 04 Feb 2022- -To clarify:- -The dashboard should not have the recently accessed courses block- -The my courses page should be ordered by Last accessed by default- Revised requirements as part of this issue: New default blocks for the dashboard content area - timeline, calendar block Recently accessed items should be in the right area To account for mobile - the external blocks function should return a dummy course overview block until the app has been upgraded.
11.summary: Assignment tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Assignment activity. Identified issues: The View gradebook link should be removed from the secondary navigation Remove the Add submission, Edit submission (available after submitting) Remove submission (available after submitting) buttons which are duplicated and displayed at the bottom of the page. Add submission button should be primary Remove the activity completion section from the View all submissions page. Add heading (Submissions) in the View all submissions page Highlight the "Overrides" secondary navigation item in the Add user/group overrides pages Add heading in the Add user/group overrides pages Add a notification (info) in the user/group overrides pages when there are not overrides present instead of displaying a blank page. Remove the assignment name part from the heading in the Advanced grading page Remove the completion data and activity description in the Add submission page. Add title heading in the Add submission page. Update the breadcrumbs in the Add submission page and add an additional item "Add submission" to reflect the current location Move the separate/visible groups selector element just below the Grading summary heading in the forum view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the following code as it is no longer required
12.summary: Forum tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Forum activity. Identified issues: Display an info notification in the forum view page when there are no discussion topics added yet (zero state) In the Subscriptions secondary navigation page, add headings for both View subscribers ("Subscribers") and Manage subscribers ("Manage subscribers") pages. Display a notification in the View subscribers page when there are no subscribers yet in the forum (zero state) Do not display the Manage subscribers option in the tertiary navigation selector in Subscriptions when forced subscription mode is selected (this is the existing behavior in 3.11). Also, in this case the we do not need to display the tertiary navigation selector element at all as only one item will is available which relates to the current page. Remove the subscription mode selector element from the Manage subscribers page Remove the activity description from the Add new discussion topic (advanced) page. Add heading in the Add new discussion topic page (advanced) Update the breadcrumbs in the Add new discussion topic (advanced) page and add "Add discussion topic" to the breadcrumb trail When you access a given discussion topic, the settings dropdown menu should be changed to a dropdown button (right aligned) and should be vertically aligned with the rest of the selector elements (Display replies .. , Move discussion to...) Add heading in the Edit discussion topic page ("Edit discussion topic") Remove the activity description in the Edit discussion topic page Update the breadcrumbs in the Edit discussion topic page and add "Edit discussion topic" to the breadcrumb trail In the delete forum discussion page, highlight the Forum item in the secondary navigation menu In the delete forum discussion page, remove the activity description and activity completion section. Update the breadcrumbs in the Add reply (advanced) page and add "Add reply" to the breadcrumb trail In the split discussion page (has to be reply in a discussion topic), highlight the "Forum" item in the secondary navigation menu. In the split discussion page, remove the activity description and the completion section Update the breadcrumbs in the Split discussion page and add a link to the parent discussion to the breadcrumb trail Move the heading below the forum selector element in the Reports page and update the heading to "Forum summary report" If there are no results in the reports page, display an info notification instead of the heading. Found function forum_update_subscriptions_button stale, as its not used anymore after the recent changes made in . The forum subscription when changed by the user, it redirects back to the forum tab. Instead, it should be there on the subscription page. Remove the following code as it is no longer required
13.summary: Category page breadcrumbs and other navigation related issues
description: This is how the breadcrumb looks like on the current category page (/course/index.php?categoryid=X) !Screenshot 2021-11-25 at 11.07.25.png|width=600! There are multiple problems with this breadcrumb: The first element in it is "Course", which is a page that now competes directly with "My courses". The user would be confused if both pages are available. The course category page will now be mostly accessed from the "Site home" by default, so having the "Courses" page as the first element in this breadcrumb just adds to the confusion. After some thinking, we agreed on developing a mechanism that uses whichever option is selected in the setting defaulthomepage as the first element in this breadcrumb. Examples: If "Site" is selected... !Screenshot 2021-11-25 at 11.14.38.png|width=600! ...the breadcrumb will look like this: !Screenshot 2021-11-25 at 11.15.03.png|width=600! If "Dashboard" is selected... !Screenshot 2021-11-25 at 11.13.23.png|width=600! ...the breadcrumb will look like this: !Screenshot 2021-11-25 at 11.15.21.png|width=600! UPDATE: We have agreed to take the following actions: Every page in the course category context should have the base breadcrumb trail "Courses / \Category name". This means that in every course context page we will display breadcrumbs, due to the necessity to keep the link to the Courses page, which otherwise will be lost. On exception is when the defaulthomepage is changed to My courses, then the My courses node is prepended to the breadcumbs (ex. "My courses / Courses / \Category name") We should fix all the cases where the primary/secondary items are not properly highlighted We should update the header text wherever is necessary to properly reflect the current category context The figma prototype now covers in detail the required changes in the course category pages (
14.summary: Re-implement breadcrumbs in the course pages
description: We need to re-implement the breadcrumbs for the course pages that have been removed in Things to do: Revert the course breadcrumbs removal in Breadcrumb items (links) that exist in the primary and secondary navigation should be removed from the breadcrumb. ex. The breadcrumb "My courses > Course1 > Badges > Manage badges > Badge1" should be "Manage badges > Badge1" as the items (links) "My Courses", "C1" (course) and "Badges" are already highlighted and can be accessed through the primary or secondary navigation.
15.summary: Course and category management secondary and tertiary navigation
description: Steps to reproduce: Login as admin Go to "Site administration > Courses > Manage courses and categories". Create a new category with a super-long name (for instance, "Miscellaneous with a long long long long title to test if its truncated. Etiam massa orci, vehicula sed ligula sit amet, lobortis eleifend magna") Expected behaviour The secondary navigation is displayed. Current behaviour Only the "More" button of the secondary navigation appears. !secondarynavigationwithlongcategoryname.png|thumbnail! After having a discussion regarding this issue, it was decided that we need to modify the secondary and tertiary navigation in the course categories management page. These proposed improvements should also resolve this problem in the course category context. The following changes need to be done: In the course category context the following items should be present in the secondary navigation menu: Category - link to the course category view page (originally Category: \categoryname, the category name part needs to be removed) Settings - link to the edit category settings page (originally Edit this category, needs to be renamed to Settings), Permissions Cohorts Filters Restore courses Learning plan templates Competency frameworks Content bank. The header text in the course category pages should correspond to the category name (ex. Miscellaneous) In the category view page (Category) The Category secondary navigation item should be highlighted Add the following items in the tertiary navigation: Navigation selector element containing a list (links) of the available course categories (aligned to the left) Search courses input field (aligned to the left. right next to the category selector) More dropdown element (aligned to the right), containing the following items: New course (link to the Add a new course page) Manage courses (link to the Course and category management page related to the given category) Remove the Manage courses button from the page header Remove the Add a new course and Courses pending approval buttons (at the bottom of the page) In the Add a new course page The Category secondary navigation item should be highlighted In the Course and category management page (Note: the breadcrumbs displayed on the prototype should be ignored) The Category secondary navigation item should be highlighted Add the following items in the tertiary navigation: Navigation selector element containing (aligned to the left) the following items: Course categories and courses, Course categories and Courses. Search courses input field (next to the the view selector) When Courses view is selected, add another navigation selector element right next to the general navigation selector element which will contain the the available categories. Remove the Viewing dropdown Update the heading to Manage courses and categories In the settings cog dropdown menu for each category add View item (link to the category view page) In the Permissions page Add the following items in the tertiary navigation Navigation selector element containing (aligned to the left) the following items: Permissions, Check permissions and Assign roles. These requirements are presented on the following figma design prototype
16.summary: General tertiary navigation followup
description: This is a followup to address any general tertiary navigation issues in the activities. Identified issues: Move Locally assigned roles from the secondary navigation in activities into the tertiary navigation selector in the Permissions page (Secondary navigation More menu > Permissions). Add the navigation selector element into the Locally assigned roles page as well (Permissions, Check permissions, Locally assigned roles) Remove Logs and Competency breakdown from the secondary navigation in activities (These links can be accessed through Course > Reports) Remove Courses from the breadcrumbs shown in the activities. Update the heading text in the Enrolled users (Participans) page from Participants to Enrolled users.
17.summary: Tertiary navigation in course completion
description: Currently, a tab structure is used for navigation between the course completion pages. We need to replace the tabs with a navigation selector element and place it above the heading text.
18.summary: Document and inform the public about changes to theme plugins
description: Update to have a section that specifies what theme plugin developers have to do to get their plugins working. Please see for the specifics of what theme developers need to do. Please also include information about how to fix their problems, such as how to add back the settings cog, or a link to how to include the secondary navigation. Also please create a forum post pointing to the Moodle 4.0 developer update to help inform more people.
19.summary: Remove the secondary navigation menu in the calendar page
description: Secondary navigation menu is currently displayed on the calendar page with different items based on the capabilities of the authenticated user. !calendar_page.jpeg|thumbnail! Based on the 4.0 navigation requirements a secondary navigation menu should not be displayed on this page.
20.summary: Glossary tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Glossary activity. Identified issues: The description should be moved above the tertiary navigation in the Glossary view page. The activity description should not be displayed in the Add entry page The heading should be updated in the Add entry page The activity description should not be displayed in the Edit entry page Add heading in the Add/edit entry pages Add a back button (secondary) in the tertiary navigation in the view entry page which will redirect back to the glossary view page. Also, remove the existing anchor element from the page Add Cancel button (secondary) in the Import entries page which will redirect back to the glossary view page. Add back button (secondary) in the Export entries page Printer friendly version page should be opened in a new window
21.summary: Chat tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Chat activity. Identified issues: Remove the activity name part from the heading in the Past sessions page. Move the separate/visible groups selector element just below the tertiary navigation elements in the chat view page (The group mode needs to be set in the activity settings to be able to see the groups selector)
22.summary: Lesson tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Lesson activity. Identified issues: Add more spacing between Edit and Grade essays button (we need to define how much spacing should be added and be consistent) Edit button should be renamed to Edit lesson Move Edit page content from the page header to the tertiary navigation in the Lesson view page (secondary button) Add margins on the buttons in the user/group overrides pages Remove the activity description and completion data in the user/group overrides pages Add heading in the user/group overrides pages Add a notification (info) in the user/group overrides pages when there are not overrides present instead of displaying a blank page. Remove the link to grades in Overview and Detailed statistics pages in Reports Add heading in Overview and Detailed statistics pages in Reports just below the tertiary navigation Do not display the activity description in Overview and Detailed statistics pages in Reports Move the separate/visible groups selector element just below the heading in Overview and Detailed statistics pages in Reports (The group mode needs to be set in the activity settings to be able to see the groups selector)
23.summary: Survey tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Survey activity. Identified issues: Add padding at the bottom of the tertiary navigation elements in the Response reports page Move the Visible/Separate groups selector below the heading in the Response reports page (you will need to change the group mode setting to Visible groups or Separate groups in the activity to be able so see this selector) When nobody has yet completed the survey, display an info notification below the heading (or below the visible/separate groups selector if it exists) in the reponse reports pages
24.summary: Add headings to all reports displayed in the course context.
description: Some of the reports have headings and others dont. The goal is to have all of these reports looking consistent. Reports that need headings: Logs Live logs Activity report Course participation Activity completion
25.summary: Plugin set 4 of 4 tertiary navigation followup
description: During the PR and IR phase it was found that for the Forum activity: The "Search forum" in the activity redirects us to Course page and not to the secondary nav of the activity. This does deviate from the consistency. We need to decide how to move ahead with this behavior. We would also need help of UX team for the same. Additional issues found during integration: . -Forum- quote-Navigate to the subscriptions tab in the secondary nav:- -2 drop downs are noticed.- -Subscribers- -a) View subscribers- -b) Manage subscribers- -Shows the potential subscribers and Existing subscribers tables.- -This selection is saved in the session. Whenever the user comes back to the- -subscribers tab, the previous option is remembered.- -So for me selection is not saved - when I come back to Subscriptions tab I always have View subscribers selected even though I selected Manage subsribers last time- quote As mentioned by Sujith, this functionality is expected now. . -Quiz- -The dropdown selection does not get preserved when a validation error happens. To reproduce:- -As a teacher, go to the Question bank.- -Select Export- -Press "Export questions to file" without selecting a File format- -Validation fails- -Expected: The dropdown will show "Export" as selected.- -Actual: The dropdown selects the first item on the list (Questions) instead of the "Export" menu item.- -Students are presented with the option to re-attempt the quiz regardless of the enforced delay between attempts (Identified in , ).- -Login as a teacher, edit the settings for the quiz and set an enforced delay between 1st and 2nd attempts of 1 minute and an enforced delay between later attempts of 30 seconds.- -Login as a student and attempt the quiz.- -Go back to the Quiz.- -Expected: you should not have an option to re-attempt the quiz until the time delay between attempts has passed. There should be a text notifying the user that he must wait until can re-attempt the quiz- -Actual: there is an option to attempt quiz which triggers an error.- -The access message for the quiz is shown at the bottom, instead it should be shown after the tertiary nav.- We are moving all the Quiz related issues to Forum -Found function forum_update_subscriptions_button stale, as its not used anymore after the recent changes made in .- -The forum subscription when changed by the user, it redirects back to the forum tab. Instead, it should be there on the subscription page.- We are moving all Forum related issues to
26.summary: Improve the UI/UX of the recently accessed items block design for suitability in the Moodle 4.0 blocks drawer
description: When adding the recently accessed items block to the drawer it shows a horizontal scroll. This is not ideal. See options discussed here. () The ideal solution is to stack 3 items vertically and add a show more link to load more. !Recently accessed - Show more.png|thumbnail! We should estimate the work involved in this to determine if this is feasible before starting QA. If not we will stick with the current block layout for 4.0, add it to the blocks drawer as is, and address this issue for 4.1.
27.summary: Update the footer in the mobile view.
description: quoteWe agreed that the footer should always be displayed on small screens. However, I think we could improve its current design a little bit. (There are no prototypes for the footer on small screens my bad ) quote !Screenshot from 2022-02-07 15-05-46.png! Transparent background Dark text Same padding as the rest of the page content (see ) Powered by Moodle string aligned with the rest of the text (to the left) Original post|
28.summary: Keep management settings button on the same line in my courses (mobile view)
description: When in mobile view the settings button (three vertical dots) moves below the "My courses" title. Can we move this to be right aligned with the title in the mobile view?
29.summary: Word wrap long activity names in the context header.
description: When the activity name is long the activity type and name shift to below the activity icon. Can we instead please have these elements stay in the same spot, but have the text wrap in that area instead. Attached images show how it looks now and how it should look.
30.summary: Change the format of breadcrumbs in mobile view
description: We want to change a few things with how the breadcrumbs look in the mobile view. Remove the border around the breadcrumbs There is too much line-height ^Screenshot from 2022-02-07 16-02-46.png Currently: !Screen Shot 2022-02-09 at 5.09.47 pm.png|thumbnail! Should be: !Screenshot from 2022-02-07 16-02-46.png|thumbnail! quoteIt would be even better if we could truncate the breadcrumb items, so they always fill one row, like in the prototypes quote !Screenshot from 2022-02-07 16-02-55.png|thumbnail!
31.summary: Increase the strength of title text
description: There are several text sections around Moodle that should be bolder like the figma designs. The greeting message Block titles Course sections
32.summary: Decrease gap between course sections and the section description
description: The prototype has a gap of 12px between the course section title and the description. We currently have a bigger gap. Can we please bring this inline with the design? The design: !Screenshot from 2022-02-09 13-32-14.png|thumbnail! Current: !Screenshot from 2022-02-09 13-32-26.png|thumbnail!
33.summary: Document new activity iconography in component library
description: We should document the design details of the new icons in the component library, and in dev docs. Including rule-set used for BBB, which should be applied consistently: So heres what I propose as a rule-set to deciding background colours: We allow the actual icon to use the brand colours (so the darker blue in case of BBB). Ideally all plugin icons use the category assigned background colours| For BBB, which would fall in the communication (or maybe collaboration) category, this means green. If the assigned background colour would compromise the branding of the plugin too much, then the plugin will use the default background colour of grey
34.summary: Moodle 4 Admin pages should ALL have the admin search box
description: The admin search box should be always there also on: admin category pages specific admin settings pages Having the search option handy top right all the time will really speed up moving around. And it would add to the overall consistency of the Admins UX. (The idea first raised in the "Navigation issues in site administration pages" issue, added here following this suggestion| from sujith .)
35.summary: Remove the "Course categories" dropdown from the categories page
description: color:0e101aAlthough these category pages need a complete redesign from scratch, we could make them simpler by removing the "Course categories" selector, which only adds noise to the page since users have:color -color:0e101athe breadcrumb to navigate back to the parent category pagecolor- color:0e101athe browser "back" button to navigate back to the parent category pagecolor color:0e101athe current child categories printed on the page itself as collapsible elements, which are also linkscolor !Screenshot 2021-11-25 at 11.23.19.png|width=600!
36.summary: Mobile view nav bar header improvements
description: This is what it looks like now: !Screen Shot 2022-02-09 at 11.25.08 am.png|width=286,height=53,thumbnail! There are still a few areas that are different to the figma prototype. Can we please change the following: Change the hamburger: Remove the border Use the font awesome icon "fa-bars" Update the edit mode to remove the text in mobile view. It should look like this: !Screenshot from 2022-02-07 13-31-50.png|width=282,height=48,thumbnail! Initial report|
37.summary: Change padding / margins in the mobile view
description: Observed issues: (x) Right now, there s a lot of padding and margins in the containers. They push the content up to around 38px away from the screen borders (x) These different paddings and margins also affect the alignment of page elements (titles, content, etc.) Can we please make the border just a standard 8px. !Screenshot from 2022-02-07 13-51-47.png! Original post| Current page layouts: My courses: !Screenshot from 2022-02-09 11-59-21.png|thumbnail! Course page: !Screenshot from 2022-02-09 11-59-30.png|thumbnail! Activity: !Screenshot from 2022-02-09 11-59-40.png|thumbnail! Site administration: !Screenshot from 2022-02-09 11-59-50.png|thumbnail!
38.summary: Course section headings should have similar styling to form section headings.
description: The course section headers behave the same as form section headers and should have the same design.
39.summary: Style main container scrollbar to match the style of the drawers scrollbar
description: Main container still uses native browser styling for scrollbar. It should match the look and feel of the drawer scrollbars
40.summary: Change the first tab label to General from Site administration
description: The first tab in the site administration is to change from General to Site administration (screenshot included).
41.summary: Section expand/collapse icons not centred in circles
description: These are irritatingly not in the middle. See screenshots: !expanded.png|thumbnail! !collapsed.png|thumbnail!
42.summary: Increase the font size of the description in all activities.
description: We altered the look of the course completion details and summary to match the main course page, but we would like the summary in the activity page to be the same as it previously was, and not smaller as it currently is.
43.summary: Show the course index on all pages within a course
description: Currently the course index is available on the course page and when within activities. Some user feedback has been received suggesting the course index should also be available when on the other course pages such as settings, participants, grades, etc. Lets review. 15/12/2021 update I attached a screen recording to this issue. When switching back and forth between the course page and other pages (settings, etc) we are jumping between showing the course index (when open in the course page) and not (elsewhere). This feels a bit disorienting and also causes the secondary nav to shift. I tend to agree that keeping it open on the other pages (when open on the course page) is preferable. 6/01/2022 update Agreed to go ahead and introduce the course index on all other course pages
44.summary: Move adminpresets to admin/presets
description: dobedobedoh and brendanheywood have mentioned that: "I wish /adminpresets/ was instead /admin/presets/ so that CLI tab autocomplete wasnt broken trying to run CLI scripts". When I worked on , I didnt realise it was possible to create this component inside admin/presets (so thanks mudrd8mz for pointing that admin/roles is a similar case). This issue is about moving the content in the adminpresets folder into admin/presets for consistency and also to make happy our beloved developers :)
45.summary: Provide option to not use the Dashboard
description: In Moodle 4.0, the Course overview block is being moved from the Dashboard to My courses. This will leave only the calendar and timeline blocks on the Dashboard. For sites which dont use the calendar or timeline blocks, such as sites offering self-paced courses, it would be good to provide the option to disable the Dashboard. -Adrian edit Weve had a few developers ask about being able to customise the primary header. Can we please investigate expanding this issue to cover adding and removing any combination of the primary navigation items?-
46.summary: Manage blocks page should remind about unneeded blocks
description: The admin page Manage blocks at /admin/blocks.php should display a reminder about the /admin/search.php?query=unaddable settings and perhaps provide a link to this search result page, so the admin can check if the enabled blocks can actually be added to courses, and so s/he can sync both types of settings as needed.
47.summary: Starter site admin preset improvements
description: Lets make some improvements to the Starter site admin preset based on community feedback in the discussion Site admin presets in Moodle 4.0| We also need to consider new features and improvements in 4.0, such as the BigBlueButton activity, and decide on appropriate settings for them in the Starter preset. ---- This is the list of settings/plugins to be changed (after discussing and agreeing on them): BLOCKS The following blocks will be disabled by default in the Starter preset: Online users (block_online_users). In Moodle 4.0 it has been removed from the Dashboard. Recently accessed courses (block_recentlyaccessedcourses) and Starred courses (block_starredcourses). The My Courses page lists recently accessed courses, so there is no point in adding the block to the Dashboard. There is also no point in adding the Starred courses block to the Dashboard because you can only star courses on the My courses page. QUESTION TYPES Essay and Description question types will be re-enabled in the Starter preset (as suggested by timhunt in an issue). GUEST ACCESS As recommended by thornedu in the forum| the following settings related to Guest access will be disabled for the Starter preset: Plugins / Enrolments / Manage enrol plugins > "Disable Guest access" Plugins / Authentication / Manage authentication > Guest login button = Hide. ACTIVITY CHOOSER To reduce the information displayed in the activity chooser: Activity chooser tabs (activitychoosertabmode) will be set to "Starred, All, Recommended" (no Activities or Resources tabs).
48.summary: Improve the loading time of the course index when the user is not in the course page
description: Since the course index appears in all pages related to the course, not only in activities and the course view. This implies that in most pages the course index content can be fully cached to speed up the page loading. All those new pages with the course index cannot alter the course structure itself so they can use the previously loaded version of the course index. This does not happen with the course index and activity pages as they can, for example, alter the activity completion.
49.summary: Improve links to services and support
description: To make it easier for our users to get additional assistance we want to improve the links to Moodle Service providers -and ensure the site support email address is always configured-. For this purpose we want to introduce the following changes: 1. Add a link in the new ? pop-up that takes users to a new to be created page on moodle.com. This page will present the user with various options to get further support for their Moodle site. 2. Add a notification message in the admin notification screen after install / upgrade that points to the same page defined above in 1. -3. Make the site support email address mandatory (Administration > Server > Support contact) and also make this available in the new ? pop-up.- Suggested page URL to point to: moodle.com/help . Admin notification pages !final-screenshot.jpg|width=615,height=354! As illustrated in the image above, lets add a new notification above the existing "donation" one, with the Moodle Partner logo and the following message: "Support and services Need support for your Moodle site? Find a Moodle Certified Service Provider near you at moodle.com/help" The Moodle Partner logo image is here: ^moodle-partners-logo.zip . Help (?) pop up changes This is the design that I came (and tested briefly) for the help pop-up: !footer.png|width=325,height=317! Document and guides Link: same as current "Moodle Docs for this page" Font-awesome icon: fa-book Services and support Link: new services page (this issue) Font-awesome icon: fa-life-ring Note: the "services and support" footer link should only be visible for admins.
50.summary: Follow up: using "chevrons" instead of "carets" would give Moodle a more modern feel
description: In the prototypes we changed the "caret" icon found in menus and dropdowns to a "chevron" one. So these elements: !Screenshot 2021-10-28 at 14.56.56.png|width=420,height=133! !Screenshot 2021-10-28 at 14.57.00.png|width=211,height=57! Would look like this: !Screenshot 2021-10-28 at 14.58.01.png|width=400,height=119! !Screenshot 2021-10-28 at 14.58.26.png|width=237,height=46! The problem is that, right now, the "caret" icon is printed using sorely CSS in an ::after pseudo-element. To print a "chevron" in there we need to make deeper changes in the code than we first thought.
51.summary: Update tertiary navigation in the database module
description: Some updates to the tertiary navigation in the database module are required in order to improve the accessibility in these pages. In the "Fields" tab, change the naming of the Create a new field selector option to "Manage fields". On the same page, update the default option in the field type selector from Choose... to "Create a new field" On the same page, add a "Manage fields" heading !screenshot.jpeg|thumbnail!
52.summary: Add standard method to retrieve all navigation nodes for a requested section
description: This is specific for the secondary navigation views. The standard navigation has a few nodes (user, reports, badges, and question bank) that are categories. There are a couple of callbacks that extend the navigation tree and this allows a lot of freedom to add an update the tree anywhere. In this case we are looking at the potential of third party plugins adding navigation nodes into the above mentioned categories. On those pages we need to retrieve the navigation tree for that category and display the inserted third party categories and child nodes. As we have to do the same thing in all of these places we should have a centralised function.
53.summary: Missing a divider between the "My courses" page header and content
description: This is how it looks right now: !Screenshot 2021-11-04 at 10.20.15.png|width=658,height=249! This is how it looks in the prototype: !Screenshot 2021-11-04 at 10.20.22.png|width=660,height=257!
54.summary: Display a title in the dashboard page
description: We need to step back on our decision to remove the greeting message from the dashboard after the user leaves the page. We should always display a page title, for accessibility reasons and also to make the experience more solid when navigating through the primary navigation. My initial idea was to always keep the greeting message in the dashboard even when the user browses away from the page and come back later. Im aware that this option was already discussed and denied in the past, so I suggest we change the page title from the greeting to "Dashboard" when the user comes back to this page. So, when the user logs in the greeting would be the dashboard title (as it is right now): !Screenshot 2021-11-18 at 14.46.15.png|width=460! Then, if the user goes away from the dashboard and comes later (in the same session), the title of the page would be "Dashboard": !Screenshot 2021-11-18 at 14.46.28.png|width=460!
55.summary: Make rounded corners more rounded by default
description: Change the default boost theme border-radius from .25rem to .5rem. Comparison: !rc-1.jpg|width=600! !rc-2.jpg|width=600! (In the images above: Left: .25rem; Right: .5rem) Just as an example, I achieved the results above by adding the following SCSS to the "Raw initial SCSS" theme configuration field. $border-radius: .5rem !default;
56.summary: Database tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Database activity. Identified issues: Move the separate/visible groups selector element just below the tertiary navigation in the database view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the completion data and activity description from every page except the database view page. Pages that should not display the description and completion: Add new entry page Edit entry page Export entries page Delete entry page Manage fields page Add field page Edit field page Delete field page Import a preset page Use a preset page Templates pages Presets pages Add headings in the Templates pages Set the List template to be the default template to land on in Templates Add template should be changed to Add entry template in Templates
57.summary: Label secondary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Label resource. Identified issues: Rename the Label secondary navigation item to Course. The label resource does not have a dedicated view page and clicking on this secondary nav item takes the user to the course page.
58.summary: Choice tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Choice activity. Identified issues: Move the separate/visible groups selector element just below the Responses heading in the responses page and the view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the duplicated Responses node from the breadcrumbs in the Responses page
59.summary: Workshop tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Workshop activity. Identified issues: Add some spacing at the bottom of the tertiary navigation selector element in the Submissions allocation page. Add headings below the tertiary navigation selector element in the Submission allocation pages (Manual allocation, Random allocation, Scheduled allocation)
60.summary: Feedback tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Feedback activity. Identified issues: Add heading ("Templates") in the templates page Add heading ("Analysis") in the analysis page below the Export to Excel button Move the separate/visible groups selector element just below the Analysis heading in the analysis page (The group mode needs to be set in the activity settings to be able to see the groups selector) Add Show responses heading below the tertiary navigation selector in the show responses page
61.summary: Update date in security.txt for 4.0 release to factor in release delay
description: Given the large move of release dates for 4.0 (and 4.1), the security.txt expiry date as added in no longer seems sufficient, since it would only be approximately 2 months. The minors on earlier versions can be updated in May minors, but ideally 4.0 will be released with a security.txt that is valid until around the the expected release date of 4.1 (+3 weeks as standard).
62.summary: Enable MoodleNet integration by default
description: Now that we have MoodleNet in a good beta version, we are looking at switching tool_moodlenet|enablemoodlenet on by default. We were originally looking at doing this earlier, but then MoodleNet ran into some problems and so we switch the default to off. -This is only for new installations. No need for an upgrade step here.- EDIT (SB): 18 Jan 2022 Discussed with the product team; agreed yes we want to enable by default. Need to: Enable the setting Enable the footer Default values for MoodleNet settings need to be updated Testing should involve end to end importing of MoodleNet content into LMS, both when logged into MoodleNet and when not logged in. EDIT (SB) 19 Jan 2022 Enabling by default is for both new installs and upgrades. For sites that are upgrading we should inform the admin by sending an admin notification. Something along the lines of: quoteIn Moodle 4.0 the MoodleNet integration has been enabled. Users with the ability to edit courses will now see a link to MoodleNet in the activity chooser. Clicking on this link will take them to MoodleNet where they can select and import content into their Moodle course. Please visit for MoodleNet| for more information. You can change the MoodleNet settings or disable this feature. quote WHERE MoodleNet settings should link to disable this feature should link to
63.summary: Stronger highlighting of the selected activity is required.
description: This is for the UX team to review if it is necessary to increase the darkness of the highlighted activity in the course index. suggests that the current contrast is not enough. Edit: agreed to go ahead, see Rafas comment below
64.summary: Badge pages polish
description: A couple of things to bring the badge pages inline with the figma design| "Add a new badge" button should be btn-primary When there is no badges, the notice should have a blue background instead of a red one. When there are no badges the "manage badges" buttons should not be displayed.
65.summary: The active activity is not always displayed in the course index.
description: I think most of the concerns in have been addressed, but there are situations where the topic will be collapsed and entering the activity will not force open the topic to show the current activity that we are in. Can we please review this situation and make sure that we are always aware (in the course index) of our location?
66.summary: Review padding at the top of the page
description: The padding between the primary navigation and the context header is substantial. It tends to stand out more when there is no background set and there is nothing but white space. Lets have a discussion about whether we should reduce the space between the primary navigation and the context header.
67.summary: Display some help text with the new subscription mode change action bar
description: See following forum subscription page: !Screenshot_2022-01-17 Subscribers.png|width=800! The tertiary navigation lacks any context as to its purpose, but is consistent with elsewhere and should be resolved by The select element on the far right of the page also lacks context, but acts as a form submission when changed. Apart from the user no longer being asked for confirmation before submitting the form (), they are given no context about what it actually is and/or refers to - a help icon would be good here Pinging tsala for her thoughts
68.summary: Provide a contact form which sends to the site support email and replace mailto link in footer
description: This is a follow up from There is some concern that the public email address would be misused. As a result it is better to hide this for not logged in users. -The proposal for this issue is to:- -If the supportpage is set, show the link to the support page- -If not, show a link to a generic contact form which will send an email to the support email address- The updated footer support link logic for this issue is: If the supportpage is set, show the link to the support page (which will open in a new window). If not, and SMTP is configured on the Moodle site, link to a generic contact form within Moodle, which will send an email to the support email address. If not, and SMTP is _not_ configured, still direct to the internal page, but display a message that it cant be sent from that page. If the user is logged in, also show them a mailto link to the support email address. If not logged in (or a guest user), then omit the support email address. Uli has provided UX mockups for both the email received by support, as well as the version of the page described in point 3 above: Email mockup: !support-email-mockup.png|thumbnail! When internal form hidden (SMTP not configured): !support-form-no-smtp-config-mockup.png|thumbnail! (Note some of the suggested mockup strings have been used, but were not all designed to be final strings, so some have been refined/changed since. The icon was also changed to an appropriate fontawesome one, since the cone doesnt exist in our icons or FA.)
69.summary: Change UI for Add activity, Add block, Add topic and similar elements
description: Based on rafaellechugos comment on , theres a new design to implement for Add activity or resources, Add block, Add topic and every other similar element. The border of those elements should be solid instead of dashed. A) !-A.png|width=842,height=96! B) !-B.png|width=523,height=830! C) !-C.png|width=837,height=482! D) !-D.png|width=807,height=283! E) !-E.png|width=810,height=470! Also, there were some design specifications from that were not implemented e.g the "plus" icon should be inside a box also with rounded corners. EDIT: Also address the issue raised in the linked duplicate issue.
70.summary: Document and list all new behat steps.
description: Please update with a list of all new behat steps that have been introduced in 4.0. We currently give a couple of examples, but really we should just list everything that has been changed. Please format this in a way that is useful for a plugin developer. The current Behat section could do with an overhaul. Suggestions from Jonathan Champ quoteThese mostly made sense, but it would be nice to have it spelled out a bit more. It says "modname activity" and Im fairly sure that for the "quiz" activity module, it would be "quiz activity", but Im not sure if resource modules are different or not. I dont know if something special needs to happen for blocks. At one point, it says that two examples "work fine" and its not clear if the author is bolding the word "fine" to imply a negative emotion or to imply a technical compromise or if it has any additional meaning at all. When I say something is "fine", I mean that it meets the definition, but only barely. Example: "What do you think of Red Lobster? Its fine." For reference, Red Lobster is a chain restaurant in the United States that does indeed sell food, but I would not describe it as either good or bad. It simply is. quote
71.summary: Dialog should have the action button on the right
description: As commented by dougiamas in : quote1) OS X, Windows and Ubuntu ALL put the "Cancel" button on the left and the action button on the right. 2) This makes sense to me because dialogs are like a step in a process/story, and we are used to moving left to right in those situations (is probably reversed for RTL speakers). "Cancel" is like going BACK while "Save" or Add" in this case is like going FORWARD. quote Also jverdaguer highlighted the inconsistency between Moodle and the Moodle app, which has the action button on the right. !dialogue_boxes.png|thumbnail! Thus, lets change the order of the dialog buttons to have the action button on the right.
72.summary: current class no longer applied to the section when it is the highlighted section
description: Ref: When highlighting a section, the current class is no longer applied to the section as it was before in M3.11-. Suggested fix is to add $data->iscurrent = true; to export_for_template() of /course/format/classes/output/local/content/section.php when ($format->is_section_current($thissection)) is true. Or change /course/format/templates/local/content/section.mustache to use highlighted instead of iscurrent on the section li tag.
73.summary: Default dashboard page showing wrong header and secondary nav
description: Problem: The Default dashboard page is showing the site admin header and the site admin secondary nav which get in the way of having a real view of the dashboard page during customization. Also the active top nav indicates Site admin instead of Dashboard. The change to 4.0 from 3.11 made it more confusing. !comparison between 311 and 40.png|thumbnail! Recommendations: Change header to Default dashboard page Remove secondary nav Make Dashboard active on the top nav
74.summary: Bump NodeJS version, dependencies, and update JS build process, drop IE support
description: panel:title=Policy: Keeping us on top of nodejs/npm LTS versions (including jumps to next LTS)|borderStyle=dashed|borderColor=ccc|titleBGColor=F7D6C1|bgColor=FFFFCE Since September 2018 (): This policy will be applied to ALL supported branches, normal and security-only. This policy wont update any tool per se, unless strictly needed by nodejs/npm own dependencies/changes. It wont include npm audit changes either. Those are handled apart. So, normally, only changes to .nvmrc and package.json will happen. That will be achieved by: update .nvmrc to the new version. run nvm install && nvm alias default node && nvm use to install, set it as new default and use it for the next steps. update package.json and set engines to the new restriction (>= new version and < next major). When needed to bump components or run some audit, a new issue, similar to this, will be created and these steps performed in order to get a renewed npm-shrinkwrap.json file: remove node_modules & npm-shrinkwrap.json npm cache clear --force npm install npm shrinkwrap In any case, simple update or complete components bump, run grunt and verify that all the generated css/js/map stuff remains the same. If there are differences in the generation... it will need to be analysed and decided if: accepted (so everything, shrinkwrap and generated css/js/map) lands or not accepted (and only change .nvmrc and package.json) instead). The resulting branches will be sent to github (or similar), making a peer-review request here so both travis and cibot will verify that all them pass ok. Changes will be normally integrated and the NodeJSVersion template| and NodeJSExactVersion| templates will be updated with latest information in the Docs. TODO (): A job @ CI servers will be, daily, using latest lts/current version to detect if there are npm-shrinkwrap.json changes. It will fail when that happens and inform integrators. Jumps to lts/next will be detected manually,. panel Im raising this issue because of some problems with our current build identified in . Essentially, our current minification options include an option called mangle (on by default) which in some situations can cause broken JS to be generated. We dont know if/when this may crop up, and the relevant project seems to be abandoned. Unfortunately disabling the mangle option causes minified files to be changed, which is something that we try to avoid because it messes with third-party developers and their build processes. Given the combination of these things I think that we need to: update the Grunt JS config to set the mangle option to false update our NodeJS version to the latest LTS (16.14.0) update our package versions This has the following effects: updates all built JavaScript (YUI and AMD) replace the current babel-minify plugin with a supported minification system (terser) This combination fixes the issue blocking . I believe we should apply this to master, and stables so that all versions of Moodle have the same NodeJS version support as per policy. For master I think we should consider dropping support for IE and adjusting our browser compatibility list accordingly to: remove IE update the browser usage restriction to cover the top 0.3 instead of 0.25 (this removes support for Android 4.4 released in October 2013) This combinations of things will: drop use of many of the legacy polyfills for things like for...of, and async which makes debugging async functions much _much_ easier This was agreed in back in August 2020, and was intended to happen in the Moodle 3.10 release. This was not done at the time (due to time constraints). Because of this change there _will_ be build output changes in third-party plugins. We do try to avoid this wherever possible but sometimes it is unavoidable. We technically _can_ get away with _not_ modifying minified files, but the older our babel packages get the harder it becomes to upgrade in the future. We will be supporting Moodle 3.9 until May 2023, and it makes more sense to make this change to Moodle 3.10 so that all versions from 3.9 to 3.11 have the same build process, and Moodle 4.0 has the same process but with IE support dropped.
75.summary: Improve flexibility of site support form and consistency of site support info provided in Moodle
description: Remove SMTP limitation The current implementation of the site support form checks if outbound SMTP is configured in Moodle, and if not will not provide the form (instead showing a message and linking logged in users to the support email address). Since sites may be using another external MTA, we should allow sending via the form regardless, and only display the aforementioned message if the system registers that it has failed (if it succeeds with the request, but the mail fails to send from the MTA, that is out of the view of Moodle so out of scope to be handled). We should also then display the form again below the message, so that if its a temporary outage they can try again, and worst case still have their message available to copy out and email through manually. Remove support email where it is exposed elsewhere In we removed access to the support email address from the new "footer" link, but there are some existing places in Moodle where it is also available, which should act consistently and link to the support form (and also not expose the now compulsory support email address to unauthenticated users). An example of this is /error/index.php, but we need to check for any other leaks.
76.summary: Allow secondary navigation to be shown for behat in quiz
description: We have a comment in . Kindly remove this comment and the following if condition for BEHAT_SITE_RUNNING. You may also require to adjust the behat tests accordingly.
77.summary: Improve access to a users custom reports
description: Users can can access their list of reports if $CFG->enablecustomreports is set (it is by default, ) and they have any of the following capabilities: moodle/reportbuilder:editall, moodle/reportbuilder:edit, moodle/reportbuilder:view, Relevant method: However, without moodle/site:configview there is no obvious way for them to navigate to their list of reports (note they can still access it if directly linked to the page) In Workplace we use a custom launcher: !Screenshot_2022-02-28 Dashboard.png! LMS should have a similar alternative (e.g. something on the user menu) that doesnt rely on granting access to view the admin tree to all users From discussion with emiliolozano, sanderbangma & rafaellechugo (please update issue as you see fit, and/or to add clarification :))
78.summary: Allow full customisation of the primary navigation
description: A large number of developers have asked about the possibility of customising the primary navigation. We had an investigation into doing that in , but a complete solution like what is being implemented for the dashboard, is not possible for all primary navigation items in the time remaining for the 4.0 release. This issue is to provide a way to show and hide primary navigation nodes (tabs) in a less strict fashion. For this adding variables to theme/config.php are for developer alterations and the same internal checks are not required from core. The primary navigation is only visible in the boost theme, and making changes in core related to theme specifics is not allowed. So we have to work with that restriction. By adding a config to the boost theme, the specific layout pages can retrieve that information and then alter the primary class accordingly. We could help out here by providing a method to help.
79.summary: Timeline block - search for multilang
description: Hi! (I was testing the Timeline block on the app, but this is LMS) If you have an activity that is shown on the Timeline block titled "One option EnglishEspa ol", you will be able to search it by "One option" but NOT by "One option English" Thanks! PD I am aware this is an edge case
80.summary: Expand course section icons are not rendered properly in RTL
description: In LTR, expand icons are rendered as ">". In RTL, theyre also rendered the same (">") instead of "<". !screenshot-1.png|thumbnail!
81.summary: Duplicated link name "Home" when viewing a badge
description: When I view a badge as a student, I see 2 links/buttons above the badge and they both have the same name: Home. In my site, one of them sends me to Site Home (course/view.php?id=1) and the other one sends me to My courses (root of the site). I think its confusing to have 2 buttons with the same name if they send me to different places. As an admin I can see: Home, Participants, Content Bank, Home, Site administration
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Remaining Moodle 4.0 release issues
description: This epic is to merge all current issues that are still open or in development for the Moodle 4.0 release. This will give us just one place to check our progress to releasing 4.0. For convenience, this search shows issues in this epic which are not yet finished| This may be easier than the list below.
### Response:
1.summary: Add information in relevant upgrade.txt files
description: Given all of the new navigation code coming in / landed (primary & secondary navigation) we should make heavy mention of how to use it within appropriate upgrade.txt files. As it currently stands the general structure is solidified but minor changes are still happening in the original epic as of MDL creation. Adrian edit All of this information should be in the developer docs. So in addition to adding comments on the new methods for developers to use, we need to create the documentation that outlines the new classes and how the developers can interact with them with their own plugins.
2.summary: Quiz and question bank tertiary navigation followup
description: Given the following designs on figma we need to implement the tertiary navigation for the Quiz module and Question Bank: Teacher view: Student view: Some of this work was done in , but it was agreed to revert all commits related to Quiz and Question bank and reintroduce the code separated in logical commits. This is a list of the issues/regressions that needs to be addressed and included to the general tertiary navigation changes: The dropdown selection does not get preserved when a validation error happens. To reproduce: As a teacher, go to the Question bank. Select Export Press "Export questions to file" without selecting a File format Validation fails Expected: The dropdown will show "Export" as selected. Actual: The dropdown selects the first item on the list (Questions) instead of the "Export" menu item. This behavior is also noticed with import. For instance in step 2 select "Import" and then in the following page, click "Import" button at the bottom. You would see validation fails and user sees "Question" instead of "Import" in the menu item. Students are presented with the option to re-attempt the quiz regardless of the enforced delay between attempts (Identified in , ). Login as a teacher, edit the settings for the quiz and set an enforced delay between 1st and 2nd attempts of 1 minute and an enforced delay between later attempts of 30 seconds. Login as a student and attempt the quiz. Go back to the Quiz. Expected: you should not have an option to re-attempt the quiz until the time delay between attempts has passed. There should be a text notifying the user that he must wait until can re-attempt the quiz Actual: there is an option to attempt quiz which triggers an error. And, more generally, the button to start/continue a quiz attempt/preview should have an appropriate button lable at all times. That is, initially the button is Attempt quiz, but if you leave in the middle of a quiz attempt, and come back later, it will say Continue the last attempt, etc. Basically, the logic that was there before was right, and should not have been changed. The access message for the quiz is shown at the bottom, instead it should be shown after the tertiary nav. Update the heading text to "User overrides"/"Group overrides" in the user/group override pages and move it under the tertiary navigation. Move the Add category section (Question bank > Categories) to its own page and add a button (primary) "Add category" in the Question bank > Categories tertiary navigation which redirects to this page. Remove the cog icon from the quiz activity. When the quiz has a time limit, there needs to be some spacing between that and any other information such as the grading method. We should either display these paragraphs in separate lines as the original behavior or display them on the same line with some responsive spacing. Also, we should move them just below the tertiary navigation buttons. The Edit quiz button should be removed from the tertiary navigation and new item Questions (linking to this page) should be added to the secondary navigation instead. The Attempt quiz button should be primary for students. NOTE: I wasnt able to replicate this on the QA site, but it would be good to double check whether there are any existing scenarios where this button is displayed as secondary. The default visible items in the secondary navigation should be organized in the following order: Quiz, Settings, Questions, Results, Question bank. The secondary navigation item Overrides should be renamed to Settings overrides and placed in the secondary more menu by default. When a student starts an attempt in a quiz with a set time limit, a modal should be displayed notifying the student about the time limit restrictions as in 3.11. As a student, in the quiz summary page the Submit all and finish button should be primary The review quiz page should be max-width.
3.summary: Page tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Page activity. Identified issues: -The heading should be removed in the page activity (view page)- -The activity setting "Display page name" doesnt do anything in Boost which is a confusing. We should try to find a way to hide this option if secondary navigation is present.- Edit: As per Sanders comment| it was decided within the team to opt instead to remove the setting altogether.
4.summary: Scorm tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the SCORM activity. Identified issues: The Preview and Enter buttons and the content should be aligned to the left in the SCORM view page as presented in the design prototype When "Display course structure on entry page" is set to "yes" the content structure needs to be aligned correctly in the page. Align the Download dropdown button properly to the right (remove right margins) in the Reports page Add headings in every Reports page Update the redirect back flow in the Track details page to properly redirect to the previous page as presented in the design prototype Add headings in the pages under Attempts (Learning objects, Interaction) The Exit activity button should be moved from the header to the tertiary navigation in the scorm player, -renamed to Exit- and it should redirect back to the course homepage, Site homepage, or scorm view page depending on course format (single activity) and skipview settings within the scorm. The Enter button is not available when Disable preview mode is enabled. This seems to be a regression. The Display activity name is only applicable to classic at the moment. In boost the activity name is not displayed in the page content in the scorm player page. We should either consider hiding this setting when using boost or update the description and note that this setting does not affect boost related themes. - Edit: Remove the setting based on Remove the activity description and completion data from the SCORM player page. Remove the activity description and completion data from the pages under Attempts (Learning objects, Interactions) Remove the activity description and completion data from the Track details page. When the scorm attempt is in preview or review mode, the text that appears above the player stating that is in review or preview mode is a bit small/lost - it should be a lot more prominent as if in preview mode - no attempt data will be stored, and if in review mode it wont always update an existing score. Remove hard-coded styling in The exit button should not exist when viewing the scorm in a new window
5.summary: Update My Overview block styling
description: Given the supplied below we need to do the following: Remove the text from the dropdowns Update the styles & templates to better reflect the template in the list view i.e. adding the course image Make the summary display mode look like the list view with the exception it also contains the course description Edit: Updated figma design -
6.summary: Further improve login page
description: Im going to suggest that we further simplify the design of the login page as there are a number of UI features which belong in the previous century, and the design is still slightly too cluttered. In short, Im going to suggest that we should consider some more drastic changes: Remove the Footer entirely - especially when it is empty, but also consider hiding the performance info (collapse it perhaps) when stats are shown Make the login region wider. For some reason it appears narrower now than it does on the screenshots from when Angelia tested - considerably narrower. Remove the Cookies warning - we should only show information about this when a login fails because cookies are not enabled. Its a standard feature of browsers and very very few people disable cookies. Logins are too prevalent these days to consider disabling them entirely. Reword the "Forgotten your username or password?" link to simply "Forgot password?" Remove the "Remember username" checkbox entirely. This should be the default. I quite like what Chrome have done whereby they show information on how to open a private browsing window if you _do not_ want your login to be remembered. This is a much safer and more user-friendly approach. Make the username and password fields _taller_. At the moment theyre really short but they are the main focus of this page. We should make the area that users are expected to interact with more prominent. Equally we can increase the padding around them to make the area clearer. Move the Language selection to beneath the username and password fields. The Username field should be the first field in the tab order The "Username / email" placeholder text should read "Username or email" rather than having a slash (not very user friendly) Id like to suggest that we move the Cookie warning, to a new page which opens in a popup. It can also have the information on starting a private browsing session, and any other help we need to show in future (i.e. password recovery for admin, etc.). Comparing a number of other big login screens, none of them has the "Remember" or Cookie warnings. . Mockups Current: !Current without debug footer.png|thumbnail! Minimum width: !Current but wider (380px min).png|thumbnail! Simplified by removing Cookies prompt, and replacing "Remember username" with instructions for private browsing !With private browsing prompt.png|thumbnail!
7.summary: Update the secondary navigation for single activity course format
description: When using single activity format in a course, the secondary navigation only shows the navigation items related to the activity (module context) while the course related navigation items are missing on the page. Currently, the only way to access these course administration items is through the administration block. Therefore we need to update the secondary navigation and also include the course administration items as proposed on the following figma prototype The secondary navigation menu for a single activity course: should contain two items: Course and Activity both items should display dropdown menus on click the Course dropdown menu should contain the navigation items related to the course administration (Settings, Participants, Grades, Reports, ...) The Activity dropdown menu should contain the navigation items related to the activity administration (Link to the activity view page, Settings, Advanced grading, Permissions, ...) once a given navigation link has been accessed from the secondary navigation dropdowns or any other nested link within, the appropriate secondary navigation item should be still highlighted.
8.summary: Book tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Book activity. Identified issues: Print book and Print this chapter should be opened in a new window after clicking on the links. Highlight Book in the secondary navigation once the user is on the Add new chapter page (currently nothing is highlighted) In zero state (the book does not have any content yet), when students accesses the Book activity, they should be able to see the books description and a notification (info), stating that the book activity is empty.
9.summary: The Overrides secondary navigation item should be placed into the more menu by default
description: We should place the Overrides secondary navigation item in the more menu by default. For consistency reasons this change should be generally applied to every module (Assignment, Quiz, Lesson) that has this item in the secondary navigation. Additionally, the link attached to this node should redirect to the User overrides page by default instead of Group overrides Behat tests will have to be updated with default landing page change
10.summary: Arrange blocks between My courses & My dashboard
description: -Confirm and alter the block ordering within the dashboard & my courses pages currently defaults are being set within but we need UX to confirm exactly which blocks should appear where and when i.e. recently accessed courses added to the my courses page during installation and what blocks should be relocated during site upgrade.- -EDIT: Summary from UX discussion- -For a new site, dashboard should have:- -Timeline block (main region)- -Calendar block (main region)- -Recently accessed items (block drawer, this one needs confirming still)- -For an existing site, during upgrade, dashboard should retain all blocks the site has there currently, but the course overview block is no longer required since the courses are now displayed in the my courses page. So the course overview block should be removed from the dashboard.- -EDIT 04 Feb 2022- -To clarify:- -The dashboard should not have the recently accessed courses block- -The my courses page should be ordered by Last accessed by default- Revised requirements as part of this issue: New default blocks for the dashboard content area - timeline, calendar block Recently accessed items should be in the right area To account for mobile - the external blocks function should return a dummy course overview block until the app has been upgraded.
11.summary: Assignment tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Assignment activity. Identified issues: The View gradebook link should be removed from the secondary navigation Remove the Add submission, Edit submission (available after submitting) Remove submission (available after submitting) buttons which are duplicated and displayed at the bottom of the page. Add submission button should be primary Remove the activity completion section from the View all submissions page. Add heading (Submissions) in the View all submissions page Highlight the "Overrides" secondary navigation item in the Add user/group overrides pages Add heading in the Add user/group overrides pages Add a notification (info) in the user/group overrides pages when there are not overrides present instead of displaying a blank page. Remove the assignment name part from the heading in the Advanced grading page Remove the completion data and activity description in the Add submission page. Add title heading in the Add submission page. Update the breadcrumbs in the Add submission page and add an additional item "Add submission" to reflect the current location Move the separate/visible groups selector element just below the Grading summary heading in the forum view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the following code as it is no longer required
12.summary: Forum tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Forum activity. Identified issues: Display an info notification in the forum view page when there are no discussion topics added yet (zero state) In the Subscriptions secondary navigation page, add headings for both View subscribers ("Subscribers") and Manage subscribers ("Manage subscribers") pages. Display a notification in the View subscribers page when there are no subscribers yet in the forum (zero state) Do not display the Manage subscribers option in the tertiary navigation selector in Subscriptions when forced subscription mode is selected (this is the existing behavior in 3.11). Also, in this case the we do not need to display the tertiary navigation selector element at all as only one item will is available which relates to the current page. Remove the subscription mode selector element from the Manage subscribers page Remove the activity description from the Add new discussion topic (advanced) page. Add heading in the Add new discussion topic page (advanced) Update the breadcrumbs in the Add new discussion topic (advanced) page and add "Add discussion topic" to the breadcrumb trail When you access a given discussion topic, the settings dropdown menu should be changed to a dropdown button (right aligned) and should be vertically aligned with the rest of the selector elements (Display replies .. , Move discussion to...) Add heading in the Edit discussion topic page ("Edit discussion topic") Remove the activity description in the Edit discussion topic page Update the breadcrumbs in the Edit discussion topic page and add "Edit discussion topic" to the breadcrumb trail In the delete forum discussion page, highlight the Forum item in the secondary navigation menu In the delete forum discussion page, remove the activity description and activity completion section. Update the breadcrumbs in the Add reply (advanced) page and add "Add reply" to the breadcrumb trail In the split discussion page (has to be reply in a discussion topic), highlight the "Forum" item in the secondary navigation menu. In the split discussion page, remove the activity description and the completion section Update the breadcrumbs in the Split discussion page and add a link to the parent discussion to the breadcrumb trail Move the heading below the forum selector element in the Reports page and update the heading to "Forum summary report" If there are no results in the reports page, display an info notification instead of the heading. Found function forum_update_subscriptions_button stale, as its not used anymore after the recent changes made in . The forum subscription when changed by the user, it redirects back to the forum tab. Instead, it should be there on the subscription page. Remove the following code as it is no longer required
13.summary: Category page breadcrumbs and other navigation related issues
description: This is how the breadcrumb looks like on the current category page (/course/index.php?categoryid=X) !Screenshot 2021-11-25 at 11.07.25.png|width=600! There are multiple problems with this breadcrumb: The first element in it is "Course", which is a page that now competes directly with "My courses". The user would be confused if both pages are available. The course category page will now be mostly accessed from the "Site home" by default, so having the "Courses" page as the first element in this breadcrumb just adds to the confusion. After some thinking, we agreed on developing a mechanism that uses whichever option is selected in the setting defaulthomepage as the first element in this breadcrumb. Examples: If "Site" is selected... !Screenshot 2021-11-25 at 11.14.38.png|width=600! ...the breadcrumb will look like this: !Screenshot 2021-11-25 at 11.15.03.png|width=600! If "Dashboard" is selected... !Screenshot 2021-11-25 at 11.13.23.png|width=600! ...the breadcrumb will look like this: !Screenshot 2021-11-25 at 11.15.21.png|width=600! UPDATE: We have agreed to take the following actions: Every page in the course category context should have the base breadcrumb trail "Courses / \Category name". This means that in every course context page we will display breadcrumbs, due to the necessity to keep the link to the Courses page, which otherwise will be lost. On exception is when the defaulthomepage is changed to My courses, then the My courses node is prepended to the breadcumbs (ex. "My courses / Courses / \Category name") We should fix all the cases where the primary/secondary items are not properly highlighted We should update the header text wherever is necessary to properly reflect the current category context The figma prototype now covers in detail the required changes in the course category pages (
14.summary: Re-implement breadcrumbs in the course pages
description: We need to re-implement the breadcrumbs for the course pages that have been removed in Things to do: Revert the course breadcrumbs removal in Breadcrumb items (links) that exist in the primary and secondary navigation should be removed from the breadcrumb. ex. The breadcrumb "My courses > Course1 > Badges > Manage badges > Badge1" should be "Manage badges > Badge1" as the items (links) "My Courses", "C1" (course) and "Badges" are already highlighted and can be accessed through the primary or secondary navigation.
15.summary: Course and category management secondary and tertiary navigation
description: Steps to reproduce: Login as admin Go to "Site administration > Courses > Manage courses and categories". Create a new category with a super-long name (for instance, "Miscellaneous with a long long long long title to test if its truncated. Etiam massa orci, vehicula sed ligula sit amet, lobortis eleifend magna") Expected behaviour The secondary navigation is displayed. Current behaviour Only the "More" button of the secondary navigation appears. !secondarynavigationwithlongcategoryname.png|thumbnail! After having a discussion regarding this issue, it was decided that we need to modify the secondary and tertiary navigation in the course categories management page. These proposed improvements should also resolve this problem in the course category context. The following changes need to be done: In the course category context the following items should be present in the secondary navigation menu: Category - link to the course category view page (originally Category: \categoryname, the category name part needs to be removed) Settings - link to the edit category settings page (originally Edit this category, needs to be renamed to Settings), Permissions Cohorts Filters Restore courses Learning plan templates Competency frameworks Content bank. The header text in the course category pages should correspond to the category name (ex. Miscellaneous) In the category view page (Category) The Category secondary navigation item should be highlighted Add the following items in the tertiary navigation: Navigation selector element containing a list (links) of the available course categories (aligned to the left) Search courses input field (aligned to the left. right next to the category selector) More dropdown element (aligned to the right), containing the following items: New course (link to the Add a new course page) Manage courses (link to the Course and category management page related to the given category) Remove the Manage courses button from the page header Remove the Add a new course and Courses pending approval buttons (at the bottom of the page) In the Add a new course page The Category secondary navigation item should be highlighted In the Course and category management page (Note: the breadcrumbs displayed on the prototype should be ignored) The Category secondary navigation item should be highlighted Add the following items in the tertiary navigation: Navigation selector element containing (aligned to the left) the following items: Course categories and courses, Course categories and Courses. Search courses input field (next to the the view selector) When Courses view is selected, add another navigation selector element right next to the general navigation selector element which will contain the the available categories. Remove the Viewing dropdown Update the heading to Manage courses and categories In the settings cog dropdown menu for each category add View item (link to the category view page) In the Permissions page Add the following items in the tertiary navigation Navigation selector element containing (aligned to the left) the following items: Permissions, Check permissions and Assign roles. These requirements are presented on the following figma design prototype
16.summary: General tertiary navigation followup
description: This is a followup to address any general tertiary navigation issues in the activities. Identified issues: Move Locally assigned roles from the secondary navigation in activities into the tertiary navigation selector in the Permissions page (Secondary navigation More menu > Permissions). Add the navigation selector element into the Locally assigned roles page as well (Permissions, Check permissions, Locally assigned roles) Remove Logs and Competency breakdown from the secondary navigation in activities (These links can be accessed through Course > Reports) Remove Courses from the breadcrumbs shown in the activities. Update the heading text in the Enrolled users (Participans) page from Participants to Enrolled users.
17.summary: Tertiary navigation in course completion
description: Currently, a tab structure is used for navigation between the course completion pages. We need to replace the tabs with a navigation selector element and place it above the heading text.
18.summary: Document and inform the public about changes to theme plugins
description: Update to have a section that specifies what theme plugin developers have to do to get their plugins working. Please see for the specifics of what theme developers need to do. Please also include information about how to fix their problems, such as how to add back the settings cog, or a link to how to include the secondary navigation. Also please create a forum post pointing to the Moodle 4.0 developer update to help inform more people.
19.summary: Remove the secondary navigation menu in the calendar page
description: Secondary navigation menu is currently displayed on the calendar page with different items based on the capabilities of the authenticated user. !calendar_page.jpeg|thumbnail! Based on the 4.0 navigation requirements a secondary navigation menu should not be displayed on this page.
20.summary: Glossary tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Glossary activity. Identified issues: The description should be moved above the tertiary navigation in the Glossary view page. The activity description should not be displayed in the Add entry page The heading should be updated in the Add entry page The activity description should not be displayed in the Edit entry page Add heading in the Add/edit entry pages Add a back button (secondary) in the tertiary navigation in the view entry page which will redirect back to the glossary view page. Also, remove the existing anchor element from the page Add Cancel button (secondary) in the Import entries page which will redirect back to the glossary view page. Add back button (secondary) in the Export entries page Printer friendly version page should be opened in a new window
21.summary: Chat tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Chat activity. Identified issues: Remove the activity name part from the heading in the Past sessions page. Move the separate/visible groups selector element just below the tertiary navigation elements in the chat view page (The group mode needs to be set in the activity settings to be able to see the groups selector)
22.summary: Lesson tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Lesson activity. Identified issues: Add more spacing between Edit and Grade essays button (we need to define how much spacing should be added and be consistent) Edit button should be renamed to Edit lesson Move Edit page content from the page header to the tertiary navigation in the Lesson view page (secondary button) Add margins on the buttons in the user/group overrides pages Remove the activity description and completion data in the user/group overrides pages Add heading in the user/group overrides pages Add a notification (info) in the user/group overrides pages when there are not overrides present instead of displaying a blank page. Remove the link to grades in Overview and Detailed statistics pages in Reports Add heading in Overview and Detailed statistics pages in Reports just below the tertiary navigation Do not display the activity description in Overview and Detailed statistics pages in Reports Move the separate/visible groups selector element just below the heading in Overview and Detailed statistics pages in Reports (The group mode needs to be set in the activity settings to be able to see the groups selector)
23.summary: Survey tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Survey activity. Identified issues: Add padding at the bottom of the tertiary navigation elements in the Response reports page Move the Visible/Separate groups selector below the heading in the Response reports page (you will need to change the group mode setting to Visible groups or Separate groups in the activity to be able so see this selector) When nobody has yet completed the survey, display an info notification below the heading (or below the visible/separate groups selector if it exists) in the reponse reports pages
24.summary: Add headings to all reports displayed in the course context.
description: Some of the reports have headings and others dont. The goal is to have all of these reports looking consistent. Reports that need headings: Logs Live logs Activity report Course participation Activity completion
25.summary: Plugin set 4 of 4 tertiary navigation followup
description: During the PR and IR phase it was found that for the Forum activity: The "Search forum" in the activity redirects us to Course page and not to the secondary nav of the activity. This does deviate from the consistency. We need to decide how to move ahead with this behavior. We would also need help of UX team for the same. Additional issues found during integration: . -Forum- quote-Navigate to the subscriptions tab in the secondary nav:- -2 drop downs are noticed.- -Subscribers- -a) View subscribers- -b) Manage subscribers- -Shows the potential subscribers and Existing subscribers tables.- -This selection is saved in the session. Whenever the user comes back to the- -subscribers tab, the previous option is remembered.- -So for me selection is not saved - when I come back to Subscriptions tab I always have View subscribers selected even though I selected Manage subsribers last time- quote As mentioned by Sujith, this functionality is expected now. . -Quiz- -The dropdown selection does not get preserved when a validation error happens. To reproduce:- -As a teacher, go to the Question bank.- -Select Export- -Press "Export questions to file" without selecting a File format- -Validation fails- -Expected: The dropdown will show "Export" as selected.- -Actual: The dropdown selects the first item on the list (Questions) instead of the "Export" menu item.- -Students are presented with the option to re-attempt the quiz regardless of the enforced delay between attempts (Identified in , ).- -Login as a teacher, edit the settings for the quiz and set an enforced delay between 1st and 2nd attempts of 1 minute and an enforced delay between later attempts of 30 seconds.- -Login as a student and attempt the quiz.- -Go back to the Quiz.- -Expected: you should not have an option to re-attempt the quiz until the time delay between attempts has passed. There should be a text notifying the user that he must wait until can re-attempt the quiz- -Actual: there is an option to attempt quiz which triggers an error.- -The access message for the quiz is shown at the bottom, instead it should be shown after the tertiary nav.- We are moving all the Quiz related issues to Forum -Found function forum_update_subscriptions_button stale, as its not used anymore after the recent changes made in .- -The forum subscription when changed by the user, it redirects back to the forum tab. Instead, it should be there on the subscription page.- We are moving all Forum related issues to
26.summary: Improve the UI/UX of the recently accessed items block design for suitability in the Moodle 4.0 blocks drawer
description: When adding the recently accessed items block to the drawer it shows a horizontal scroll. This is not ideal. See options discussed here. () The ideal solution is to stack 3 items vertically and add a show more link to load more. !Recently accessed - Show more.png|thumbnail! We should estimate the work involved in this to determine if this is feasible before starting QA. If not we will stick with the current block layout for 4.0, add it to the blocks drawer as is, and address this issue for 4.1.
27.summary: Update the footer in the mobile view.
description: quoteWe agreed that the footer should always be displayed on small screens. However, I think we could improve its current design a little bit. (There are no prototypes for the footer on small screens my bad ) quote !Screenshot from 2022-02-07 15-05-46.png! Transparent background Dark text Same padding as the rest of the page content (see ) Powered by Moodle string aligned with the rest of the text (to the left) Original post|
28.summary: Keep management settings button on the same line in my courses (mobile view)
description: When in mobile view the settings button (three vertical dots) moves below the "My courses" title. Can we move this to be right aligned with the title in the mobile view?
29.summary: Word wrap long activity names in the context header.
description: When the activity name is long the activity type and name shift to below the activity icon. Can we instead please have these elements stay in the same spot, but have the text wrap in that area instead. Attached images show how it looks now and how it should look.
30.summary: Change the format of breadcrumbs in mobile view
description: We want to change a few things with how the breadcrumbs look in the mobile view. Remove the border around the breadcrumbs There is too much line-height ^Screenshot from 2022-02-07 16-02-46.png Currently: !Screen Shot 2022-02-09 at 5.09.47 pm.png|thumbnail! Should be: !Screenshot from 2022-02-07 16-02-46.png|thumbnail! quoteIt would be even better if we could truncate the breadcrumb items, so they always fill one row, like in the prototypes quote !Screenshot from 2022-02-07 16-02-55.png|thumbnail!
31.summary: Increase the strength of title text
description: There are several text sections around Moodle that should be bolder like the figma designs. The greeting message Block titles Course sections
32.summary: Decrease gap between course sections and the section description
description: The prototype has a gap of 12px between the course section title and the description. We currently have a bigger gap. Can we please bring this inline with the design? The design: !Screenshot from 2022-02-09 13-32-14.png|thumbnail! Current: !Screenshot from 2022-02-09 13-32-26.png|thumbnail!
33.summary: Document new activity iconography in component library
description: We should document the design details of the new icons in the component library, and in dev docs. Including rule-set used for BBB, which should be applied consistently: So heres what I propose as a rule-set to deciding background colours: We allow the actual icon to use the brand colours (so the darker blue in case of BBB). Ideally all plugin icons use the category assigned background colours| For BBB, which would fall in the communication (or maybe collaboration) category, this means green. If the assigned background colour would compromise the branding of the plugin too much, then the plugin will use the default background colour of grey
34.summary: Moodle 4 Admin pages should ALL have the admin search box
description: The admin search box should be always there also on: admin category pages specific admin settings pages Having the search option handy top right all the time will really speed up moving around. And it would add to the overall consistency of the Admins UX. (The idea first raised in the "Navigation issues in site administration pages" issue, added here following this suggestion| from sujith .)
35.summary: Remove the "Course categories" dropdown from the categories page
description: color:0e101aAlthough these category pages need a complete redesign from scratch, we could make them simpler by removing the "Course categories" selector, which only adds noise to the page since users have:color -color:0e101athe breadcrumb to navigate back to the parent category pagecolor- color:0e101athe browser "back" button to navigate back to the parent category pagecolor color:0e101athe current child categories printed on the page itself as collapsible elements, which are also linkscolor !Screenshot 2021-11-25 at 11.23.19.png|width=600!
36.summary: Mobile view nav bar header improvements
description: This is what it looks like now: !Screen Shot 2022-02-09 at 11.25.08 am.png|width=286,height=53,thumbnail! There are still a few areas that are different to the figma prototype. Can we please change the following: Change the hamburger: Remove the border Use the font awesome icon "fa-bars" Update the edit mode to remove the text in mobile view. It should look like this: !Screenshot from 2022-02-07 13-31-50.png|width=282,height=48,thumbnail! Initial report|
37.summary: Change padding / margins in the mobile view
description: Observed issues: (x) Right now, there s a lot of padding and margins in the containers. They push the content up to around 38px away from the screen borders (x) These different paddings and margins also affect the alignment of page elements (titles, content, etc.) Can we please make the border just a standard 8px. !Screenshot from 2022-02-07 13-51-47.png! Original post| Current page layouts: My courses: !Screenshot from 2022-02-09 11-59-21.png|thumbnail! Course page: !Screenshot from 2022-02-09 11-59-30.png|thumbnail! Activity: !Screenshot from 2022-02-09 11-59-40.png|thumbnail! Site administration: !Screenshot from 2022-02-09 11-59-50.png|thumbnail!
38.summary: Course section headings should have similar styling to form section headings.
description: The course section headers behave the same as form section headers and should have the same design.
39.summary: Style main container scrollbar to match the style of the drawers scrollbar
description: Main container still uses native browser styling for scrollbar. It should match the look and feel of the drawer scrollbars
40.summary: Change the first tab label to General from Site administration
description: The first tab in the site administration is to change from General to Site administration (screenshot included).
41.summary: Section expand/collapse icons not centred in circles
description: These are irritatingly not in the middle. See screenshots: !expanded.png|thumbnail! !collapsed.png|thumbnail!
42.summary: Increase the font size of the description in all activities.
description: We altered the look of the course completion details and summary to match the main course page, but we would like the summary in the activity page to be the same as it previously was, and not smaller as it currently is.
43.summary: Show the course index on all pages within a course
description: Currently the course index is available on the course page and when within activities. Some user feedback has been received suggesting the course index should also be available when on the other course pages such as settings, participants, grades, etc. Lets review. 15/12/2021 update I attached a screen recording to this issue. When switching back and forth between the course page and other pages (settings, etc) we are jumping between showing the course index (when open in the course page) and not (elsewhere). This feels a bit disorienting and also causes the secondary nav to shift. I tend to agree that keeping it open on the other pages (when open on the course page) is preferable. 6/01/2022 update Agreed to go ahead and introduce the course index on all other course pages
44.summary: Move adminpresets to admin/presets
description: dobedobedoh and brendanheywood have mentioned that: "I wish /adminpresets/ was instead /admin/presets/ so that CLI tab autocomplete wasnt broken trying to run CLI scripts". When I worked on , I didnt realise it was possible to create this component inside admin/presets (so thanks mudrd8mz for pointing that admin/roles is a similar case). This issue is about moving the content in the adminpresets folder into admin/presets for consistency and also to make happy our beloved developers :)
45.summary: Provide option to not use the Dashboard
description: In Moodle 4.0, the Course overview block is being moved from the Dashboard to My courses. This will leave only the calendar and timeline blocks on the Dashboard. For sites which dont use the calendar or timeline blocks, such as sites offering self-paced courses, it would be good to provide the option to disable the Dashboard. -Adrian edit Weve had a few developers ask about being able to customise the primary header. Can we please investigate expanding this issue to cover adding and removing any combination of the primary navigation items?-
46.summary: Manage blocks page should remind about unneeded blocks
description: The admin page Manage blocks at /admin/blocks.php should display a reminder about the /admin/search.php?query=unaddable settings and perhaps provide a link to this search result page, so the admin can check if the enabled blocks can actually be added to courses, and so s/he can sync both types of settings as needed.
47.summary: Starter site admin preset improvements
description: Lets make some improvements to the Starter site admin preset based on community feedback in the discussion Site admin presets in Moodle 4.0| We also need to consider new features and improvements in 4.0, such as the BigBlueButton activity, and decide on appropriate settings for them in the Starter preset. ---- This is the list of settings/plugins to be changed (after discussing and agreeing on them): BLOCKS The following blocks will be disabled by default in the Starter preset: Online users (block_online_users). In Moodle 4.0 it has been removed from the Dashboard. Recently accessed courses (block_recentlyaccessedcourses) and Starred courses (block_starredcourses). The My Courses page lists recently accessed courses, so there is no point in adding the block to the Dashboard. There is also no point in adding the Starred courses block to the Dashboard because you can only star courses on the My courses page. QUESTION TYPES Essay and Description question types will be re-enabled in the Starter preset (as suggested by timhunt in an issue). GUEST ACCESS As recommended by thornedu in the forum| the following settings related to Guest access will be disabled for the Starter preset: Plugins / Enrolments / Manage enrol plugins > "Disable Guest access" Plugins / Authentication / Manage authentication > Guest login button = Hide. ACTIVITY CHOOSER To reduce the information displayed in the activity chooser: Activity chooser tabs (activitychoosertabmode) will be set to "Starred, All, Recommended" (no Activities or Resources tabs).
48.summary: Improve the loading time of the course index when the user is not in the course page
description: Since the course index appears in all pages related to the course, not only in activities and the course view. This implies that in most pages the course index content can be fully cached to speed up the page loading. All those new pages with the course index cannot alter the course structure itself so they can use the previously loaded version of the course index. This does not happen with the course index and activity pages as they can, for example, alter the activity completion.
49.summary: Improve links to services and support
description: To make it easier for our users to get additional assistance we want to improve the links to Moodle Service providers -and ensure the site support email address is always configured-. For this purpose we want to introduce the following changes: 1. Add a link in the new ? pop-up that takes users to a new to be created page on moodle.com. This page will present the user with various options to get further support for their Moodle site. 2. Add a notification message in the admin notification screen after install / upgrade that points to the same page defined above in 1. -3. Make the site support email address mandatory (Administration > Server > Support contact) and also make this available in the new ? pop-up.- Suggested page URL to point to: moodle.com/help . Admin notification pages !final-screenshot.jpg|width=615,height=354! As illustrated in the image above, lets add a new notification above the existing "donation" one, with the Moodle Partner logo and the following message: "Support and services Need support for your Moodle site? Find a Moodle Certified Service Provider near you at moodle.com/help" The Moodle Partner logo image is here: ^moodle-partners-logo.zip . Help (?) pop up changes This is the design that I came (and tested briefly) for the help pop-up: !footer.png|width=325,height=317! Document and guides Link: same as current "Moodle Docs for this page" Font-awesome icon: fa-book Services and support Link: new services page (this issue) Font-awesome icon: fa-life-ring Note: the "services and support" footer link should only be visible for admins.
50.summary: Follow up: using "chevrons" instead of "carets" would give Moodle a more modern feel
description: In the prototypes we changed the "caret" icon found in menus and dropdowns to a "chevron" one. So these elements: !Screenshot 2021-10-28 at 14.56.56.png|width=420,height=133! !Screenshot 2021-10-28 at 14.57.00.png|width=211,height=57! Would look like this: !Screenshot 2021-10-28 at 14.58.01.png|width=400,height=119! !Screenshot 2021-10-28 at 14.58.26.png|width=237,height=46! The problem is that, right now, the "caret" icon is printed using sorely CSS in an ::after pseudo-element. To print a "chevron" in there we need to make deeper changes in the code than we first thought.
51.summary: Update tertiary navigation in the database module
description: Some updates to the tertiary navigation in the database module are required in order to improve the accessibility in these pages. In the "Fields" tab, change the naming of the Create a new field selector option to "Manage fields". On the same page, update the default option in the field type selector from Choose... to "Create a new field" On the same page, add a "Manage fields" heading !screenshot.jpeg|thumbnail!
52.summary: Add standard method to retrieve all navigation nodes for a requested section
description: This is specific for the secondary navigation views. The standard navigation has a few nodes (user, reports, badges, and question bank) that are categories. There are a couple of callbacks that extend the navigation tree and this allows a lot of freedom to add an update the tree anywhere. In this case we are looking at the potential of third party plugins adding navigation nodes into the above mentioned categories. On those pages we need to retrieve the navigation tree for that category and display the inserted third party categories and child nodes. As we have to do the same thing in all of these places we should have a centralised function.
53.summary: Missing a divider between the "My courses" page header and content
description: This is how it looks right now: !Screenshot 2021-11-04 at 10.20.15.png|width=658,height=249! This is how it looks in the prototype: !Screenshot 2021-11-04 at 10.20.22.png|width=660,height=257!
54.summary: Display a title in the dashboard page
description: We need to step back on our decision to remove the greeting message from the dashboard after the user leaves the page. We should always display a page title, for accessibility reasons and also to make the experience more solid when navigating through the primary navigation. My initial idea was to always keep the greeting message in the dashboard even when the user browses away from the page and come back later. Im aware that this option was already discussed and denied in the past, so I suggest we change the page title from the greeting to "Dashboard" when the user comes back to this page. So, when the user logs in the greeting would be the dashboard title (as it is right now): !Screenshot 2021-11-18 at 14.46.15.png|width=460! Then, if the user goes away from the dashboard and comes later (in the same session), the title of the page would be "Dashboard": !Screenshot 2021-11-18 at 14.46.28.png|width=460!
55.summary: Make rounded corners more rounded by default
description: Change the default boost theme border-radius from .25rem to .5rem. Comparison: !rc-1.jpg|width=600! !rc-2.jpg|width=600! (In the images above: Left: .25rem; Right: .5rem) Just as an example, I achieved the results above by adding the following SCSS to the "Raw initial SCSS" theme configuration field. $border-radius: .5rem !default;
56.summary: Database tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Database activity. Identified issues: Move the separate/visible groups selector element just below the tertiary navigation in the database view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the completion data and activity description from every page except the database view page. Pages that should not display the description and completion: Add new entry page Edit entry page Export entries page Delete entry page Manage fields page Add field page Edit field page Delete field page Import a preset page Use a preset page Templates pages Presets pages Add headings in the Templates pages Set the List template to be the default template to land on in Templates Add template should be changed to Add entry template in Templates
57.summary: Label secondary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Label resource. Identified issues: Rename the Label secondary navigation item to Course. The label resource does not have a dedicated view page and clicking on this secondary nav item takes the user to the course page.
58.summary: Choice tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Choice activity. Identified issues: Move the separate/visible groups selector element just below the Responses heading in the responses page and the view page (The group mode needs to be set in the activity settings to be able to see the groups selector) Remove the duplicated Responses node from the breadcrumbs in the Responses page
59.summary: Workshop tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Workshop activity. Identified issues: Add some spacing at the bottom of the tertiary navigation selector element in the Submissions allocation page. Add headings below the tertiary navigation selector element in the Submission allocation pages (Manual allocation, Random allocation, Scheduled allocation)
60.summary: Feedback tertiary navigation followup
description: This is a followup to address any issues or any inconsistencies with the design prototype in the Feedback activity. Identified issues: Add heading ("Templates") in the templates page Add heading ("Analysis") in the analysis page below the Export to Excel button Move the separate/visible groups selector element just below the Analysis heading in the analysis page (The group mode needs to be set in the activity settings to be able to see the groups selector) Add Show responses heading below the tertiary navigation selector in the show responses page
61.summary: Update date in security.txt for 4.0 release to factor in release delay
description: Given the large move of release dates for 4.0 (and 4.1), the security.txt expiry date as added in no longer seems sufficient, since it would only be approximately 2 months. The minors on earlier versions can be updated in May minors, but ideally 4.0 will be released with a security.txt that is valid until around the the expected release date of 4.1 (+3 weeks as standard).
62.summary: Enable MoodleNet integration by default
description: Now that we have MoodleNet in a good beta version, we are looking at switching tool_moodlenet|enablemoodlenet on by default. We were originally looking at doing this earlier, but then MoodleNet ran into some problems and so we switch the default to off. -This is only for new installations. No need for an upgrade step here.- EDIT (SB): 18 Jan 2022 Discussed with the product team; agreed yes we want to enable by default. Need to: Enable the setting Enable the footer Default values for MoodleNet settings need to be updated Testing should involve end to end importing of MoodleNet content into LMS, both when logged into MoodleNet and when not logged in. EDIT (SB) 19 Jan 2022 Enabling by default is for both new installs and upgrades. For sites that are upgrading we should inform the admin by sending an admin notification. Something along the lines of: quoteIn Moodle 4.0 the MoodleNet integration has been enabled. Users with the ability to edit courses will now see a link to MoodleNet in the activity chooser. Clicking on this link will take them to MoodleNet where they can select and import content into their Moodle course. Please visit for MoodleNet| for more information. You can change the MoodleNet settings or disable this feature. quote WHERE MoodleNet settings should link to disable this feature should link to
63.summary: Stronger highlighting of the selected activity is required.
description: This is for the UX team to review if it is necessary to increase the darkness of the highlighted activity in the course index. suggests that the current contrast is not enough. Edit: agreed to go ahead, see Rafas comment below
64.summary: Badge pages polish
description: A couple of things to bring the badge pages inline with the figma design| "Add a new badge" button should be btn-primary When there is no badges, the notice should have a blue background instead of a red one. When there are no badges the "manage badges" buttons should not be displayed.
65.summary: The active activity is not always displayed in the course index.
description: I think most of the concerns in have been addressed, but there are situations where the topic will be collapsed and entering the activity will not force open the topic to show the current activity that we are in. Can we please review this situation and make sure that we are always aware (in the course index) of our location?
66.summary: Review padding at the top of the page
description: The padding between the primary navigation and the context header is substantial. It tends to stand out more when there is no background set and there is nothing but white space. Lets have a discussion about whether we should reduce the space between the primary navigation and the context header.
67.summary: Display some help text with the new subscription mode change action bar
description: See following forum subscription page: !Screenshot_2022-01-17 Subscribers.png|width=800! The tertiary navigation lacks any context as to its purpose, but is consistent with elsewhere and should be resolved by The select element on the far right of the page also lacks context, but acts as a form submission when changed. Apart from the user no longer being asked for confirmation before submitting the form (), they are given no context about what it actually is and/or refers to - a help icon would be good here Pinging tsala for her thoughts
68.summary: Provide a contact form which sends to the site support email and replace mailto link in footer
description: This is a follow up from There is some concern that the public email address would be misused. As a result it is better to hide this for not logged in users. -The proposal for this issue is to:- -If the supportpage is set, show the link to the support page- -If not, show a link to a generic contact form which will send an email to the support email address- The updated footer support link logic for this issue is: If the supportpage is set, show the link to the support page (which will open in a new window). If not, and SMTP is configured on the Moodle site, link to a generic contact form within Moodle, which will send an email to the support email address. If not, and SMTP is _not_ configured, still direct to the internal page, but display a message that it cant be sent from that page. If the user is logged in, also show them a mailto link to the support email address. If not logged in (or a guest user), then omit the support email address. Uli has provided UX mockups for both the email received by support, as well as the version of the page described in point 3 above: Email mockup: !support-email-mockup.png|thumbnail! When internal form hidden (SMTP not configured): !support-form-no-smtp-config-mockup.png|thumbnail! (Note some of the suggested mockup strings have been used, but were not all designed to be final strings, so some have been refined/changed since. The icon was also changed to an appropriate fontawesome one, since the cone doesnt exist in our icons or FA.)
69.summary: Change UI for Add activity, Add block, Add topic and similar elements
description: Based on rafaellechugos comment on , theres a new design to implement for Add activity or resources, Add block, Add topic and every other similar element. The border of those elements should be solid instead of dashed. A) !-A.png|width=842,height=96! B) !-B.png|width=523,height=830! C) !-C.png|width=837,height=482! D) !-D.png|width=807,height=283! E) !-E.png|width=810,height=470! Also, there were some design specifications from that were not implemented e.g the "plus" icon should be inside a box also with rounded corners. EDIT: Also address the issue raised in the linked duplicate issue.
70.summary: Document and list all new behat steps.
description: Please update with a list of all new behat steps that have been introduced in 4.0. We currently give a couple of examples, but really we should just list everything that has been changed. Please format this in a way that is useful for a plugin developer. The current Behat section could do with an overhaul. Suggestions from Jonathan Champ quoteThese mostly made sense, but it would be nice to have it spelled out a bit more. It says "modname activity" and Im fairly sure that for the "quiz" activity module, it would be "quiz activity", but Im not sure if resource modules are different or not. I dont know if something special needs to happen for blocks. At one point, it says that two examples "work fine" and its not clear if the author is bolding the word "fine" to imply a negative emotion or to imply a technical compromise or if it has any additional meaning at all. When I say something is "fine", I mean that it meets the definition, but only barely. Example: "What do you think of Red Lobster? Its fine." For reference, Red Lobster is a chain restaurant in the United States that does indeed sell food, but I would not describe it as either good or bad. It simply is. quote
71.summary: Dialog should have the action button on the right
description: As commented by dougiamas in : quote1) OS X, Windows and Ubuntu ALL put the "Cancel" button on the left and the action button on the right. 2) This makes sense to me because dialogs are like a step in a process/story, and we are used to moving left to right in those situations (is probably reversed for RTL speakers). "Cancel" is like going BACK while "Save" or Add" in this case is like going FORWARD. quote Also jverdaguer highlighted the inconsistency between Moodle and the Moodle app, which has the action button on the right. !dialogue_boxes.png|thumbnail! Thus, lets change the order of the dialog buttons to have the action button on the right.
72.summary: current class no longer applied to the section when it is the highlighted section
description: Ref: When highlighting a section, the current class is no longer applied to the section as it was before in M3.11-. Suggested fix is to add $data->iscurrent = true; to export_for_template() of /course/format/classes/output/local/content/section.php when ($format->is_section_current($thissection)) is true. Or change /course/format/templates/local/content/section.mustache to use highlighted instead of iscurrent on the section li tag.
73.summary: Default dashboard page showing wrong header and secondary nav
description: Problem: The Default dashboard page is showing the site admin header and the site admin secondary nav which get in the way of having a real view of the dashboard page during customization. Also the active top nav indicates Site admin instead of Dashboard. The change to 4.0 from 3.11 made it more confusing. !comparison between 311 and 40.png|thumbnail! Recommendations: Change header to Default dashboard page Remove secondary nav Make Dashboard active on the top nav
74.summary: Bump NodeJS version, dependencies, and update JS build process, drop IE support
description: panel:title=Policy: Keeping us on top of nodejs/npm LTS versions (including jumps to next LTS)|borderStyle=dashed|borderColor=ccc|titleBGColor=F7D6C1|bgColor=FFFFCE Since September 2018 (): This policy will be applied to ALL supported branches, normal and security-only. This policy wont update any tool per se, unless strictly needed by nodejs/npm own dependencies/changes. It wont include npm audit changes either. Those are handled apart. So, normally, only changes to .nvmrc and package.json will happen. That will be achieved by: update .nvmrc to the new version. run nvm install && nvm alias default node && nvm use to install, set it as new default and use it for the next steps. update package.json and set engines to the new restriction (>= new version and < next major). When needed to bump components or run some audit, a new issue, similar to this, will be created and these steps performed in order to get a renewed npm-shrinkwrap.json file: remove node_modules & npm-shrinkwrap.json npm cache clear --force npm install npm shrinkwrap In any case, simple update or complete components bump, run grunt and verify that all the generated css/js/map stuff remains the same. If there are differences in the generation... it will need to be analysed and decided if: accepted (so everything, shrinkwrap and generated css/js/map) lands or not accepted (and only change .nvmrc and package.json) instead). The resulting branches will be sent to github (or similar), making a peer-review request here so both travis and cibot will verify that all them pass ok. Changes will be normally integrated and the NodeJSVersion template| and NodeJSExactVersion| templates will be updated with latest information in the Docs. TODO (): A job @ CI servers will be, daily, using latest lts/current version to detect if there are npm-shrinkwrap.json changes. It will fail when that happens and inform integrators. Jumps to lts/next will be detected manually,. panel Im raising this issue because of some problems with our current build identified in . Essentially, our current minification options include an option called mangle (on by default) which in some situations can cause broken JS to be generated. We dont know if/when this may crop up, and the relevant project seems to be abandoned. Unfortunately disabling the mangle option causes minified files to be changed, which is something that we try to avoid because it messes with third-party developers and their build processes. Given the combination of these things I think that we need to: update the Grunt JS config to set the mangle option to false update our NodeJS version to the latest LTS (16.14.0) update our package versions This has the following effects: updates all built JavaScript (YUI and AMD) replace the current babel-minify plugin with a supported minification system (terser) This combination fixes the issue blocking . I believe we should apply this to master, and stables so that all versions of Moodle have the same NodeJS version support as per policy. For master I think we should consider dropping support for IE and adjusting our browser compatibility list accordingly to: remove IE update the browser usage restriction to cover the top 0.3 instead of 0.25 (this removes support for Android 4.4 released in October 2013) This combinations of things will: drop use of many of the legacy polyfills for things like for...of, and async which makes debugging async functions much _much_ easier This was agreed in back in August 2020, and was intended to happen in the Moodle 3.10 release. This was not done at the time (due to time constraints). Because of this change there _will_ be build output changes in third-party plugins. We do try to avoid this wherever possible but sometimes it is unavoidable. We technically _can_ get away with _not_ modifying minified files, but the older our babel packages get the harder it becomes to upgrade in the future. We will be supporting Moodle 3.9 until May 2023, and it makes more sense to make this change to Moodle 3.10 so that all versions from 3.9 to 3.11 have the same build process, and Moodle 4.0 has the same process but with IE support dropped.
75.summary: Improve flexibility of site support form and consistency of site support info provided in Moodle
description: Remove SMTP limitation The current implementation of the site support form checks if outbound SMTP is configured in Moodle, and if not will not provide the form (instead showing a message and linking logged in users to the support email address). Since sites may be using another external MTA, we should allow sending via the form regardless, and only display the aforementioned message if the system registers that it has failed (if it succeeds with the request, but the mail fails to send from the MTA, that is out of the view of Moodle so out of scope to be handled). We should also then display the form again below the message, so that if its a temporary outage they can try again, and worst case still have their message available to copy out and email through manually. Remove support email where it is exposed elsewhere In we removed access to the support email address from the new "footer" link, but there are some existing places in Moodle where it is also available, which should act consistently and link to the support form (and also not expose the now compulsory support email address to unauthenticated users). An example of this is /error/index.php, but we need to check for any other leaks.
76.summary: Allow secondary navigation to be shown for behat in quiz
description: We have a comment in . Kindly remove this comment and the following if condition for BEHAT_SITE_RUNNING. You may also require to adjust the behat tests accordingly.
77.summary: Improve access to a users custom reports
description: Users can can access their list of reports if $CFG->enablecustomreports is set (it is by default, ) and they have any of the following capabilities: moodle/reportbuilder:editall, moodle/reportbuilder:edit, moodle/reportbuilder:view, Relevant method: However, without moodle/site:configview there is no obvious way for them to navigate to their list of reports (note they can still access it if directly linked to the page) In Workplace we use a custom launcher: !Screenshot_2022-02-28 Dashboard.png! LMS should have a similar alternative (e.g. something on the user menu) that doesnt rely on granting access to view the admin tree to all users From discussion with emiliolozano, sanderbangma & rafaellechugo (please update issue as you see fit, and/or to add clarification :))
78.summary: Allow full customisation of the primary navigation
description: A large number of developers have asked about the possibility of customising the primary navigation. We had an investigation into doing that in , but a complete solution like what is being implemented for the dashboard, is not possible for all primary navigation items in the time remaining for the 4.0 release. This issue is to provide a way to show and hide primary navigation nodes (tabs) in a less strict fashion. For this adding variables to theme/config.php are for developer alterations and the same internal checks are not required from core. The primary navigation is only visible in the boost theme, and making changes in core related to theme specifics is not allowed. So we have to work with that restriction. By adding a config to the boost theme, the specific layout pages can retrieve that information and then alter the primary class accordingly. We could help out here by providing a method to help.
79.summary: Timeline block - search for multilang
description: Hi! (I was testing the Timeline block on the app, but this is LMS) If you have an activity that is shown on the Timeline block titled "One option EnglishEspa ol", you will be able to search it by "One option" but NOT by "One option English" Thanks! PD I am aware this is an edge case
80.summary: Expand course section icons are not rendered properly in RTL
description: In LTR, expand icons are rendered as ">". In RTL, theyre also rendered the same (">") instead of "<". !screenshot-1.png|thumbnail!
81.summary: Duplicated link name "Home" when viewing a badge
description: When I view a badge as a student, I see 2 links/buttons above the badge and they both have the same name: Home. In my site, one of them sends me to Site Home (course/view.php?id=1) and the other one sends me to My courses (root of the site). I think its confusing to have 2 buttons with the same name if they send me to different places. As an admin I can see: Home, Participants, Content Bank, Home, Site administration
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Users should be able to sign up, log in, and preview content
description: Users should be able to sign up, log in, and preview content.
| Solvable | 1.summary: Add metadata & preview image for nicer social media sharing & SEO
description: i.e. make shared links look nice in Telegram/Twitter/Facebook/etc
2.summary: Research identity/authentication solutions
description: Some Goals Identity originates on users home instance (where their personal/private data is stored) MoodleNet HQ API has an index of all users and their home instances Users can inform HQ API of an additional account they have on another instance Users can inform HQ API that theyve moved to an account on another instance Users can interact directly with the HQ API through a user+instance token Users can link sign into MoodleNet with their Moodle Core account using oAuth Users can link sign into Moodle Core with their MoodleNet account using oAuth ---- IMPORTANT: more here
3.summary: Create separate sign-up page
description: People are getting confused about logging-in versus signing-up. Perhaps we can change: Sign in to Login? Make the Sign up link separate / more prominent Have a separate URL for Sign up (you cant link to the modal)
4.summary: UX Design - Sign Up Page
description: Create a Sign Up page according to the UX prototype -Create modules -Style them -Implement them on Storybook
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Users should be able to sign up, log in, and preview content
description: Users should be able to sign up, log in, and preview content.
### Response:
1.summary: Add metadata & preview image for nicer social media sharing & SEO
description: i.e. make shared links look nice in Telegram/Twitter/Facebook/etc
2.summary: Research identity/authentication solutions
description: Some Goals Identity originates on users home instance (where their personal/private data is stored) MoodleNet HQ API has an index of all users and their home instances Users can inform HQ API of an additional account they have on another instance Users can inform HQ API that theyve moved to an account on another instance Users can interact directly with the HQ API through a user+instance token Users can link sign into MoodleNet with their Moodle Core account using oAuth Users can link sign into Moodle Core with their MoodleNet account using oAuth ---- IMPORTANT: more here
3.summary: Create separate sign-up page
description: People are getting confused about logging-in versus signing-up. Perhaps we can change: Sign in to Login? Make the Sign up link separate / more prominent Have a separate URL for Sign up (you cant link to the modal)
4.summary: UX Design - Sign Up Page
description: Create a Sign Up page according to the UX prototype -Create modules -Style them -Implement them on Storybook
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Server clustering improvements
description: There are a number of changes that will assist those using clustered server environments. They will improve performance of the environment. The identified items are listed in this EPIC.
| Solvable | 1.summary: Support for split memcache/memcached stores
description: In load balanced environments, it can be of significant benefit to have memcached servers running on each front end server, as it removes network time for all access of the cache. Most caches must (or at least really should be) shared, and running caches that point to localhost (ie on each front end) can/will get out of sync, as there is no modification or invalidation between machines. Some caches have a very low set/hit ratio, like Lang Strings and DB Schema. With that in mind, I propose a two cache stores (memcachecluster and memcachedcluster) that fetch from one set of servers (typically localhost) and updates a different set of servers (typically the full hostname of each front end). Because of low set/hit ratio, the time lost in updating multiple servers is more than made up by the gain of fetching locally.
2.summary: New session infrastructure - file, database and memcached storage
description: The OU finds memcache for session handling to be important for performance. Here is our code to be commented on, and hopefully, if good enough, added to core. Edit: This ticket has been highjacked for memcached session handler instead of memcache.
3.summary: new $CFG->localcachedir
description: The difference from normal $CFG->cachedir is that the directory does not have to be shared by all cluster nodes, the files stored in $CFG->localcachedir MUST NOT change! Default location is "$CFG->dataroot/localcache". All files there must use unique revision numbers or hashes because the cached data can not be invalidated by any means - it will support only adding of new files, but no file deletes or overrides. The $CFG->localcachedir will be growing over time, all local cache files will be deleted during purge_all_caches() (usually upgrade). When using hashes please make sure the number of files in one directory is kept to some reasonable number because some filesystems might have problems with large number of files in one directory. Design requirements: Everything must be automatic without extra administrative overhead. purge_all_caches() on any node triggers local cache purging on all other nodes before adding any new files there. Performance on standalone servers must not be worse. Usage restrictions: No file deletes No file modifications No file overwriting Soft limit on maximum number of files in one directory (few thousands) Benefits: clustered servers may use local tempfs no opcache cache invalidation problems if php files included from localcachedir (because the files must not change) Converted areas: lib/javascript.php theme/
4.summary: cleanup and improved caching in lib/javascript.php
description: Goals: solve caching issues when $CFG->cachejs = 0 (at present we just send links to static JS files which confuses developers because they need to invalidate browser caches manually) improve coding style preparation for introduction of $CFG->localcachedir
5.summary: cleanup, fix and improve theme resource caching
description: Goals: fix race conditions purge_all_caches() in theme designer mode standardise cache directory structure - revision right after type of resource fix potential race conditions when serving css improve performance by not doing full lib/setup.php init if only core_component used improve coding style prepare fro $CFG->localcachedir To get the best performance it is recommended to use transparent proxy such as Cloudflare - these proxies eliminate the repeated execution of PHP scripts, it is possible because data does not change and we allow infinite caching. Note: MUC is not suitable for theme caching because the performance is critical here - loading of all core libs and MUC together with DB init would be both slow and expensive, theme caching works with config.php only and only if really necessary the setup.php continues loading all libraries and inits DB.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Server clustering improvements
description: There are a number of changes that will assist those using clustered server environments. They will improve performance of the environment. The identified items are listed in this EPIC.
### Response:
1.summary: Support for split memcache/memcached stores
description: In load balanced environments, it can be of significant benefit to have memcached servers running on each front end server, as it removes network time for all access of the cache. Most caches must (or at least really should be) shared, and running caches that point to localhost (ie on each front end) can/will get out of sync, as there is no modification or invalidation between machines. Some caches have a very low set/hit ratio, like Lang Strings and DB Schema. With that in mind, I propose a two cache stores (memcachecluster and memcachedcluster) that fetch from one set of servers (typically localhost) and updates a different set of servers (typically the full hostname of each front end). Because of low set/hit ratio, the time lost in updating multiple servers is more than made up by the gain of fetching locally.
2.summary: New session infrastructure - file, database and memcached storage
description: The OU finds memcache for session handling to be important for performance. Here is our code to be commented on, and hopefully, if good enough, added to core. Edit: This ticket has been highjacked for memcached session handler instead of memcache.
3.summary: new $CFG->localcachedir
description: The difference from normal $CFG->cachedir is that the directory does not have to be shared by all cluster nodes, the files stored in $CFG->localcachedir MUST NOT change! Default location is "$CFG->dataroot/localcache". All files there must use unique revision numbers or hashes because the cached data can not be invalidated by any means - it will support only adding of new files, but no file deletes or overrides. The $CFG->localcachedir will be growing over time, all local cache files will be deleted during purge_all_caches() (usually upgrade). When using hashes please make sure the number of files in one directory is kept to some reasonable number because some filesystems might have problems with large number of files in one directory. Design requirements: Everything must be automatic without extra administrative overhead. purge_all_caches() on any node triggers local cache purging on all other nodes before adding any new files there. Performance on standalone servers must not be worse. Usage restrictions: No file deletes No file modifications No file overwriting Soft limit on maximum number of files in one directory (few thousands) Benefits: clustered servers may use local tempfs no opcache cache invalidation problems if php files included from localcachedir (because the files must not change) Converted areas: lib/javascript.php theme/
4.summary: cleanup and improved caching in lib/javascript.php
description: Goals: solve caching issues when $CFG->cachejs = 0 (at present we just send links to static JS files which confuses developers because they need to invalidate browser caches manually) improve coding style preparation for introduction of $CFG->localcachedir
5.summary: cleanup, fix and improve theme resource caching
description: Goals: fix race conditions purge_all_caches() in theme designer mode standardise cache directory structure - revision right after type of resource fix potential race conditions when serving css improve performance by not doing full lib/setup.php init if only core_component used improve coding style prepare fro $CFG->localcachedir To get the best performance it is recommended to use transparent proxy such as Cloudflare - these proxies eliminate the repeated execution of PHP scripts, it is possible because data does not change and we allow infinite caching. Note: MUC is not suitable for theme caching because the performance is critical here - loading of all core libs and MUC together with DB init would be both slow and expensive, theme caching works with config.php only and only if really necessary the setup.php continues loading all libraries and inits DB.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Prepare Moodle for PHP 8.1
description: !taken_on_near_completion.png! _(image taken near completion, now php81 is being tested everywhere, GHA, CIs... so no need for those custom tests and branches anymore)_ The, hopefully small, epic to turn Moodle ready for PHP 8.1. When: Being cristal clear (aka transparent), the ideal target release for this is Moodle 4.1.0 (aka, supported since the very beginning of the branch), but be warned that full support may arrive later in any Moodle 4.1.x minor release in the branch, depending of a number of factors (extensions availability and bugs, 3rd part libraries, last minute surprises...). Some initial links: - Main changes explained: and - Changes detailed: - Accepted RFCs: Some basic requirements for this: (/) get unit and acceptance tests passing against all databases (may imply the need of upgrading phpunit/behat...). (/) phpunit upgrade: (just small updates to 9.5.x) (/) behat upgrade: (just small updates to 3.11.x, and moving to upstream mink-extension). (/) check all the changes details| have been reviewed and fixed (attached file ^php81-progress.rtf ). Note that, until release, this file is considered WIP and subject to changes! (/) ensure older versions of Moodle dont work with PHP 8.1 () (/) get moodle-php-apache| docker images working with the new php version (/) verify that php-parallel-lint/php-parallel-lint| and others pass for all php versions () (/) search in the tracker for any issue created about "php 8.1" or "php81". Add them to this epic after analysing them. (/) FINAL: verify that the apache logs are clean of PHP 8.1 notices/warnings/errors () (/) FINAL: verify that all the issues found by the dev version of PHPCompatibility are fixed or false positives (). (/) FINAL: When CIs are passing consistently, put all the MySQL (W) jobs in the target branches of the Epic to, manually, use the new PHP version (note that later, in the TODOs, well undo this manual configuration). (/) FINAL: get travis| and gha| working with the new php version () (/) FINAL: Verify that both install and upgrade from lowest possible site works ok, without any error/warning/notice. Both cli and web. (/) FINAL: Update docs| (and others, see testing instructions) once this is ready. (PR566| - ... And some tasks to do once this is upstream: TODO 1: (/) Review the travis and/or github actions configuration for various repositories. The new PHP version needs to be covered. Known to need review / fix repos include: - (/) (PR252| - moodle_docker| - (/) moodle-ci-runner| - (/) (MR43| - nightlyjobs| (dont forget to delete any manual configuration that has been done in advance for the, usually, MySQL (W) jobs in the Epic target branches). - (/) moodle-cs| - (/) moodle-plugin-ci| (version 4.0 being prepared @ dev-master, though version 3.x works ok too, it seems) - (/) (PR215| - local_codechecker| (waiting for to be integrated...) - (/) (PR105| - local_moodlecheck| - (/) local_ci| - (/) (Issue116| - moodle-tool_pluginskel| - (/) (PR3| - moodle-webservice_xmlrpc| - ... All the issues belonging to this epic should be pulled into master and MOODLE_401_STABLE (unless they are bug fixes requiring patching older, still supported, branches)
| Unsolvable | 1.summary: Verify that the apache logs are clean of PHP 8.1 notices/warnings/errors
description: Important note to developers: This is considered to be e FINAL task within the PHP X.Y issues, and better if its executed once the upstream branches are already passing both PHPUnit and Behat runs. Only that way the findings here will be useful. Once we get behat passing, its time to inspect web server logs to see if there is anything there that has not been detected by the runs. Usually we get both the logs from a js and non-js run and go looking to them. Ensure they are runs which PHP versions is the one being fixed in the Epic. Older ones arent meaningful for this issue. See for example to know how to clean the logs and focus on the important bits and, also, how to be able to know (by times) which the problematic scenario is.
2.summary: PHP 8.1: Fix all problems detected by phplint
description: Just run: code composer require --dev php-parallel-lint/php-parallel-lint && \ vendor/bin/parallel-lint --show-deprecated --exclude vendor . code And fix all the problems detected by the linter
3.summary: Wiki creole parser encodes single quotes in PHP8.1
description: Change in PHP8.1 (see ) code htmlspecialchars(), htmlentities(), htmlspecialchars_decode(), html_entity_decode() and get_html_translation_table() now use ENT_QUOTES | ENT_SUBSTITUTE rather than ENT_COMPAT by default. This means that is escaped to &039; while previously it was left alone. code
4.summary: Perform a complete PHPCompatibility 8.1 execution against codebase
description: This task is one of the final ones to perform when everything else in the epic has been already applied. Its about to run the PHPCompatibility standard (that we usually also run as part of our local_codechecker) against the whole codebase. Prerequisites: (/) The epic must be almost finished (to avoid detecting problems that correspond to other issues). (/) PHPCompatibility must support the php versions being checked. (/) Determine the range of PHP versions supported for the branch (7.4-8.1). See for 4.1 reqs. To perform the run against master, just: Clone locally. Ensure youre in the "develop" branch (the "master" branch contains the latest release, quite old now 2019). run composer install Run: code export DIRROOT=/path/to/your/moodle ; vendor/bin/phpcs \ --standard=PHPCompatibility \ --runtime-set testVersion 7.3-8.0 \ --extensions=php \ --ignore=$DIRROOT/vendor/,$DIRROOT/local/ \ --cache=/tmp/cache -p $DIRROOT code Look for detected stuff, discard false positives (it can be useful to look to the results of the previous PHP 8.0 Epic - ) to copy any decision here.
5.summary: Migrate away from use of strftime and friends
description: The strftime, and gmstrftime functions have been deprecated and will be removed in 9.0. See for further information. We will need to get on this ASAP and should take this opportunity to improve the core_date class (and/or replace it if relevant). The recognised replacement is to use the Intl library, which uses Unicode CLDR data rather than system locale data and alleviates other issues. With the right API design we can also hopefully improve our testing integrations.
6.summary: Skip behat tests requiring Solr if Solr is not installed
description: search/tests/behat/search_by_user.feature contains behat tests that require solr, and they fail if solr is not installed We skip such tests in unittests but do not skip in behat It is important for PHP 8.1 epic because Solr does not currently work in PHP 8.1 and we need to run all tests
7.summary: Bennu - patch for PHP 8.1 compatibility, add a test
description: Export calendar is not tested and Bennu library that we use there uses strftime that is deprecated in PHP 8.1 1. Patch bennu library, it looks like its abandoned - 2. Add a test for calendar export
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Prepare Moodle for PHP 8.1
description: !taken_on_near_completion.png! _(image taken near completion, now php81 is being tested everywhere, GHA, CIs... so no need for those custom tests and branches anymore)_ The, hopefully small, epic to turn Moodle ready for PHP 8.1. When: Being cristal clear (aka transparent), the ideal target release for this is Moodle 4.1.0 (aka, supported since the very beginning of the branch), but be warned that full support may arrive later in any Moodle 4.1.x minor release in the branch, depending of a number of factors (extensions availability and bugs, 3rd part libraries, last minute surprises...). Some initial links: - Main changes explained: and - Changes detailed: - Accepted RFCs: Some basic requirements for this: (/) get unit and acceptance tests passing against all databases (may imply the need of upgrading phpunit/behat...). (/) phpunit upgrade: (just small updates to 9.5.x) (/) behat upgrade: (just small updates to 3.11.x, and moving to upstream mink-extension). (/) check all the changes details| have been reviewed and fixed (attached file ^php81-progress.rtf ). Note that, until release, this file is considered WIP and subject to changes! (/) ensure older versions of Moodle dont work with PHP 8.1 () (/) get moodle-php-apache| docker images working with the new php version (/) verify that php-parallel-lint/php-parallel-lint| and others pass for all php versions () (/) search in the tracker for any issue created about "php 8.1" or "php81". Add them to this epic after analysing them. (/) FINAL: verify that the apache logs are clean of PHP 8.1 notices/warnings/errors () (/) FINAL: verify that all the issues found by the dev version of PHPCompatibility are fixed or false positives (). (/) FINAL: When CIs are passing consistently, put all the MySQL (W) jobs in the target branches of the Epic to, manually, use the new PHP version (note that later, in the TODOs, well undo this manual configuration). (/) FINAL: get travis| and gha| working with the new php version () (/) FINAL: Verify that both install and upgrade from lowest possible site works ok, without any error/warning/notice. Both cli and web. (/) FINAL: Update docs| (and others, see testing instructions) once this is ready. (PR566| - ... And some tasks to do once this is upstream: TODO 1: (/) Review the travis and/or github actions configuration for various repositories. The new PHP version needs to be covered. Known to need review / fix repos include: - (/) (PR252| - moodle_docker| - (/) moodle-ci-runner| - (/) (MR43| - nightlyjobs| (dont forget to delete any manual configuration that has been done in advance for the, usually, MySQL (W) jobs in the Epic target branches). - (/) moodle-cs| - (/) moodle-plugin-ci| (version 4.0 being prepared @ dev-master, though version 3.x works ok too, it seems) - (/) (PR215| - local_codechecker| (waiting for to be integrated...) - (/) (PR105| - local_moodlecheck| - (/) local_ci| - (/) (Issue116| - moodle-tool_pluginskel| - (/) (PR3| - moodle-webservice_xmlrpc| - ... All the issues belonging to this epic should be pulled into master and MOODLE_401_STABLE (unless they are bug fixes requiring patching older, still supported, branches)
### Response:
1.summary: Verify that the apache logs are clean of PHP 8.1 notices/warnings/errors
description: Important note to developers: This is considered to be e FINAL task within the PHP X.Y issues, and better if its executed once the upstream branches are already passing both PHPUnit and Behat runs. Only that way the findings here will be useful. Once we get behat passing, its time to inspect web server logs to see if there is anything there that has not been detected by the runs. Usually we get both the logs from a js and non-js run and go looking to them. Ensure they are runs which PHP versions is the one being fixed in the Epic. Older ones arent meaningful for this issue. See for example to know how to clean the logs and focus on the important bits and, also, how to be able to know (by times) which the problematic scenario is.
2.summary: PHP 8.1: Fix all problems detected by phplint
description: Just run: code composer require --dev php-parallel-lint/php-parallel-lint && \ vendor/bin/parallel-lint --show-deprecated --exclude vendor . code And fix all the problems detected by the linter
3.summary: Wiki creole parser encodes single quotes in PHP8.1
description: Change in PHP8.1 (see ) code htmlspecialchars(), htmlentities(), htmlspecialchars_decode(), html_entity_decode() and get_html_translation_table() now use ENT_QUOTES | ENT_SUBSTITUTE rather than ENT_COMPAT by default. This means that is escaped to &039; while previously it was left alone. code
4.summary: Perform a complete PHPCompatibility 8.1 execution against codebase
description: This task is one of the final ones to perform when everything else in the epic has been already applied. Its about to run the PHPCompatibility standard (that we usually also run as part of our local_codechecker) against the whole codebase. Prerequisites: (/) The epic must be almost finished (to avoid detecting problems that correspond to other issues). (/) PHPCompatibility must support the php versions being checked. (/) Determine the range of PHP versions supported for the branch (7.4-8.1). See for 4.1 reqs. To perform the run against master, just: Clone locally. Ensure youre in the "develop" branch (the "master" branch contains the latest release, quite old now 2019). run composer install Run: code export DIRROOT=/path/to/your/moodle ; vendor/bin/phpcs \ --standard=PHPCompatibility \ --runtime-set testVersion 7.3-8.0 \ --extensions=php \ --ignore=$DIRROOT/vendor/,$DIRROOT/local/ \ --cache=/tmp/cache -p $DIRROOT code Look for detected stuff, discard false positives (it can be useful to look to the results of the previous PHP 8.0 Epic - ) to copy any decision here.
5.summary: Migrate away from use of strftime and friends
description: The strftime, and gmstrftime functions have been deprecated and will be removed in 9.0. See for further information. We will need to get on this ASAP and should take this opportunity to improve the core_date class (and/or replace it if relevant). The recognised replacement is to use the Intl library, which uses Unicode CLDR data rather than system locale data and alleviates other issues. With the right API design we can also hopefully improve our testing integrations.
6.summary: Skip behat tests requiring Solr if Solr is not installed
description: search/tests/behat/search_by_user.feature contains behat tests that require solr, and they fail if solr is not installed We skip such tests in unittests but do not skip in behat It is important for PHP 8.1 epic because Solr does not currently work in PHP 8.1 and we need to run all tests
7.summary: Bennu - patch for PHP 8.1 compatibility, add a test
description: Export calendar is not tested and Bennu library that we use there uses strftime that is deprecated in PHP 8.1 1. Patch bennu library, it looks like its abandoned - 2. Add a test for calendar export
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Prepare Moodle for PHP 7.3
description: An, hopefully, small epic to turn Moodle ready for PHP 7.3 (end of 2018). Some initial links: - Main changes explained: - Accepted RFCs: - Deprecations: - Upgrading details: - Some basic requirements for this: - get unit and acceptance tests passing. - check all the upgrading details have been reviewed and fixed. - ensure older versions of Moodle dont work with PHP 7.3 () - Update docs| once this is ready. - ...
| Unsolvable | 1.summary: Add environment check for versions not supporting PHP 7.3
description: On Moodle 3.4 and 3.5, add an environmental check about PHP 7.3 not being supported. See previous as reference for this.
2.summary: Fix cases of continue within switch statements
description: With PHP 7.3 a warning has been added (about an existing problem) when continue; commands are used within switch statements. Really they act as normal break; statements there and, if within a loop, we should be using continue 2; instead. bq. PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2" Link: PHPUnit run: This is about to find all those continue uses within switch statements and replace them with the correct statement when needed. Some links explaining continue within switch and loops: - -
3.summary: Deprecated some flags using FILTER_VALIDATE_URL
description: quote The explicit usage of the constants FILTER_FLAG_SCHEME_REQUIRED and FILTER_FLAG_HOST_REQUIRED is now deprecated; both are implied for FILTER_VALIDATE_URL anyway. quote We have 2 uses of this is core: code lib/typo3/class.t3lib_div.php 1530: return (filter_var($IDN->encode($url), FILTER_VALIDATE_URL, FILTER_FLAG_SCHEME_REQUIRED) !== FALSE); lib/phpmailer/src/PHPMailer.php 3581: if (filter_var( . $host, FILTER_VALIDATE_URL, FILTER_FLAG_HOST_REQUIRED)) code Need to see if its reachable code and get rid of the deprecated flags (since 5.2!) to avoid this added PHP Deprecated warning: code PHP Deprecated: filter_var(): explicit use of FILTER_FLAG_SCHEME_REQUIRED and FILTER_FLAG_HOST_REQUIRED is deprecated in xxxx code
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Prepare Moodle for PHP 7.3
description: An, hopefully, small epic to turn Moodle ready for PHP 7.3 (end of 2018). Some initial links: - Main changes explained: - Accepted RFCs: - Deprecations: - Upgrading details: - Some basic requirements for this: - get unit and acceptance tests passing. - check all the upgrading details have been reviewed and fixed. - ensure older versions of Moodle dont work with PHP 7.3 () - Update docs| once this is ready. - ...
### Response:
1.summary: Add environment check for versions not supporting PHP 7.3
description: On Moodle 3.4 and 3.5, add an environmental check about PHP 7.3 not being supported. See previous as reference for this.
2.summary: Fix cases of continue within switch statements
description: With PHP 7.3 a warning has been added (about an existing problem) when continue; commands are used within switch statements. Really they act as normal break; statements there and, if within a loop, we should be using continue 2; instead. bq. PHP Warning: "continue" targeting switch is equivalent to "break". Did you mean to use "continue 2" Link: PHPUnit run: This is about to find all those continue uses within switch statements and replace them with the correct statement when needed. Some links explaining continue within switch and loops: - -
3.summary: Deprecated some flags using FILTER_VALIDATE_URL
description: quote The explicit usage of the constants FILTER_FLAG_SCHEME_REQUIRED and FILTER_FLAG_HOST_REQUIRED is now deprecated; both are implied for FILTER_VALIDATE_URL anyway. quote We have 2 uses of this is core: code lib/typo3/class.t3lib_div.php 1530: return (filter_var($IDN->encode($url), FILTER_VALIDATE_URL, FILTER_FLAG_SCHEME_REQUIRED) !== FALSE); lib/phpmailer/src/PHPMailer.php 3581: if (filter_var( . $host, FILTER_VALIDATE_URL, FILTER_FLAG_HOST_REQUIRED)) code Need to see if its reachable code and get rid of the deprecated flags (since 5.2!) to avoid this added PHP Deprecated warning: code PHP Deprecated: filter_var(): explicit use of FILTER_FLAG_SCHEME_REQUIRED and FILTER_FLAG_HOST_REQUIRED is deprecated in xxxx code
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Convert some of the "standard" user profile fields into custom user profile fields.
description: For a long time weve been talking about stripping the user table down to the essentials and converting some of the existing fields into "custom user profile fields" so that admins have more flexibility about allowing/displaying them. The problem is that so many things already expect to find this info into user table, and it is returned with many queries that return users, so it needs to be implemented carefully. This bug details this process, starting with the easy.
| Unsolvable | 1.summary: Convert user profile fields for messaging/networking into custom profile fields
description: These fields are pretty easy to convert during an upgrade. 1) Create a new user custom field. If its not possible to replicate the full functionality using a text field type (eg note that Skype can show an online/offline icon) then you will have to create a special new user profile field type as a new plugin. 2) Copy existing data into this new field. 3) Drop old column from the user table. 4) Make sure that all code no longer relies on this field. 5) Make sure that all code that provides user data (eg web services) behaves as expected and APIs are not changed. Fields include: - Web URL - ICQ - Skype - AIM - Yahoo - MSN
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Convert some of the "standard" user profile fields into custom user profile fields.
description: For a long time weve been talking about stripping the user table down to the essentials and converting some of the existing fields into "custom user profile fields" so that admins have more flexibility about allowing/displaying them. The problem is that so many things already expect to find this info into user table, and it is returned with many queries that return users, so it needs to be implemented carefully. This bug details this process, starting with the easy.
### Response:
1.summary: Convert user profile fields for messaging/networking into custom profile fields
description: These fields are pretty easy to convert during an upgrade. 1) Create a new user custom field. If its not possible to replicate the full functionality using a text field type (eg note that Skype can show an online/offline icon) then you will have to create a special new user profile field type as a new plugin. 2) Copy existing data into this new field. 3) Drop old column from the user table. 4) Make sure that all code no longer relies on this field. 5) Make sure that all code that provides user data (eg web services) behaves as expected and APIs are not changed. Fields include: - Web URL - ICQ - Skype - AIM - Yahoo - MSN
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: SCORM player
description: Implement a plugin for playing SCORM 1.2 contents
| Unsolvable | 1.summary: Implement the Cordova FileAPI to support usage of the file system in the dev. browser
description: In MM1 we supported the Cordova FileAPI natively in the browser, we should implement a mock for the Cordova library to use the native browser FileAPI. This will allow us to speed-up the development of new features that uses the File API like the SCORM module
2.summary: Backport the SCORM Web Services to the local_mobile plugin
description: Apart from backporting the Web Services we need the new global setting (proteckpackagedownloads) and modify the get_scorms_by_courses WS to return that setting from the local_mobile settings area
3.summary: Create a SCORM debugger package for testing the Run-Time implementation
description: We need a way to test if our run-time implementation support correctly all the elements (including objectives, interactions and nav.element)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: SCORM player
description: Implement a plugin for playing SCORM 1.2 contents
### Response:
1.summary: Implement the Cordova FileAPI to support usage of the file system in the dev. browser
description: In MM1 we supported the Cordova FileAPI natively in the browser, we should implement a mock for the Cordova library to use the native browser FileAPI. This will allow us to speed-up the development of new features that uses the File API like the SCORM module
2.summary: Backport the SCORM Web Services to the local_mobile plugin
description: Apart from backporting the Web Services we need the new global setting (proteckpackagedownloads) and modify the get_scorms_by_courses WS to return that setting from the local_mobile settings area
3.summary: Create a SCORM debugger package for testing the Run-Time implementation
description: We need a way to test if our run-time implementation support correctly all the elements (including objectives, interactions and nav.element)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Convert JS in Moodle from YUI to AMD modules
description: Over a few years we need to convert all of the JS in Moodle from yui to amd modules.
| Unsolvable | 1.summary: Convert form showadvanced from yui to amd
description: This should be a drop in replacement.
2.summary: Make searchableselector a wrapper for autocomplete
description: Autocomplete form element does everything searchable selector does - without yui and in a more usable way. They are api compatible so lets make searchableselector a wrapper for autocomplete.
3.summary: Convert single select to template and get rid of moodle-core-formautosubmit
description: moodle-core-formautosubmit is often needed on every page, its not a very big wrapper over what a small bit of jquery would do.
4.summary: Remove moodle-calendar-info and replace with bootstrap popovers
description: The current moodle-calendar-info is yui, adds two http requests to each page when the calendar block is visible and is quite out of style. It can be replaced with bootstrap tooltips !Screen Shot 2017-01-02 at 15.02.26.png|thumbnail!
5.summary: Avoid use of moodle-core-event unless YUI module actually needs it (so amd can be yui-free)
description: I have not thought deeply about this yet.. Weve got all our new AMD code which then requires the loading of the YUI module. I think that we could switch this around, so if no yui modules are listening, we just fire the events in AMD, then if a YUI module wants to listen for them, it requires the AMD module
6.summary: Replace moodle-core-notification-dialogue uses in amd code with core/modal
description: There are a few where we are calling out to AMD
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Convert JS in Moodle from YUI to AMD modules
description: Over a few years we need to convert all of the JS in Moodle from yui to amd modules.
### Response:
1.summary: Convert form showadvanced from yui to amd
description: This should be a drop in replacement.
2.summary: Make searchableselector a wrapper for autocomplete
description: Autocomplete form element does everything searchable selector does - without yui and in a more usable way. They are api compatible so lets make searchableselector a wrapper for autocomplete.
3.summary: Convert single select to template and get rid of moodle-core-formautosubmit
description: moodle-core-formautosubmit is often needed on every page, its not a very big wrapper over what a small bit of jquery would do.
4.summary: Remove moodle-calendar-info and replace with bootstrap popovers
description: The current moodle-calendar-info is yui, adds two http requests to each page when the calendar block is visible and is quite out of style. It can be replaced with bootstrap tooltips !Screen Shot 2017-01-02 at 15.02.26.png|thumbnail!
5.summary: Avoid use of moodle-core-event unless YUI module actually needs it (so amd can be yui-free)
description: I have not thought deeply about this yet.. Weve got all our new AMD code which then requires the loading of the YUI module. I think that we could switch this around, so if no yui modules are listening, we just fire the events in AMD, then if a YUI module wants to listen for them, it requires the AMD module
6.summary: Replace moodle-core-notification-dialogue uses in amd code with core/modal
description: There are a few where we are calling out to AMD
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Add learning outcomes: new metadata field
description: Add new metadata field to describe a resource. UX idea| UX idea inspired from CADMOS|
| Solvable | 1.summary: Learning outcomes in Resources
description: See in GitHub issue| Metadata list for Resources Description Teaching subject Teaching level Content language Learning outcome Creation date Upload date Resource Type Resource Format
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Add learning outcomes: new metadata field
description: Add new metadata field to describe a resource. UX idea| UX idea inspired from CADMOS|
### Response:
1.summary: Learning outcomes in Resources
description: See in GitHub issue| Metadata list for Resources Description Teaching subject Teaching level Content language Learning outcome Creation date Upload date Resource Type Resource Format
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 4.3
description: In Moodle 4.3 we can remove functionality that was deprecated in 3.11 or earlier (see policy issue) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
| Unsolvable | 1.summary: Move php-sodium recommendation back to requirement
description: In the 3.11 requirements issues ( and ) it was initially agreed to make the php-sodium extension a requirement for Moodle. But, in the very same issues, it was finally decided to lower it to be only a recommendation and that was done @ . Part of that issue and the decisions taken was that the "lowering" was only a temporal solution and, as soon as a new LTS was released (4.1), the requirement would be back, removing the current fallback (less strong crypto-code) allowing Moodle to work without php-sodium. For more information about the discussions and rationale for the changes, please visit the linked issues. So this is issue is about to: 1) Make php-sodium a requirement for 4.2 (1st version after LTS). Done @ 2) Final removal of the fallback code @ lib/classes/encryption.php 3) Consider what to do with the decrypt() method that may need to continue supporting the openssl fallback forever. Alternatively is to convert, in upgrade, all the encrypted contents to the new, sodium, alternative, but Im not sure if thats possible. Note this will need to be linked to the "4.2 moodle requirements"| issue whenever it becomes created.
2.summary: Remove support for Legacy cron
description: So it is 2023 now, and the worlds Global climate problem has been solved. I guess it is time to abandon the old legacy cron system. Hence, we need to remove support for it. TODO: mark as closed as soon as this issue is fixed.
3.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.9
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.9 should be replaced with exceptions in 4.1. This includes all functions in lib/deprecatedlib.php that say since 3.9 (or earlier). If any functions from this file do not have this comment but also need to be finally deprecated in 4.1 - please list them in this issue description.
4.summary: Final deprecation of get_enabledcontenttypes()
description: Remove the function get_enabledcontenttypes().
5.summary: Final deprecation of \core_p\file_storage::EDITOR_FILEAREA constant
description: Only if goes in. In temporary files from the editor will be moved from core_p/editor to user/draft. So the constant \core_p\file_storage::EDITOR_FILEAREA isnt required any more.
6.summary: Final deprecation of extend_lock()
description: The function extend_lock() was deprecated in . As were the following: \core\lock\lock::extend \core\lock\lock_factory::extend_lock \core\lock\lock_factory::supports_recursion
7.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.11
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.11 should be replaced with exceptions in 4.3. This includes all functions in lib/deprecatedlib.php that say since 3.11 (or earlier). If any functions from this file do not have this comment but also need to be finally deprecated in 4.3 - please list them in this issue description.
8.summary: Remove behat steps deprecated in 3.11
description: Go through lib/tests/behat/behat_deprecated.php and remove steps that were deprecated in Moodle 3.11 (or earlier). Please add to the description if you know of any other deprecated behat functionality outside of this file that needs to be removed.
9.summary: Remove strings deprecated in 3.11
description: Remove strings from language files under the heading "Deprecated in Moodle 3.11" and the respective lines in deprecated.txt files See also
10.summary: Remove old classes renamed in 3.11
description: This issue is about to review all the /db/renamedclasses.php that were renamed "since" Moodle 3.11 or earlier and remove them completely from core, adding a note in the corresponding upgrade.txt files.
11.summary: Final deprecation of whitelist properties in coverage_info
description: With the bump to PHPUnit @ (Moodle 3.11), some parts of the phpunit.xml schema were changed. One of the changes was about to rename the old whitelist to include. That was done and, in parallel, we changed our coverage_info properties in the same direction: - whitelistfolders => includelistfolders - whitelistfiles => includelistfiles And left the old (whitelist) ones deprecated, so they continue working but display a warning when the PHPUnit site is created. Now, for Moodle 4.3, we should remove them completely. To do it, just look for this issue code () in codebase and remove the 2 properties and 1 block (if-block) of code. Verify that there arent more occurrences in code, apart from the change that was documented in lib/upgrade.txt. Ciao :-)
12.summary: Final deprecation of contentbank/upload.php
description: In the form to upload files to the content bank has been replaced to modal. This issue is about removing the file contentbank/upload.php definitively.
13.summary: Final deprecation for \core_course_renderer::course_section_cm_completion()
description: \core_course_renderer::course_section_cm_completion() is being deprecated in as it is no longer being used and is being replaced by the activity information output component.
14.summary: Final deprecation of create_gradecategory webservice
description: Remove the webservice from webservices, and the underlying external functions, as well as the tests for the service.
15.summary: Final deprecation of user profile functions
description: The following functions were deprecated in 3.11 and need to be removed in 4.3 user/profile/definelib.php: profile_edit_category() profile_edit_field() user/profile/lib.php profile_display_fields()
16.summary: Final deprecation of _get_completion_state() callbacks
description: _get_completion_state() callbacks are being deprecated in as it is no longer used and is being replaced by the activity custom completion classes.
17.summary: Final deprecation of function: course_section_add_cm_control_nonajax()
description: Final deprecation for the function, `course_section_add_cm_control_nonajax()`, should be done in Moodle 4.3. It was deprecated in 3.11+master in .
18.summary: Final deprecation of badge backpack methods from 3.11
description: Perform the final stage of deprecation process on methods initially deprecated as part of (methods in lib/badgeslib.php)
19.summary: forum_print_discussion_header should be deprecated
description: The forum_print_discussion_header function was only ever called by forum_print_latest_discussions, but that was deprecated in Moodle 3.7, and removed in Moodle 4.0. This method was missed in the deprecation.
20.summary: Remove old mod_assign deprecated methods
description: These were both deprecated in 2.7 and never processed finally: format_grade_for_log format_submission_for_log There is also an add_to_log definition but I believe that will be handled elsewhere.
21.summary: Final deprecation of the $extradetails parameter in mod_feedback\output\summary constructor
description: The $extradetails parameter in the constructor of the mod_feedback\output\summary class was deprecated in and it must be removed here.
22.summary: Deprecate unused \calendar_top_controls()
description: \calendar_top_controls() is being used by \core_calendar\external\day_exporter()| for its navigation context data. However, the navigation context data is not being used anywhere within the calendar templates. So theres really no point adding this context data. Removing this will also mean that calendar_top_controls() will no longer be used and is better suited to be deprecated.
23.summary: Deprecate other unused calendar functions
description: We have some calendar functions that will no longer be used with calendar_top_controls() now deprecated. These are: calendar_get_link_previous() calendar_get_link_next() We need to deprecate these as well.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 4.3
description: In Moodle 4.3 we can remove functionality that was deprecated in 3.11 or earlier (see policy issue) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
### Response:
1.summary: Move php-sodium recommendation back to requirement
description: In the 3.11 requirements issues ( and ) it was initially agreed to make the php-sodium extension a requirement for Moodle. But, in the very same issues, it was finally decided to lower it to be only a recommendation and that was done @ . Part of that issue and the decisions taken was that the "lowering" was only a temporal solution and, as soon as a new LTS was released (4.1), the requirement would be back, removing the current fallback (less strong crypto-code) allowing Moodle to work without php-sodium. For more information about the discussions and rationale for the changes, please visit the linked issues. So this is issue is about to: 1) Make php-sodium a requirement for 4.2 (1st version after LTS). Done @ 2) Final removal of the fallback code @ lib/classes/encryption.php 3) Consider what to do with the decrypt() method that may need to continue supporting the openssl fallback forever. Alternatively is to convert, in upgrade, all the encrypted contents to the new, sodium, alternative, but Im not sure if thats possible. Note this will need to be linked to the "4.2 moodle requirements"| issue whenever it becomes created.
2.summary: Remove support for Legacy cron
description: So it is 2023 now, and the worlds Global climate problem has been solved. I guess it is time to abandon the old legacy cron system. Hence, we need to remove support for it. TODO: mark as closed as soon as this issue is fixed.
3.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.9
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.9 should be replaced with exceptions in 4.1. This includes all functions in lib/deprecatedlib.php that say since 3.9 (or earlier). If any functions from this file do not have this comment but also need to be finally deprecated in 4.1 - please list them in this issue description.
4.summary: Final deprecation of get_enabledcontenttypes()
description: Remove the function get_enabledcontenttypes().
5.summary: Final deprecation of \core_p\file_storage::EDITOR_FILEAREA constant
description: Only if goes in. In temporary files from the editor will be moved from core_p/editor to user/draft. So the constant \core_p\file_storage::EDITOR_FILEAREA isnt required any more.
6.summary: Final deprecation of extend_lock()
description: The function extend_lock() was deprecated in . As were the following: \core\lock\lock::extend \core\lock\lock_factory::extend_lock \core\lock\lock_factory::supports_recursion
7.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.11
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.11 should be replaced with exceptions in 4.3. This includes all functions in lib/deprecatedlib.php that say since 3.11 (or earlier). If any functions from this file do not have this comment but also need to be finally deprecated in 4.3 - please list them in this issue description.
8.summary: Remove behat steps deprecated in 3.11
description: Go through lib/tests/behat/behat_deprecated.php and remove steps that were deprecated in Moodle 3.11 (or earlier). Please add to the description if you know of any other deprecated behat functionality outside of this file that needs to be removed.
9.summary: Remove strings deprecated in 3.11
description: Remove strings from language files under the heading "Deprecated in Moodle 3.11" and the respective lines in deprecated.txt files See also
10.summary: Remove old classes renamed in 3.11
description: This issue is about to review all the /db/renamedclasses.php that were renamed "since" Moodle 3.11 or earlier and remove them completely from core, adding a note in the corresponding upgrade.txt files.
11.summary: Final deprecation of whitelist properties in coverage_info
description: With the bump to PHPUnit @ (Moodle 3.11), some parts of the phpunit.xml schema were changed. One of the changes was about to rename the old whitelist to include. That was done and, in parallel, we changed our coverage_info properties in the same direction: - whitelistfolders => includelistfolders - whitelistfiles => includelistfiles And left the old (whitelist) ones deprecated, so they continue working but display a warning when the PHPUnit site is created. Now, for Moodle 4.3, we should remove them completely. To do it, just look for this issue code () in codebase and remove the 2 properties and 1 block (if-block) of code. Verify that there arent more occurrences in code, apart from the change that was documented in lib/upgrade.txt. Ciao :-)
12.summary: Final deprecation of contentbank/upload.php
description: In the form to upload files to the content bank has been replaced to modal. This issue is about removing the file contentbank/upload.php definitively.
13.summary: Final deprecation for \core_course_renderer::course_section_cm_completion()
description: \core_course_renderer::course_section_cm_completion() is being deprecated in as it is no longer being used and is being replaced by the activity information output component.
14.summary: Final deprecation of create_gradecategory webservice
description: Remove the webservice from webservices, and the underlying external functions, as well as the tests for the service.
15.summary: Final deprecation of user profile functions
description: The following functions were deprecated in 3.11 and need to be removed in 4.3 user/profile/definelib.php: profile_edit_category() profile_edit_field() user/profile/lib.php profile_display_fields()
16.summary: Final deprecation of _get_completion_state() callbacks
description: _get_completion_state() callbacks are being deprecated in as it is no longer used and is being replaced by the activity custom completion classes.
17.summary: Final deprecation of function: course_section_add_cm_control_nonajax()
description: Final deprecation for the function, `course_section_add_cm_control_nonajax()`, should be done in Moodle 4.3. It was deprecated in 3.11+master in .
18.summary: Final deprecation of badge backpack methods from 3.11
description: Perform the final stage of deprecation process on methods initially deprecated as part of (methods in lib/badgeslib.php)
19.summary: forum_print_discussion_header should be deprecated
description: The forum_print_discussion_header function was only ever called by forum_print_latest_discussions, but that was deprecated in Moodle 3.7, and removed in Moodle 4.0. This method was missed in the deprecation.
20.summary: Remove old mod_assign deprecated methods
description: These were both deprecated in 2.7 and never processed finally: format_grade_for_log format_submission_for_log There is also an add_to_log definition but I believe that will be handled elsewhere.
21.summary: Final deprecation of the $extradetails parameter in mod_feedback\output\summary constructor
description: The $extradetails parameter in the constructor of the mod_feedback\output\summary class was deprecated in and it must be removed here.
22.summary: Deprecate unused \calendar_top_controls()
description: \calendar_top_controls() is being used by \core_calendar\external\day_exporter()| for its navigation context data. However, the navigation context data is not being used anywhere within the calendar templates. So theres really no point adding this context data. Removing this will also mean that calendar_top_controls() will no longer be used and is better suited to be deprecated.
23.summary: Deprecate other unused calendar functions
description: We have some calendar functions that will no longer be used with calendar_top_controls() now deprecated. These are: calendar_get_link_previous() calendar_get_link_next() We need to deprecate these as well.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Improve mod_book editing interface
description: We need to look at how one edits mod_book pages and chapters. The current UI leads to a confusing UX and it is very difficult for new users to work out how to edit content - it is not immediately apparent that you must use the cog icon in the Table of contents block. We need to look at what we can do to improve the editing experience. This may include: adding a pencil icon to the page for all editors removing the modal editing concept (Turn editing on) Adding inplace-editables to change the title (may be difficult with the TOC) Improved TOC editing: Drag/drop re-ordering AJAX hide/reveal Improve clarity of "Add chapter" link - e.g. where is it added when adding a new subchapter to a subchapter (its the same level) Clearer "Add chapter" interface - e.g. indicating the eventual location of the chapter when adding a subchapter
| Unsolvable | 1.summary: Define a renderer for book
description: It will be great if we can define a renderer template for book. Specially book/tool/index.php needs a cleanup and it will be good if the renderer codes be reused there.
2.summary: Put "Turn editing on" button in a more obvious location
description: The link to edit book pages ("Turn editing on") is currently hidden at the end of the list in the "Administration" block. As users reported to me, it is quite hard to find there. Better solutions include: a) Have a "Turn editing on" button in the same place as on the main course page, i.e., on the top-right of the screen; b) Add a "Turn editing on" icon in the "Table of contents" block, where per-chapter editing icons currently appear after editing is turned on.
3.summary: Support collapsing of TOC chapters
description: This is a request to reopen , and the title says it all. I must say, it seems a very obvious and simple to implement request, given that sub-chapters can easily number into the several 10s.
4.summary: Improve formatting of (sub)chapter number + title
description: When we create a Book with numbered chapters, the chapter numerals do not have a period or other spacing punctuation before the Chapters title in the book navigation block and also the page title. ie. 1 My Chapter Title instead of 1. My Chapter Title
5.summary: Hiding all book chapters causes editing ability to disappear
description: 1. Create book module by adding Title to corresponding field and save and display 2. Youre taken to page to create first chapter. Add Title and Content to corresponding fields. Save changes 3. Youll be taken into the book and editing will be still turned on. 4. Hide the chapter you just created in the Table of Contents. All chapters are now hidden but you still have editing turned on. 5. Turn editing off in Administration block. Youll still be in book and still have the option to turn editing back on. Dont do so. 6. Navigate back to the course page and then click on the book or click on book name in bread crumbs trail to refresh page contents. If you just do a browser refresh, it is going to keep the session key and editing parameter in the URL but we need that cleared out. 7. Now back in the book, the table of contents will be gone and youll get a message of "No content has been added to this book yet" and a Continue button that takes you back to the course page. In addition, the Turn editing on link is gone from the Administration block. From an instructors viewpoint, it looks like all their content is gone. To resolve, instructor must go back to the course page, turn editing on there and then go back into the book. Video demo of bug - Tested and was able to replicate on my own site (2.8.10) and on core demo site (3.0.3 - as of April 11th, 2016). Assuming it affects everything in between as well.
6.summary: Add additional chapter information to in-page nav
description: We have Next page + Previous page navigation within the book. The alt attribute on the image, and the title attribute on the link are both set to basic strings "Next" and "Previous". Lets make these more descriptive by adding the details of the new page. Note, we only need to do this for image navigation. The "Text" navigation is already appropriate.
7.summary: Table of contents block should be shown on all editing pages
description: The Table of Contents is currently only shown when viewing the book. For better contextual relevance it should also be shown when creating, editing, and deleting chapters.
8.summary: Chapter deletion should use JS confirmation
description: Chapter deletion should use JS confirmation Nice and easy like.
9.summary: Add additional print options
description: The book currently has support for: Print Book Print Chapter In the case of the Chapter option, this only allows printing of the current exact chapter and not the whole chapter. Consider the following Table of Contents: Introduction Wildflowers of WA The Kimberley Pinjelly Margaret River Native plants Xanthorroea Succulents Summary With the current Print Chapter option, if you chose to print the "Wildflowers of WA" section, you would only get the one page, and not each of the sub-chapters. We should: Rename the current "Print chapter" option to be more specific; and Add a new "Print whole chapter" When viewing a subchapter, or a chapter with subchapters
10.summary: Move Print options to page body
description: This is a proposal to move the print options out of the administration block and into a dropdown (action menu) in the page body.
11.summary: Move edit options to page body
description: This is a proposal to move the edit options out of the administration block and into a dropdown (action menu) in the page body. This includes: Edit this chapter Delete this chapter We still need to consider how the following can be managed: Add a new chapter after this one Move up Move down This is to try and reduce the clutter in the Table of content when editing is turned on
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Improve mod_book editing interface
description: We need to look at how one edits mod_book pages and chapters. The current UI leads to a confusing UX and it is very difficult for new users to work out how to edit content - it is not immediately apparent that you must use the cog icon in the Table of contents block. We need to look at what we can do to improve the editing experience. This may include: adding a pencil icon to the page for all editors removing the modal editing concept (Turn editing on) Adding inplace-editables to change the title (may be difficult with the TOC) Improved TOC editing: Drag/drop re-ordering AJAX hide/reveal Improve clarity of "Add chapter" link - e.g. where is it added when adding a new subchapter to a subchapter (its the same level) Clearer "Add chapter" interface - e.g. indicating the eventual location of the chapter when adding a subchapter
### Response:
1.summary: Define a renderer for book
description: It will be great if we can define a renderer template for book. Specially book/tool/index.php needs a cleanup and it will be good if the renderer codes be reused there.
2.summary: Put "Turn editing on" button in a more obvious location
description: The link to edit book pages ("Turn editing on") is currently hidden at the end of the list in the "Administration" block. As users reported to me, it is quite hard to find there. Better solutions include: a) Have a "Turn editing on" button in the same place as on the main course page, i.e., on the top-right of the screen; b) Add a "Turn editing on" icon in the "Table of contents" block, where per-chapter editing icons currently appear after editing is turned on.
3.summary: Support collapsing of TOC chapters
description: This is a request to reopen , and the title says it all. I must say, it seems a very obvious and simple to implement request, given that sub-chapters can easily number into the several 10s.
4.summary: Improve formatting of (sub)chapter number + title
description: When we create a Book with numbered chapters, the chapter numerals do not have a period or other spacing punctuation before the Chapters title in the book navigation block and also the page title. ie. 1 My Chapter Title instead of 1. My Chapter Title
5.summary: Hiding all book chapters causes editing ability to disappear
description: 1. Create book module by adding Title to corresponding field and save and display 2. Youre taken to page to create first chapter. Add Title and Content to corresponding fields. Save changes 3. Youll be taken into the book and editing will be still turned on. 4. Hide the chapter you just created in the Table of Contents. All chapters are now hidden but you still have editing turned on. 5. Turn editing off in Administration block. Youll still be in book and still have the option to turn editing back on. Dont do so. 6. Navigate back to the course page and then click on the book or click on book name in bread crumbs trail to refresh page contents. If you just do a browser refresh, it is going to keep the session key and editing parameter in the URL but we need that cleared out. 7. Now back in the book, the table of contents will be gone and youll get a message of "No content has been added to this book yet" and a Continue button that takes you back to the course page. In addition, the Turn editing on link is gone from the Administration block. From an instructors viewpoint, it looks like all their content is gone. To resolve, instructor must go back to the course page, turn editing on there and then go back into the book. Video demo of bug - Tested and was able to replicate on my own site (2.8.10) and on core demo site (3.0.3 - as of April 11th, 2016). Assuming it affects everything in between as well.
6.summary: Add additional chapter information to in-page nav
description: We have Next page + Previous page navigation within the book. The alt attribute on the image, and the title attribute on the link are both set to basic strings "Next" and "Previous". Lets make these more descriptive by adding the details of the new page. Note, we only need to do this for image navigation. The "Text" navigation is already appropriate.
7.summary: Table of contents block should be shown on all editing pages
description: The Table of Contents is currently only shown when viewing the book. For better contextual relevance it should also be shown when creating, editing, and deleting chapters.
8.summary: Chapter deletion should use JS confirmation
description: Chapter deletion should use JS confirmation Nice and easy like.
9.summary: Add additional print options
description: The book currently has support for: Print Book Print Chapter In the case of the Chapter option, this only allows printing of the current exact chapter and not the whole chapter. Consider the following Table of Contents: Introduction Wildflowers of WA The Kimberley Pinjelly Margaret River Native plants Xanthorroea Succulents Summary With the current Print Chapter option, if you chose to print the "Wildflowers of WA" section, you would only get the one page, and not each of the sub-chapters. We should: Rename the current "Print chapter" option to be more specific; and Add a new "Print whole chapter" When viewing a subchapter, or a chapter with subchapters
10.summary: Move Print options to page body
description: This is a proposal to move the print options out of the administration block and into a dropdown (action menu) in the page body.
11.summary: Move edit options to page body
description: This is a proposal to move the edit options out of the administration block and into a dropdown (action menu) in the page body. This includes: Edit this chapter Delete this chapter We still need to consider how the following can be managed: Add a new chapter after this one Move up Move down This is to try and reduce the clutter in the Table of content when editing is turned on
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: User stories for the MUA-32 work
description: A collection of User stories for MUA-32
| Unsolvable | 1.summary: As a teacher, I can add tag(s) to a question bank question for use in my course for organizational and search/filtering of questions.
description: As a teacher in a course I should be able to click the tag icon for a question bank question to add/modify/remove course level tags for any question I can see which will apply when the question is searched for in this course As a teacher in a course who can edit a question from the course, I can add/modify/remove tags directly on the question, in the edit question form which will apply when the question is searched for in this course As a user who can edit questions outside of a course (belonging to the course category or site context), I can add/modify/remove tags directly on the question edit form, which will apply in all contexts the question can be used Clicking the tag icon should open a dialog specifying category, course and question name, an overview of assigned tags and a text field to allow entering custom tags All teachers in a course can see the full list of tags either directly attached to the question from the question bank, or only attached to the question in this course Question tags are not specific to a single user (not private) Course backups should contain course level question tags A course restored from a backup should contain the same set of course level question tags pointing to the correct questions in all cases (same site, new site etc). Any webservices that allow for searching for questions by tag need to return questions either by question tags, or course question tags. Any webservices returning the list of tags for a question needs to include both the question tags and the course question tags
2.summary: As a teacher, I can filter my questions in courses based on tags.
description: I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a drop down I should be able to filter by tag when editing questions from the Question Bank page The list of tags should provide suggestions based on the tag containers for both the question tags and the course question tags
3.summary: As a teacher, I can see tags on all questions that I have access to
description: As a teacher, I can see tags on all questions that I have access to: I should be able to see the tags in any context, including: Course context Course category context Site context
4.summary: As another teacher in the same course, I have access to the question tags on the questions in that course context.
description: I should be able to add course level tags to a question defined at course category or site level I should be able to see the course level tags defined by other teachers for this course
5.summary: As a teacher in a course, I do not see tags of others in contexts I do not have access to. (Instructor 1 s midterm 1 question set would not be relevant to Instructor 2 from a different course)
description: As a teacher in a course, I do not see tags of others in contexts I do not have access to. (Instructor 1 s midterm 1 question set would not be relevant to Instructor 2 from a different course) I should not be able to access course level tags from a course I do not have access to. I should not be able to access course category tags for categories I do not have access to. All users should have access to questions by tag belonging to the site context
6.summary: As a teacher, I am able to add/modify/remove tags on questions.
description: This is included in the first requirement As a teacher, I can add tag(s) to a question bank question for use in my course for organizational and search/filtering of questions.
7.summary: As a teacher, I should not have to copy a question into my course from higher category contexts to include it in a random question question type.
description: When adding a random question from a question category and tag (at a course level), I can select questions that exist (or are newly created) in a higher category context. If a question is deleted and it has active attempts, the data for the question will remain but it will not be selectable to add to new quizzes.
8.summary: As a teacher, I can add a random question to my quiz where the question is taken from a question category (optionally including sub categories) with optional filtering by tags.
description: The add a random question dialog allows for: Selecting a question category; Specifying whether questions from sub categories should be included, and filtering of the random questions in the question bank by specifying a tag, either by entering free text or selecting tags from a drop down. If the search returns no results you will still be able to create a random question, but until new questions are added matching the search criteria, the quiz will display an error. You will no longer be able to add a new question category at the same time as creating a random question (there is not enough room to display a preview of the search as well as this create new question category option).
9.summary: Tags can contain any visible ASCII characters including characters such as apostrophes, slashes, and colons. Exception of Comma.
description: I can define tags using any visible ASCII character apart from the comma I receive a warning message when I try to define a tag that contains a comma, informing me that the comma character is not allowed.
10.summary: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible.
description: I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
11.summary: As a teacher, I can export/import questions with their tags.
description: When using Moodle XML format I can export questions with all site, category, course and user level tags that are available to me. I can import questions using Moodle XML format and their associated site, category, course and user level tags will be imported A file imported without course question tags should still import successfully
12.summary: As a user with appropriate capabilities, I can add a tag(s) to a question bank question that exist at the category context
description: As a user with appropriate capabilities, I can add a tag(s) to a question bank question that exist at the category context. As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context. As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context. I should be able to click the tag icon for a question bank question at the category context to add/modify/remove tags for each question Clicking the tag icon should open a dialog specifying category and question name, a list of the question tags belonging directly to the question, the current course name and a list of the question tags attached only in this course. The list of tags attached directly to the question will only be editable if the user has the capability to edit the question.
13.summary: As a user who can access the Question Bank, I can search/filter all the questions I have access to, based on category or tags, and see them along with their context
description: As a user who can access the Question Bank, I can search/filter all the questions I have access to, based on category or tags, and see them along with their context. I should be able to filter by tag when editing questions from the Question Bank page The list of tags should provide suggestions based on the tag containers for both the question tags and the course question tags
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: User stories for the MUA-32 work
description: A collection of User stories for MUA-32
### Response:
1.summary: As a teacher, I can add tag(s) to a question bank question for use in my course for organizational and search/filtering of questions.
description: As a teacher in a course I should be able to click the tag icon for a question bank question to add/modify/remove course level tags for any question I can see which will apply when the question is searched for in this course As a teacher in a course who can edit a question from the course, I can add/modify/remove tags directly on the question, in the edit question form which will apply when the question is searched for in this course As a user who can edit questions outside of a course (belonging to the course category or site context), I can add/modify/remove tags directly on the question edit form, which will apply in all contexts the question can be used Clicking the tag icon should open a dialog specifying category, course and question name, an overview of assigned tags and a text field to allow entering custom tags All teachers in a course can see the full list of tags either directly attached to the question from the question bank, or only attached to the question in this course Question tags are not specific to a single user (not private) Course backups should contain course level question tags A course restored from a backup should contain the same set of course level question tags pointing to the correct questions in all cases (same site, new site etc). Any webservices that allow for searching for questions by tag need to return questions either by question tags, or course question tags. Any webservices returning the list of tags for a question needs to include both the question tags and the course question tags
2.summary: As a teacher, I can filter my questions in courses based on tags.
description: I should be able to filter by tag when adding questions to a quiz, either by entering free text or selecting from a drop down I should be able to filter by tag when editing questions from the Question Bank page The list of tags should provide suggestions based on the tag containers for both the question tags and the course question tags
3.summary: As a teacher, I can see tags on all questions that I have access to
description: As a teacher, I can see tags on all questions that I have access to: I should be able to see the tags in any context, including: Course context Course category context Site context
4.summary: As another teacher in the same course, I have access to the question tags on the questions in that course context.
description: I should be able to add course level tags to a question defined at course category or site level I should be able to see the course level tags defined by other teachers for this course
5.summary: As a teacher in a course, I do not see tags of others in contexts I do not have access to. (Instructor 1 s midterm 1 question set would not be relevant to Instructor 2 from a different course)
description: As a teacher in a course, I do not see tags of others in contexts I do not have access to. (Instructor 1 s midterm 1 question set would not be relevant to Instructor 2 from a different course) I should not be able to access course level tags from a course I do not have access to. I should not be able to access course category tags for categories I do not have access to. All users should have access to questions by tag belonging to the site context
6.summary: As a teacher, I am able to add/modify/remove tags on questions.
description: This is included in the first requirement As a teacher, I can add tag(s) to a question bank question for use in my course for organizational and search/filtering of questions.
7.summary: As a teacher, I should not have to copy a question into my course from higher category contexts to include it in a random question question type.
description: When adding a random question from a question category and tag (at a course level), I can select questions that exist (or are newly created) in a higher category context. If a question is deleted and it has active attempts, the data for the question will remain but it will not be selectable to add to new quizzes.
8.summary: As a teacher, I can add a random question to my quiz where the question is taken from a question category (optionally including sub categories) with optional filtering by tags.
description: The add a random question dialog allows for: Selecting a question category; Specifying whether questions from sub categories should be included, and filtering of the random questions in the question bank by specifying a tag, either by entering free text or selecting tags from a drop down. If the search returns no results you will still be able to create a random question, but until new questions are added matching the search criteria, the quiz will display an error. You will no longer be able to add a new question category at the same time as creating a random question (there is not enough room to display a preview of the search as well as this create new question category option).
9.summary: Tags can contain any visible ASCII characters including characters such as apostrophes, slashes, and colons. Exception of Comma.
description: I can define tags using any visible ASCII character apart from the comma I receive a warning message when I try to define a tag that contains a comma, informing me that the comma character is not allowed.
10.summary: As a teacher, when searching for questions to add to a random question I see the question with its context clearly visible.
description: I can see the questions listed in the add a random question dialog I can see the counts of questions matching the search criteria for each separate context
11.summary: As a teacher, I can export/import questions with their tags.
description: When using Moodle XML format I can export questions with all site, category, course and user level tags that are available to me. I can import questions using Moodle XML format and their associated site, category, course and user level tags will be imported A file imported without course question tags should still import successfully
12.summary: As a user with appropriate capabilities, I can add a tag(s) to a question bank question that exist at the category context
description: As a user with appropriate capabilities, I can add a tag(s) to a question bank question that exist at the category context. As a user with the moodle/question:tagall capability, I can add tag(s) to any question bank question that exist at the course category context. As a user with the moodle/question:tagmine capability, I can add tag(s) to any question bank question that I created and which exists at the course category context. I should be able to click the tag icon for a question bank question at the category context to add/modify/remove tags for each question Clicking the tag icon should open a dialog specifying category and question name, a list of the question tags belonging directly to the question, the current course name and a list of the question tags attached only in this course. The list of tags attached directly to the question will only be editable if the user has the capability to edit the question.
13.summary: As a user who can access the Question Bank, I can search/filter all the questions I have access to, based on category or tags, and see them along with their context
description: As a user who can access the Question Bank, I can search/filter all the questions I have access to, based on category or tags, and see them along with their context. I should be able to filter by tag when editing questions from the Question Bank page The list of tags should provide suggestions based on the tag containers for both the question tags and the course question tags
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle sites 2.8.5 upgrade
description:
| Unsolvable | 1.summary: Upgrade moodle.org to 2.8.5
description: Reminder from David: quoteWe need to 1) upgrade the spam block and 2) test that is fixedquote
2.summary: Upgrade learn.moodle.net to 2.8.5
description:
3.summary: Upgrade lang.moodle.org to 2.8.5
description:
4.summary: Upgrade download.moodle.org to 2.8.5
description:
5.summary: Upgrade school.demo.moodle.net to 2.8.5
description:
6.summary: Upgrade demo.moodle.net to 2.8.5
description:
7.summary: Upgrade dev.moodle.org to 2.8.5
description:
8.summary: Upgrade moodle.net to 2.8.5
description:
9.summary: Upgrade research.moodle.net to 2.8.5
description:
10.summary: Upgrade moodlemoot.org sites to 2.8.5
description: mootau15 mootieuk15 and mootus15
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle sites 2.8.5 upgrade
description:
### Response:
1.summary: Upgrade moodle.org to 2.8.5
description: Reminder from David: quoteWe need to 1) upgrade the spam block and 2) test that is fixedquote
2.summary: Upgrade learn.moodle.net to 2.8.5
description:
3.summary: Upgrade lang.moodle.org to 2.8.5
description:
4.summary: Upgrade download.moodle.org to 2.8.5
description:
5.summary: Upgrade school.demo.moodle.net to 2.8.5
description:
6.summary: Upgrade demo.moodle.net to 2.8.5
description:
7.summary: Upgrade dev.moodle.org to 2.8.5
description:
8.summary: Upgrade moodle.net to 2.8.5
description:
9.summary: Upgrade research.moodle.net to 2.8.5
description:
10.summary: Upgrade moodlemoot.org sites to 2.8.5
description: mootau15 mootieuk15 and mootus15
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: MUA Project: Improve Student Activity Completion
description: This epic covers deliverable elements of the MUA "Improve Student Activity Completion" project described in . Issues created in this epic must be linked back to the relevant user stories that they solve. The intent of this issue is to bring together the project into a single issue covering most of the functionality and submit for integration.
| Unsolvable | 1.summary: Create a base class for fetching a users activity completion details
description: We need a base class, as well as a sample implementation for an activity, for fetching a users activity completion details. The code should be accompanied by relevant unit tests.
2.summary: Create a base class for fetching an activitys dates that are relevant for a given user
description: We need a base class, as well as a sample implementation for an activity, for fetching an activitys dates that are relevant for a given user. The code should be accompanied by relevant unit tests.
3.summary: Create an output component that displays an activitys information for a user
description: We need an output component that displays an activitys information for a user (completion info and activity dates). To do so, we need: Output component function Output component renderer Output component renderable Convert course/completion.js into AMD Templates Activity information which imports templates for Activity dates Completion details Sample implementation for an activity Unit tests Behat tests
4.summary: Implement the activity dates functionality for each activity and output them in view.php
description: We need to implement the activity dates functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: -assign- --> deferred to -assignment- -book- -chat- -choice- data feedback -folder- forum -glossary- -pactivity- -imscp- -label- -lesson- --> deferred to -lti- -page- -quiz- --> deferred to -resource- scorm -survey- -url- -wiki- workshop
5.summary: Implement the activity dates functionality for each activity and output them in view.php - Part 2
description: We need to implement the activity dates functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: label lesson lti page quiz resource scorm survey - has been done on the part 1 issue. url wiki workshop
6.summary: Create a course setting for displaying activity completion conditions
description: . User story As a course creator/editing teacher I want to be able to configure the course to show completion requirements So that I can decide if I want the completion requirements to be shown . Acceptance criteria Given I log in as an editing teacher/course creator, when I am at a course s settings page, then I should see a setting that I can use to specify if I want the completion requirements to be shown in the course or not. Given completion requirements are set to be shown, when I go to a courses homepage, then I should see the completion requirements for the activities with automatic completion requirements. Given completion requirements are not set to be shown, when I go to a courses homepage, then I should not see the completion requirements for the activities with automatic completion requirements. Given completion requirements are set to be shown, when I view an activity with automatic completion requirements, then I should see the activitys completion requirements. Given completion requirements are not set to be shown, when I view an activity with automatic completion requirements, then I should not see the activitys completion requirements.
7.summary: Create a course setting for displaying activity dates
description: . User story As a course creator/editing teacher I want to be able to configure the course to show activity dates so that I can decide if I want the activity dates to be shown . Acceptance criteria Given I log in as an editing teacher/course creator, when I am at a course s settings page, then I should see a setting that I can use to specify if I want the activity dates to be shown in the course or not. Given activity dates are set to be shown, when I go to a courses homepage, then I should see the dates for the activities in the course. Given activity dates are not set to be shown, when I go to a courses homepage, then I should not see the dates for the activities in the course. Given activity dates are set to be shown, when I view an activity with dates set, then those dates should be displayed on the activitys view page. Given activity dates are not set to be shown, when I view an activity with dates set, then those dates should not be displayed on the activitys view page.
8.summary: Rework manual completion on the course page
description: In line with the prototype| we need rework manual completion on the course page. !new_manual_completion_buttons.png|thumbnail! Things that need to be done: Remove the manual completion checkboxes. Replace these with "Mark as done"/"Done" buttons. Remove the M.core_completion.init YUI module in course/completion.js and replace it with an AMD module written on ES6.
9.summary: Create an admin setting for the default value for displaying the automatic activity completion requirements in the course settings form
description: . User story As a site administrator I want to be able to set the default value for displaying activity completion requirements in the course settings form So that course creators or editing teachers wont have to set its value in each course on course creation . Acceptance criteria When I am at the course default settings page, I should see a setting that I can use to set the default value for displaying the automatic completion requirements in the course settings form This admin setting should be set to "Yes" by default When I am creating a course with automatic completion, then the default value for the "Show completion conditions" course setting field should match the selected site default.
10.summary: Create an admin setting for the default value for displaying the activity dates in the course settings form
description: . User story As a site administrator I want to be able to set the default value for displaying activity dates in the course settings form So that course creators or editing teachers wont have to set its value in each course on course creation . Acceptance criteria When I am at the course default settings page, I should see a setting that I can use to set the default value for displaying activity dates in the course settings form This admin setting should be set to "Yes" by default for new courses, but default to "No" for existing courses when sites are upgraded (since it is new information that was not previously being displayed in courses). When I am creating a course with automatic completion, then the default value for the "Show activity dates" course setting field should match the selected site default.
11.summary: Implement the completion details functionality for each activity plugins output them in view.php - Part 2
description: We need to implement the completion details functionality for each activity not implemented by , and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: label lesson lti page quiz resource scorm -survey- - has been done on the part 1 issue. url wiki workshop
12.summary: Implement the completion details functionality for each activity plugins output them in view.php - Part 1
description: We need to implement the completion details functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: assign assignment(?) book chat choice data feedback folder forum glossary pactivity imscp survey The remainder of activities will have this implemented in .
13.summary: Update the course homepage to display the activity information
description: We need to update the course homepage to display the activity information. We should include relevant behat tests.
14.summary: Display the activity information output component on the activity modules view.php
description: Go through the view.php page of each activity module and display the activity information output component. Typical procedure: Find the heading for the view page (e.g. $OUTPUT->heading()). Add the activity information below the heading. e.g. noformat$OUTPUT->activity_information($cm);noformat Make sure that $cm is an instance of cm_info (You can also use cm_info::create())
15.summary: Deprecate the _get_completion_state() callbacks
description: With the activity_custom_completion base class being implemented by activity modules supporting custom completion rules, it is time to deprecate these callbacks as they wont be used anymore. A possible approach to do the deprecation: Add a debugging message that these callbacks are now being deprecated in completion_info::internal_get_state()| Move these callbacks to the plugins deprecatedlib.php. E.g. in assign, move to mod/assign/deprecatedlib.php. Make sure that deprecatedlib.php is included in the plugins lib.php Add the related PHPDoc block tags (e.g. to the _get_completion_state() callbacks. Note the deprecation of these callbacks in upgrade.txt
16.summary: Remove duplicate activity dates
description: As part of we show activity dates information on top of all activity main pages (view.php). Some activity modules were already showing date information on that page so now on some activities we have duplicate information on that page. We should delete the duplicate information.
17.summary: Define sort ordering for completion conditions
description: At the moment, completion conditions are being displayed in the following order: View Receive a grade Custom completion conditions For activities with no custom completion conditions, this is fine, as "view" will always be achieved before "receive a grade". However there are some cases where an activity with custom completion with have some/all of those conditions met before receiving a grade. To make it clearer to the user, it would make sense to order the conditions in the UI so that they are (as best as possible) listed in the order they would usually be completed in. For example, in the assignment activity: View Submit assignment Receive a grade would make more sense than: View Receive a grade Submit assignment Therefore we should require custom completion conditions to define their completion sort order, including both custom conditions AND the core completion conditions of "View" and "Receive a grade".
18.summary: Create user tours for the activity information output component
description: We need to create user tours for the activity output component. Some considerations regarding the tours behaviour: It needs to show appropriate information depending on the activitys settings: Whether activity dates are shown or not. Whether completion information is displayed and whether the activity tracks completions automatically or manually. Do we show in both course homepage and activity view?
19.summary: Review and update existing web services to return the new fields and exported information from activities
description: For the new MUA Project: Improve Student Activity Completion, new fields are being created in the database and new information is being returned. Existing Web Services have to be reviewed to ensure that this new information is returned for external clients such as the Moodle app to consume. dpalou is listing everything that is missing so far, we will provide a detailed document soon.
20.summary: Avoid showing the Mark as done button on the course page
description: Based on feedback from the MUA (as mentioned in a comment in ) and in the discussion Re: Student activity completion in Moodle 3.11| when completion conditions are not shown on the course page, it would be best if the Mark as done button is also not shown. The activity page is the natural place to mark an activity as done, and not showing it on the course page would mean that students cant mark activities as complete without even looking at them. That said, there are a few edge cases where it will not be possible to mark activities as done on the activity/resource page, namely: File resource set to force download, open, in pop-up, new window URL set to display open, in pop-up, new window Label I think it would be a shame though to show the Mark as done button for all activities on the course page just because of these few edge cases. Possible solutions are: Only show the Mark as done button on the course page for Label, File and URL resources. Only show the Mark as done button on the course page for Label and when File or URL are set to force download/open/in pop-up/new window. ---- Edited to add steps to reproduce: Create a course with Enable completion tracking set to Yes and Show completion conditions set to No. Add some activities and resources to the course with completion tracking set to Students can manually mark the activity as completed. Add some activities and resources to the course with completion tracking set to Show activity as complete when conditions are met. View the course page. Expected result: Activity completion conditions are not shown on the course page. Actual result: Automatic completion conditions are not shown, but a Mark as done button is shown for activities and resources with manual completion.
21.summary: Activity completion fallback for third party plugins
description: In , we show badges to indicate if an activity is completed or not. We also show the list of actions a user should perform for an activity with auto-completion to be marked as completed. The third-party plugins that are not implemented the new completion details functionality, do not show any indications about if they are completed or not. We should somehow take care of them. A proposal is to display some generic label that reflects the activity has completion conditions and indicate when they have been completed. Maybe something like: "To do: complete" "Done: completed"
22.summary: Implement the activity dates functionality for mod_chat and output them in view.php
description: Following , we need to implement the activity dates functionality for the chat module as well.
23.summary: Failures with behat and classic on LTI completion scenarios
description: Since some hours ago we are getting consistent failures with the feature / scenario: code View activity completion information in the LTI activity / Use manual completion code Only with classic, but consistently. Link: (ignore the other error) code --- Failed steps: 001 Scenario: Use manual completion /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:63 And I navigate to "Edit settings" in current page administration /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:67 Xpath matching locator "//sectioncontains( not found. (Behat\Mink\Exception\ElementNotFoundException) code Looking to the code, this scenario was added by , so assuming its a regressions there. Ciao :-)
24.summary: Display the activity information in activity view page only when theres something to display
description: Looking into , I realised that there should be no need to display the activity information output component on activities that dont display completion information and activity dates. On the current implementation where its always displayed, this also causes the horizontal line separator for the activity information to be displayed which does not serve much purpose when theres no information to present. So we should conditionally display the activity information output component only when necessary.
25.summary: Implement the activity dates functionality for activities that support overrides
description: Following the discussion on , the implementation of activity dates functionality for the activities that can have user/group overrides have been moved into this issue.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: MUA Project: Improve Student Activity Completion
description: This epic covers deliverable elements of the MUA "Improve Student Activity Completion" project described in . Issues created in this epic must be linked back to the relevant user stories that they solve. The intent of this issue is to bring together the project into a single issue covering most of the functionality and submit for integration.
### Response:
1.summary: Create a base class for fetching a users activity completion details
description: We need a base class, as well as a sample implementation for an activity, for fetching a users activity completion details. The code should be accompanied by relevant unit tests.
2.summary: Create a base class for fetching an activitys dates that are relevant for a given user
description: We need a base class, as well as a sample implementation for an activity, for fetching an activitys dates that are relevant for a given user. The code should be accompanied by relevant unit tests.
3.summary: Create an output component that displays an activitys information for a user
description: We need an output component that displays an activitys information for a user (completion info and activity dates). To do so, we need: Output component function Output component renderer Output component renderable Convert course/completion.js into AMD Templates Activity information which imports templates for Activity dates Completion details Sample implementation for an activity Unit tests Behat tests
4.summary: Implement the activity dates functionality for each activity and output them in view.php
description: We need to implement the activity dates functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: -assign- --> deferred to -assignment- -book- -chat- -choice- data feedback -folder- forum -glossary- -pactivity- -imscp- -label- -lesson- --> deferred to -lti- -page- -quiz- --> deferred to -resource- scorm -survey- -url- -wiki- workshop
5.summary: Implement the activity dates functionality for each activity and output them in view.php - Part 2
description: We need to implement the activity dates functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: label lesson lti page quiz resource scorm survey - has been done on the part 1 issue. url wiki workshop
6.summary: Create a course setting for displaying activity completion conditions
description: . User story As a course creator/editing teacher I want to be able to configure the course to show completion requirements So that I can decide if I want the completion requirements to be shown . Acceptance criteria Given I log in as an editing teacher/course creator, when I am at a course s settings page, then I should see a setting that I can use to specify if I want the completion requirements to be shown in the course or not. Given completion requirements are set to be shown, when I go to a courses homepage, then I should see the completion requirements for the activities with automatic completion requirements. Given completion requirements are not set to be shown, when I go to a courses homepage, then I should not see the completion requirements for the activities with automatic completion requirements. Given completion requirements are set to be shown, when I view an activity with automatic completion requirements, then I should see the activitys completion requirements. Given completion requirements are not set to be shown, when I view an activity with automatic completion requirements, then I should not see the activitys completion requirements.
7.summary: Create a course setting for displaying activity dates
description: . User story As a course creator/editing teacher I want to be able to configure the course to show activity dates so that I can decide if I want the activity dates to be shown . Acceptance criteria Given I log in as an editing teacher/course creator, when I am at a course s settings page, then I should see a setting that I can use to specify if I want the activity dates to be shown in the course or not. Given activity dates are set to be shown, when I go to a courses homepage, then I should see the dates for the activities in the course. Given activity dates are not set to be shown, when I go to a courses homepage, then I should not see the dates for the activities in the course. Given activity dates are set to be shown, when I view an activity with dates set, then those dates should be displayed on the activitys view page. Given activity dates are not set to be shown, when I view an activity with dates set, then those dates should not be displayed on the activitys view page.
8.summary: Rework manual completion on the course page
description: In line with the prototype| we need rework manual completion on the course page. !new_manual_completion_buttons.png|thumbnail! Things that need to be done: Remove the manual completion checkboxes. Replace these with "Mark as done"/"Done" buttons. Remove the M.core_completion.init YUI module in course/completion.js and replace it with an AMD module written on ES6.
9.summary: Create an admin setting for the default value for displaying the automatic activity completion requirements in the course settings form
description: . User story As a site administrator I want to be able to set the default value for displaying activity completion requirements in the course settings form So that course creators or editing teachers wont have to set its value in each course on course creation . Acceptance criteria When I am at the course default settings page, I should see a setting that I can use to set the default value for displaying the automatic completion requirements in the course settings form This admin setting should be set to "Yes" by default When I am creating a course with automatic completion, then the default value for the "Show completion conditions" course setting field should match the selected site default.
10.summary: Create an admin setting for the default value for displaying the activity dates in the course settings form
description: . User story As a site administrator I want to be able to set the default value for displaying activity dates in the course settings form So that course creators or editing teachers wont have to set its value in each course on course creation . Acceptance criteria When I am at the course default settings page, I should see a setting that I can use to set the default value for displaying activity dates in the course settings form This admin setting should be set to "Yes" by default for new courses, but default to "No" for existing courses when sites are upgraded (since it is new information that was not previously being displayed in courses). When I am creating a course with automatic completion, then the default value for the "Show activity dates" course setting field should match the selected site default.
11.summary: Implement the completion details functionality for each activity plugins output them in view.php - Part 2
description: We need to implement the completion details functionality for each activity not implemented by , and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: label lesson lti page quiz resource scorm -survey- - has been done on the part 1 issue. url wiki workshop
12.summary: Implement the completion details functionality for each activity plugins output them in view.php - Part 1
description: We need to implement the completion details functionality for each activity and output them in view.php. The code should be accompanied by unit and behat tests. This issue relates to implementation in the following activities: assign assignment(?) book chat choice data feedback folder forum glossary pactivity imscp survey The remainder of activities will have this implemented in .
13.summary: Update the course homepage to display the activity information
description: We need to update the course homepage to display the activity information. We should include relevant behat tests.
14.summary: Display the activity information output component on the activity modules view.php
description: Go through the view.php page of each activity module and display the activity information output component. Typical procedure: Find the heading for the view page (e.g. $OUTPUT->heading()). Add the activity information below the heading. e.g. noformat$OUTPUT->activity_information($cm);noformat Make sure that $cm is an instance of cm_info (You can also use cm_info::create())
15.summary: Deprecate the _get_completion_state() callbacks
description: With the activity_custom_completion base class being implemented by activity modules supporting custom completion rules, it is time to deprecate these callbacks as they wont be used anymore. A possible approach to do the deprecation: Add a debugging message that these callbacks are now being deprecated in completion_info::internal_get_state()| Move these callbacks to the plugins deprecatedlib.php. E.g. in assign, move to mod/assign/deprecatedlib.php. Make sure that deprecatedlib.php is included in the plugins lib.php Add the related PHPDoc block tags (e.g. to the _get_completion_state() callbacks. Note the deprecation of these callbacks in upgrade.txt
16.summary: Remove duplicate activity dates
description: As part of we show activity dates information on top of all activity main pages (view.php). Some activity modules were already showing date information on that page so now on some activities we have duplicate information on that page. We should delete the duplicate information.
17.summary: Define sort ordering for completion conditions
description: At the moment, completion conditions are being displayed in the following order: View Receive a grade Custom completion conditions For activities with no custom completion conditions, this is fine, as "view" will always be achieved before "receive a grade". However there are some cases where an activity with custom completion with have some/all of those conditions met before receiving a grade. To make it clearer to the user, it would make sense to order the conditions in the UI so that they are (as best as possible) listed in the order they would usually be completed in. For example, in the assignment activity: View Submit assignment Receive a grade would make more sense than: View Receive a grade Submit assignment Therefore we should require custom completion conditions to define their completion sort order, including both custom conditions AND the core completion conditions of "View" and "Receive a grade".
18.summary: Create user tours for the activity information output component
description: We need to create user tours for the activity output component. Some considerations regarding the tours behaviour: It needs to show appropriate information depending on the activitys settings: Whether activity dates are shown or not. Whether completion information is displayed and whether the activity tracks completions automatically or manually. Do we show in both course homepage and activity view?
19.summary: Review and update existing web services to return the new fields and exported information from activities
description: For the new MUA Project: Improve Student Activity Completion, new fields are being created in the database and new information is being returned. Existing Web Services have to be reviewed to ensure that this new information is returned for external clients such as the Moodle app to consume. dpalou is listing everything that is missing so far, we will provide a detailed document soon.
20.summary: Avoid showing the Mark as done button on the course page
description: Based on feedback from the MUA (as mentioned in a comment in ) and in the discussion Re: Student activity completion in Moodle 3.11| when completion conditions are not shown on the course page, it would be best if the Mark as done button is also not shown. The activity page is the natural place to mark an activity as done, and not showing it on the course page would mean that students cant mark activities as complete without even looking at them. That said, there are a few edge cases where it will not be possible to mark activities as done on the activity/resource page, namely: File resource set to force download, open, in pop-up, new window URL set to display open, in pop-up, new window Label I think it would be a shame though to show the Mark as done button for all activities on the course page just because of these few edge cases. Possible solutions are: Only show the Mark as done button on the course page for Label, File and URL resources. Only show the Mark as done button on the course page for Label and when File or URL are set to force download/open/in pop-up/new window. ---- Edited to add steps to reproduce: Create a course with Enable completion tracking set to Yes and Show completion conditions set to No. Add some activities and resources to the course with completion tracking set to Students can manually mark the activity as completed. Add some activities and resources to the course with completion tracking set to Show activity as complete when conditions are met. View the course page. Expected result: Activity completion conditions are not shown on the course page. Actual result: Automatic completion conditions are not shown, but a Mark as done button is shown for activities and resources with manual completion.
21.summary: Activity completion fallback for third party plugins
description: In , we show badges to indicate if an activity is completed or not. We also show the list of actions a user should perform for an activity with auto-completion to be marked as completed. The third-party plugins that are not implemented the new completion details functionality, do not show any indications about if they are completed or not. We should somehow take care of them. A proposal is to display some generic label that reflects the activity has completion conditions and indicate when they have been completed. Maybe something like: "To do: complete" "Done: completed"
22.summary: Implement the activity dates functionality for mod_chat and output them in view.php
description: Following , we need to implement the activity dates functionality for the chat module as well.
23.summary: Failures with behat and classic on LTI completion scenarios
description: Since some hours ago we are getting consistent failures with the feature / scenario: code View activity completion information in the LTI activity / Use manual completion code Only with classic, but consistently. Link: (ignore the other error) code --- Failed steps: 001 Scenario: Use manual completion /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:63 And I navigate to "Edit settings" in current page administration /var/www/html/mod/lti/tests/behat/lti_activity_completion.feature:67 Xpath matching locator "//sectioncontains( not found. (Behat\Mink\Exception\ElementNotFoundException) code Looking to the code, this scenario was added by , so assuming its a regressions there. Ciao :-)
24.summary: Display the activity information in activity view page only when theres something to display
description: Looking into , I realised that there should be no need to display the activity information output component on activities that dont display completion information and activity dates. On the current implementation where its always displayed, this also causes the horizontal line separator for the activity information to be displayed which does not serve much purpose when theres no information to present. So we should conditionally display the activity information output component only when necessary.
25.summary: Implement the activity dates functionality for activities that support overrides
description: Following the discussion on , the implementation of activity dates functionality for the activities that can have user/group overrides have been moved into this issue.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: atto_media follow up issues
description: Summary of work remaining on atto_media plugin: It becomes unusable on boost Behat Use data attributes instead of classes to identify video/audio/link (low priority) The last source/track element cannot be removed Validation on some fields (e.g., let the user know that only vtt files can be accepted for tracks)
| Unsolvable | 1.summary: Behat tests for atto_media
description: Write behat tests for the new plugin
2.summary: Atto media plugin UI/UX improvements
description: When adding multiple sources or tracks, the final one cannot be removed (the only action is to add more). This isnt so much a problem when inserting new media; but when editing existing media it could be confusing. The workaround is simply to clear the field, but its not clear to a user that you would need to do that. The UI needs some tweaking also, as per discussion with Alberto (unfortunately the changes to be made are on pieces of paper so its hard to add them here).
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: atto_media follow up issues
description: Summary of work remaining on atto_media plugin: It becomes unusable on boost Behat Use data attributes instead of classes to identify video/audio/link (low priority) The last source/track element cannot be removed Validation on some fields (e.g., let the user know that only vtt files can be accepted for tracks)
### Response:
1.summary: Behat tests for atto_media
description: Write behat tests for the new plugin
2.summary: Atto media plugin UI/UX improvements
description: When adding multiple sources or tracks, the final one cannot be removed (the only action is to add more). This isnt so much a problem when inserting new media; but when editing existing media it could be confusing. The workaround is simply to clear the field, but its not clear to a user that you would need to do that. The UI needs some tweaking also, as per discussion with Alberto (unfortunately the changes to be made are on pieces of paper so its hard to add them here).
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic Book has no behat tests
description: Book needs behat test coverage, should be quite simple to automate a few QAs for book
| Unsolvable | 1.summary: Automate - A teacher can show and hide book chapters and subchapters
description: As described in , a teacher can show and hide book chapters and subchapters
2.summary: CLONE - Automate An admin can generate and view all the book log entries
description: Automate An admin can generate and view all the book log entries
3.summary: Automate MDLQA 2423 - A teacher can create book chapters and subchapters
description: Book needs behat test coverage, should be quite simple to automate a few QAs for book
4.summary: Automate - A teacher can reorganize book chapters and subchapters
description: Automate - A teacher can reorganize book chapters and subchapters
5.summary: Automate - As teacher test book navigation options
description: As described in , a teacher can set different navigation options for a book.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic Book has no behat tests
description: Book needs behat test coverage, should be quite simple to automate a few QAs for book
### Response:
1.summary: Automate - A teacher can show and hide book chapters and subchapters
description: As described in , a teacher can show and hide book chapters and subchapters
2.summary: CLONE - Automate An admin can generate and view all the book log entries
description: Automate An admin can generate and view all the book log entries
3.summary: Automate MDLQA 2423 - A teacher can create book chapters and subchapters
description: Book needs behat test coverage, should be quite simple to automate a few QAs for book
4.summary: Automate - A teacher can reorganize book chapters and subchapters
description: Automate - A teacher can reorganize book chapters and subchapters
5.summary: Automate - As teacher test book navigation options
description: As described in , a teacher can set different navigation options for a book.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Users should be able to create profiles
description: Users should be able to create profiles that include an avatar, description, tagging, and other things we deem necessary (and they ask for!)
| Solvable | 1.summary: Move interface language selector to settings
description: The user interface selector should be moved to user settings.
2.summary: Create endpoint for unique usernames
description: We need an endpoint to enable users to create a unique username in MoodleNets frontend UI.
3.summary: Create endpoint for user-configurable header images in profiles
description: Users need to be able to enter a URL so that they can update the default header image. (Eventually this will also include the ability to upload their own header image, but this is out of scope for v0.9.4.)
4.summary: Implement forgot password flow
description: Details: The link to reset a users password should be in Settings
5.summary: Create endpoint for link in user profiles
description: Users should be able to enter a single link in their profiles to point to, for example, their home page.
6.summary: Option to add links on user profile, and in community/collection metadata
description: This should be stored and federate using the actors attachment field to be compatible with Mastodon and co:
7.summary: Endpoint to send an email invite to someone to join MoodleNet
description: Receive email address through GraphQL endpoint Add email address to invite-only white-list Send transactional email invite Return success or error message to user
8.summary: User can change password
description: User can change password: via Edit profile via Forgot password
9.summary: User can change profile header image
description: User can change profile header image
10.summary: Edit profile
description: Edit profile
11.summary: Create link field in user profile
description: Link should be a field that can be completed with a link to a website of the users choosing. (this is called "website" on the GraphQL end)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Users should be able to create profiles
description: Users should be able to create profiles that include an avatar, description, tagging, and other things we deem necessary (and they ask for!)
### Response:
1.summary: Move interface language selector to settings
description: The user interface selector should be moved to user settings.
2.summary: Create endpoint for unique usernames
description: We need an endpoint to enable users to create a unique username in MoodleNets frontend UI.
3.summary: Create endpoint for user-configurable header images in profiles
description: Users need to be able to enter a URL so that they can update the default header image. (Eventually this will also include the ability to upload their own header image, but this is out of scope for v0.9.4.)
4.summary: Implement forgot password flow
description: Details: The link to reset a users password should be in Settings
5.summary: Create endpoint for link in user profiles
description: Users should be able to enter a single link in their profiles to point to, for example, their home page.
6.summary: Option to add links on user profile, and in community/collection metadata
description: This should be stored and federate using the actors attachment field to be compatible with Mastodon and co:
7.summary: Endpoint to send an email invite to someone to join MoodleNet
description: Receive email address through GraphQL endpoint Add email address to invite-only white-list Send transactional email invite Return success or error message to user
8.summary: User can change password
description: User can change password: via Edit profile via Forgot password
9.summary: User can change profile header image
description: User can change profile header image
10.summary: Edit profile
description: Edit profile
11.summary: Create link field in user profile
description: Link should be a field that can be completed with a link to a website of the users choosing. (this is called "website" on the GraphQL end)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Introduce multiple calendar support in Moodle
description: See linked tasks.
| Unsolvable | 1.summary: Displaying and selecting dates throughout Moodle should allow the use of multiple calendars
description: I implemented a patch to add the capability of working with other calendar systems than just Gregorian. Ill provide the instructions to apply the patch in following post
2.summary: The calendar itself should display dates depending on the calendar type used
description: With the introduction of we need the calendar to display the dates in the format defined by the calendar type being used, not just Gregorian.
3.summary: Add the ability to format the years in the new calendar plugin.
description: Currently the calendar plugin only takes a starting year and ending year as information for creating the select box. Im trying to create a Japanese calendar type, and years dont run in this fashion. Additional information also needs to be added about which emperor was ruling during that year. I propose a new method get_years(), which works in the same fashion as get_days() and get_months(). I have also now included the code to change the order of the select boxes used for selecting the date as well.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Introduce multiple calendar support in Moodle
description: See linked tasks.
### Response:
1.summary: Displaying and selecting dates throughout Moodle should allow the use of multiple calendars
description: I implemented a patch to add the capability of working with other calendar systems than just Gregorian. Ill provide the instructions to apply the patch in following post
2.summary: The calendar itself should display dates depending on the calendar type used
description: With the introduction of we need the calendar to display the dates in the format defined by the calendar type being used, not just Gregorian.
3.summary: Add the ability to format the years in the new calendar plugin.
description: Currently the calendar plugin only takes a starting year and ending year as information for creating the select box. Im trying to create a Japanese calendar type, and years dont run in this fashion. Additional information also needs to be added about which emperor was ruling during that year. I propose a new method get_years(), which works in the same fashion as get_days() and get_months(). I have also now included the code to change the order of the select boxes used for selecting the date as well.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: META: Follow up issues with new course management interface
description: Just a few quick thoughts on things to address for 2.6
| Unsolvable | 1.summary: Course management drag and drop needs to work with the keyboard
description: The course category managemenent interface supports drag+drop of course to resort and move them between categories. Really this need to be made more accessible. Moving to the core drag-drop module is likely the best solution.
2.summary: Add button to quickly add a course in new course management interface
description: Previously on the course management page there were two buttons: one to add a new category and another to add a new course. When adding a new course, the default category was implied and users could select another category if one existed. The new interface requires users to first select a category, then to add a course within the category. This is an extra step, but perhaps more than that, it is a conceptual leap for users who are not using Moodle with categories (and I suspect there are lots of those). As well as that, there is a link to "Create new" under course categories and I suspect user of the old interface, where they had been able to add a new course, might find this confusing. I propose that the "Create new" link under categories be labelled more specifically as "Create new category" to avoid confusion. I also recommend one of the following two options. Showing the default category initially when a user first arrives at the management page, or Adding a "Create new course" link/button somewhere on the initial screen.
3.summary: Expand all on Manage courses and categories page
description: As far as I can see the new layout doesnt have the facility to show the entire structure of the site i.e. categories and courses. Each category must be clicked individually to reveal its contents. This is laborious. Suggestion: implement Expand all functionality on category listings.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: META: Follow up issues with new course management interface
description: Just a few quick thoughts on things to address for 2.6
### Response:
1.summary: Course management drag and drop needs to work with the keyboard
description: The course category managemenent interface supports drag+drop of course to resort and move them between categories. Really this need to be made more accessible. Moving to the core drag-drop module is likely the best solution.
2.summary: Add button to quickly add a course in new course management interface
description: Previously on the course management page there were two buttons: one to add a new category and another to add a new course. When adding a new course, the default category was implied and users could select another category if one existed. The new interface requires users to first select a category, then to add a course within the category. This is an extra step, but perhaps more than that, it is a conceptual leap for users who are not using Moodle with categories (and I suspect there are lots of those). As well as that, there is a link to "Create new" under course categories and I suspect user of the old interface, where they had been able to add a new course, might find this confusing. I propose that the "Create new" link under categories be labelled more specifically as "Create new category" to avoid confusion. I also recommend one of the following two options. Showing the default category initially when a user first arrives at the management page, or Adding a "Create new course" link/button somewhere on the initial screen.
3.summary: Expand all on Manage courses and categories page
description: As far as I can see the new layout doesnt have the facility to show the entire structure of the site i.e. categories and courses. Each category must be clicked individually to reveal its contents. This is laborious. Suggestion: implement Expand all functionality on category listings.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: User stories for SCSS Compilation improvements
description: A collection of the user stories and acceptance criterion to improve performance of SCSS generation. Acceptance criterion should include: RTL generation having the same benefits. Please note, these user stories arent really user stories in the true sense because SCSS compilation is not a user feature, nor something that ordinary users actually work with. Were using these as a guidance and to help define our set of requirements
| Unsolvable | 1.summary: As a hosting provider, I want to reset local cache without causing CPU spikes
description: As a hosting provider, I want to reset local cache without causing CPU spikes, in order to scale up and down
2.summary: As a user, I want to interact with the page, before CSS is fully ready
description: As a user, I want to interact with the page, before CSS is fully ready: After upgrades After theme setting changes After cache purges
3.summary: As a theme designer, I want a fast change test iterate loop in order to dev things quickly
description: As a theme designer I want a fast change test iterate loop in order to dev things quickly
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: User stories for SCSS Compilation improvements
description: A collection of the user stories and acceptance criterion to improve performance of SCSS generation. Acceptance criterion should include: RTL generation having the same benefits. Please note, these user stories arent really user stories in the true sense because SCSS compilation is not a user feature, nor something that ordinary users actually work with. Were using these as a guidance and to help define our set of requirements
### Response:
1.summary: As a hosting provider, I want to reset local cache without causing CPU spikes
description: As a hosting provider, I want to reset local cache without causing CPU spikes, in order to scale up and down
2.summary: As a user, I want to interact with the page, before CSS is fully ready
description: As a user, I want to interact with the page, before CSS is fully ready: After upgrades After theme setting changes After cache purges
3.summary: As a theme designer, I want a fast change test iterate loop in order to dev things quickly
description: As a theme designer I want a fast change test iterate loop in order to dev things quickly
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Messaging phase 2 - Expand Matrix integration
description: . Background This is the second phase of reviewing and improving the messaging, notifications and chat functionality in Moodle LMS. This phase aims to continue and expand and improve the Matrix ( integration work which commenced in the Phase 1 epic (). This epic relates to Moodle 4.3 and is still a work in progress, so additional features, improvements and user stories will be added as research and planning continues. . Research The parent issue for this epic contains al large amount of the initial research and investigation. Additional resources will be added once further research has been completed and compiled. . User Stories . Student As a student I want to be able to join the matrix chat for my groups in a course from the main course page in Moodle. So I can communicate with the peers in my course and ask my teacher questions. . Teacher As a teacher I want to be able to join the matrix chat for my groups in a course from the main course page in Moodle. So I can communicate with students in my groups. As a teacher when the group mode for my course is separate groups and the group mode for the course is forced , I want multiple rooms in Matrix created for my course, one for each group that has been created in Moodle and I want to be added to each Matrix room. So that my students only communicate with those that they share a group with. . Admin As an admin I want to be able to control which Matrix contact methods are displayed on a users profile page, as this is dependent on the enabled features of my organisations Matrix homeserver. So my users know how they can communicate. As an admin I want a visual indication of if the configured chat plugin can successfully communicate with the configured external service. So I can easily tell if the entered details are valid and the server is reachable.
| Unsolvable | 1.summary: Update Communication/Matrix language strings to latest approved copy
description: A UX review was undertaken on strings introduced during the Communication/Matrix work and some improvements have been suggested and discussed. Below is the final list of changes which we need to make relating to the communication subsysytem and matrix provider: ||String name||New string text||Notes (explanation / other related changes)|| |enablecommunicationsubsystem|Enable communication providers| Replaces reference to "subsystem" with "providers", for naming consistency and to remove dev terminology.| |enablecommunicationsubsystem_desc|Allow integration with communication providers such as Matrix so teachers and students can communicate more easily. You can manage these integrations in Plugins.| The word "Plugins" needs to be hyperlinked to the communications plugins page.| |coursecommunication_desc|The default communication service for new courses. Existing courses will not have any provider selected by default.| Updated wording.| |communicationroomready|Your \$a room is ready.| Remove the exclamation mark and replace it with a full stop.| |matrixuserid_desc|Delete this string and references to it.| Description not needed, does not provide any more info than the field name.| |matrixhomeserverurl|Homeserver URL| Change Homeserver to one word, consistent with how Matrix use it| |matrixaccesstoken_desc|Access token for the account which will perform actions on the homeserver.| Polishing to clarify token usage.| |matrixelementurl_desc|Delete this string and references to it.| Description not needed, name of the field is self-explanatory.| |privacy:metadata|The Matrix communication plugin does not store any personal data.| Add "The" to the beginning of the existing string for consistency.| |communicationroomname_help|If the field is left blank, the course name is used as the room name.| This is also currently buried in the help popover, with this simplified version we should move it out to be visible on the page (check for how this was achieved for customlinkurlinfo, its the same format). The string name will also need to be updated to communicationroomnameinfo since it wont be in the help popover.| |seleccommunicationprovider|Provider| "Provider" is more consistent wording than "service", and we dont need to mention "communication", because its in the heading of the page. There is also a missing t typo in the string name which we need to fix, it should be selectcommunicationprovider.| |seleccommunicationprovider_help|_(No changes to string)_| Same typo needs fixing as above, the string name should be selectcommunicationprovider_help| Be sure to check for any uses of the strings in behat tests that may need updating, also the couple of string name changes will need to be updated wherever theyre referenced in the code as well. . Out of scope Any changes to reflect the differences where groups mode is enabled/disabled. For example, this could technically mean rooms (plural) are created instead of rooms (singular), and that room name is actually used for the space name. These increase explanation complexity, and the subtleties should be intuitive/clear enough for a teacher as soon as they visit their Matrix client. We can always revisit with a follow up in future if evidence/user feedback indicates updates/clarifications are necessary. Changes to referencing room(s) to support other nomenclature (eg Slack "channels"). This is non-trivial and will be investigated as a separate piece of work if/when the need arises.
2.summary: Allow versioned APIs for clients in Matrix provider
description: The Matrix MVP implements the a variety of API endpoint versions from both matrix and synapse, however Matrix has a comprehensive client/server version support pattern which we need to be aware of for future planning. In short, a Matrix API is comprised of a set of Matrix endpoints of various versions. The Specification for Matrix defines which endpoints (and versions) must be defined, and the server must implement a well-known URL which declares which versions of the API is does support. As a Matrix Client, Moodle needs to query the server to determine which versions that server supports, and therefore which APIs it implements. This issue seeks to: compartmentalise the various Matrix endpoints add that handshake to determine the supported versions simplify the creation of a new client version simplify the instance creation of a client Described here: color Some useful resources:
3.summary: Move course level Communication settings into their own page
description: Currently, setting up Communication providers such as Matrix in a course happens within the course settings. This is incredibly limiting, contributes to the growing list of settings during course setup, and also means checking if room name etc need updating in Matrix if that page is saved. As more functionality is added, this will be exacerbated and will make future features and improvements more challenging or tedious (for example, how to display more complex choices as the number of different providers grows, unnecessary room creation during course setup because participants/groups modes are not yet established at that point). It therefore makes sense to move settings related to the Communication subsystem into their own page. . Requirements Move the existing Communication / Matrix settings from the course settings page into a new page. The current requirement is to just reuse the same Moodle form elements and progressive disclosure implemented in the current course settings version. Link to the new page from the courses "More" menu. Check for and address any impact on course defaults, if there are any that are affected by the move. We need to liaise with Robbie to confirm if there are any other UX requirements or changes to move the existing content across.
4.summary: Allow teachers, managers and admins to moderate their courses Matrix rooms
description: We need a way to allow teachers to have elevated room permissions somehow. And similar cases. Every user in a room has a power level - a number generally between 0 and 100. The higher the number the more power the user has that room. By default, the creator of the room gets the highest power level of 100 (typically called Admin ), and newly joined users get a power level of 0. You can change the power level of less powerful users than yourself - for instance, an Admin (with power 100) could promote a normal user to a power level of 50 (typically called Moderator ). We want students and teachers to have different power levels in a room. We also want to explicitly set the power levels when creating the room. We want to be explicit because then rooms created by Moodle LMS will be predictable and behave as teachers and admins expect. If we dont set them explicitly a Matrix server may have some different defaults (like all users can kick), this could lead to unexpected behaviors. We should go with the defaults for user actions as outlined in the documentation ( but set them explicitly. Teachers and managers should get a power level 50 Students should get a power level of 0 Moodle site admins (if added to the room because the have a role in the course) should get a power level of 100 Power levels should updated based on Moodle LMS course role We should make a new capability that can be assigned to teacher and manager roles by default. The presence of this capability should be the thing that determines if they get a power level of 50 or not Docs: Out of scope At this stage power levels should not be configurable via the UI. We can add this in the future if users request it. But for now it feels like over-engineering and adding unneeded admin settings. At this stage we will only be supporting the default power levels mentioned above, we will not be implementing any admin settings to make them configurable.
5.summary: Add a custom link communication provider
description: Where institutions have existing communication platforms (eg Slack, Teams, Matrix) and are already maintaining rooms/channels for their classes within that platform, it would be convenient for teachers to be able to link to those as the communication method within their course, without the overhead of having to set up a full provider, or having the LMS performing any administration (room creation, access , permissions etc) that may conflict/overwrite any management already taking place. . Confirmed requirements Create a new communication provider. Add a provider specific field which allows a URL to be provided. This URL will be what is linked on the communication icon within the course. No administration/management functions (eg room membership, power levels, room name, avatar etc) will be performed by the subsystem/this provider. Any related required provider API methods that need to be implemented will perform no action. . TBC requirements Language strings and naming. Whether any changes are required to remove/reword the "room name" field which is part of the subsystem. This may be useful to retain so teachers can put a description of what theyve linked to which other teachers will see, but wont have any impact within the provider itself, since the room wont be created. Whether anything is required to avoid running tasks which will take no action. . FAQ Why not just make it possible to provide a room ID (or equivalent) within a specific provider such as Matrix? Initially, we were considering exactly this, however it introduces a few of unnecessary complexities: Where rooms are pre-existing, we still dont want room/user administration being completed by the LMS, so all of that administration functionality within the subsystem and providers would have to factor in "if room ID provided, do/do not do xyz". The fact that its essentially providing a link within the consistent communication UI, so there is no reason for it to be implemented or limited per provider since the behaviour will be consistent across the board. It avoids having to factor custom URL rules into providers.
6.summary: Create associated methods in matrix to check room availability/state
description: Matrix records are created when communication is enabled and the room configuration is saved in db. Create a new method to reliably check against the roomid or any associated data to check if the room created or available to use in course.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Messaging phase 2 - Expand Matrix integration
description: . Background This is the second phase of reviewing and improving the messaging, notifications and chat functionality in Moodle LMS. This phase aims to continue and expand and improve the Matrix ( integration work which commenced in the Phase 1 epic (). This epic relates to Moodle 4.3 and is still a work in progress, so additional features, improvements and user stories will be added as research and planning continues. . Research The parent issue for this epic contains al large amount of the initial research and investigation. Additional resources will be added once further research has been completed and compiled. . User Stories . Student As a student I want to be able to join the matrix chat for my groups in a course from the main course page in Moodle. So I can communicate with the peers in my course and ask my teacher questions. . Teacher As a teacher I want to be able to join the matrix chat for my groups in a course from the main course page in Moodle. So I can communicate with students in my groups. As a teacher when the group mode for my course is separate groups and the group mode for the course is forced , I want multiple rooms in Matrix created for my course, one for each group that has been created in Moodle and I want to be added to each Matrix room. So that my students only communicate with those that they share a group with. . Admin As an admin I want to be able to control which Matrix contact methods are displayed on a users profile page, as this is dependent on the enabled features of my organisations Matrix homeserver. So my users know how they can communicate. As an admin I want a visual indication of if the configured chat plugin can successfully communicate with the configured external service. So I can easily tell if the entered details are valid and the server is reachable.
### Response:
1.summary: Update Communication/Matrix language strings to latest approved copy
description: A UX review was undertaken on strings introduced during the Communication/Matrix work and some improvements have been suggested and discussed. Below is the final list of changes which we need to make relating to the communication subsysytem and matrix provider: ||String name||New string text||Notes (explanation / other related changes)|| |enablecommunicationsubsystem|Enable communication providers| Replaces reference to "subsystem" with "providers", for naming consistency and to remove dev terminology.| |enablecommunicationsubsystem_desc|Allow integration with communication providers such as Matrix so teachers and students can communicate more easily. You can manage these integrations in Plugins.| The word "Plugins" needs to be hyperlinked to the communications plugins page.| |coursecommunication_desc|The default communication service for new courses. Existing courses will not have any provider selected by default.| Updated wording.| |communicationroomready|Your \$a room is ready.| Remove the exclamation mark and replace it with a full stop.| |matrixuserid_desc|Delete this string and references to it.| Description not needed, does not provide any more info than the field name.| |matrixhomeserverurl|Homeserver URL| Change Homeserver to one word, consistent with how Matrix use it| |matrixaccesstoken_desc|Access token for the account which will perform actions on the homeserver.| Polishing to clarify token usage.| |matrixelementurl_desc|Delete this string and references to it.| Description not needed, name of the field is self-explanatory.| |privacy:metadata|The Matrix communication plugin does not store any personal data.| Add "The" to the beginning of the existing string for consistency.| |communicationroomname_help|If the field is left blank, the course name is used as the room name.| This is also currently buried in the help popover, with this simplified version we should move it out to be visible on the page (check for how this was achieved for customlinkurlinfo, its the same format). The string name will also need to be updated to communicationroomnameinfo since it wont be in the help popover.| |seleccommunicationprovider|Provider| "Provider" is more consistent wording than "service", and we dont need to mention "communication", because its in the heading of the page. There is also a missing t typo in the string name which we need to fix, it should be selectcommunicationprovider.| |seleccommunicationprovider_help|_(No changes to string)_| Same typo needs fixing as above, the string name should be selectcommunicationprovider_help| Be sure to check for any uses of the strings in behat tests that may need updating, also the couple of string name changes will need to be updated wherever theyre referenced in the code as well. . Out of scope Any changes to reflect the differences where groups mode is enabled/disabled. For example, this could technically mean rooms (plural) are created instead of rooms (singular), and that room name is actually used for the space name. These increase explanation complexity, and the subtleties should be intuitive/clear enough for a teacher as soon as they visit their Matrix client. We can always revisit with a follow up in future if evidence/user feedback indicates updates/clarifications are necessary. Changes to referencing room(s) to support other nomenclature (eg Slack "channels"). This is non-trivial and will be investigated as a separate piece of work if/when the need arises.
2.summary: Allow versioned APIs for clients in Matrix provider
description: The Matrix MVP implements the a variety of API endpoint versions from both matrix and synapse, however Matrix has a comprehensive client/server version support pattern which we need to be aware of for future planning. In short, a Matrix API is comprised of a set of Matrix endpoints of various versions. The Specification for Matrix defines which endpoints (and versions) must be defined, and the server must implement a well-known URL which declares which versions of the API is does support. As a Matrix Client, Moodle needs to query the server to determine which versions that server supports, and therefore which APIs it implements. This issue seeks to: compartmentalise the various Matrix endpoints add that handshake to determine the supported versions simplify the creation of a new client version simplify the instance creation of a client Described here: color Some useful resources:
3.summary: Move course level Communication settings into their own page
description: Currently, setting up Communication providers such as Matrix in a course happens within the course settings. This is incredibly limiting, contributes to the growing list of settings during course setup, and also means checking if room name etc need updating in Matrix if that page is saved. As more functionality is added, this will be exacerbated and will make future features and improvements more challenging or tedious (for example, how to display more complex choices as the number of different providers grows, unnecessary room creation during course setup because participants/groups modes are not yet established at that point). It therefore makes sense to move settings related to the Communication subsystem into their own page. . Requirements Move the existing Communication / Matrix settings from the course settings page into a new page. The current requirement is to just reuse the same Moodle form elements and progressive disclosure implemented in the current course settings version. Link to the new page from the courses "More" menu. Check for and address any impact on course defaults, if there are any that are affected by the move. We need to liaise with Robbie to confirm if there are any other UX requirements or changes to move the existing content across.
4.summary: Allow teachers, managers and admins to moderate their courses Matrix rooms
description: We need a way to allow teachers to have elevated room permissions somehow. And similar cases. Every user in a room has a power level - a number generally between 0 and 100. The higher the number the more power the user has that room. By default, the creator of the room gets the highest power level of 100 (typically called Admin ), and newly joined users get a power level of 0. You can change the power level of less powerful users than yourself - for instance, an Admin (with power 100) could promote a normal user to a power level of 50 (typically called Moderator ). We want students and teachers to have different power levels in a room. We also want to explicitly set the power levels when creating the room. We want to be explicit because then rooms created by Moodle LMS will be predictable and behave as teachers and admins expect. If we dont set them explicitly a Matrix server may have some different defaults (like all users can kick), this could lead to unexpected behaviors. We should go with the defaults for user actions as outlined in the documentation ( but set them explicitly. Teachers and managers should get a power level 50 Students should get a power level of 0 Moodle site admins (if added to the room because the have a role in the course) should get a power level of 100 Power levels should updated based on Moodle LMS course role We should make a new capability that can be assigned to teacher and manager roles by default. The presence of this capability should be the thing that determines if they get a power level of 50 or not Docs: Out of scope At this stage power levels should not be configurable via the UI. We can add this in the future if users request it. But for now it feels like over-engineering and adding unneeded admin settings. At this stage we will only be supporting the default power levels mentioned above, we will not be implementing any admin settings to make them configurable.
5.summary: Add a custom link communication provider
description: Where institutions have existing communication platforms (eg Slack, Teams, Matrix) and are already maintaining rooms/channels for their classes within that platform, it would be convenient for teachers to be able to link to those as the communication method within their course, without the overhead of having to set up a full provider, or having the LMS performing any administration (room creation, access , permissions etc) that may conflict/overwrite any management already taking place. . Confirmed requirements Create a new communication provider. Add a provider specific field which allows a URL to be provided. This URL will be what is linked on the communication icon within the course. No administration/management functions (eg room membership, power levels, room name, avatar etc) will be performed by the subsystem/this provider. Any related required provider API methods that need to be implemented will perform no action. . TBC requirements Language strings and naming. Whether any changes are required to remove/reword the "room name" field which is part of the subsystem. This may be useful to retain so teachers can put a description of what theyve linked to which other teachers will see, but wont have any impact within the provider itself, since the room wont be created. Whether anything is required to avoid running tasks which will take no action. . FAQ Why not just make it possible to provide a room ID (or equivalent) within a specific provider such as Matrix? Initially, we were considering exactly this, however it introduces a few of unnecessary complexities: Where rooms are pre-existing, we still dont want room/user administration being completed by the LMS, so all of that administration functionality within the subsystem and providers would have to factor in "if room ID provided, do/do not do xyz". The fact that its essentially providing a link within the consistent communication UI, so there is no reason for it to be implemented or limited per provider since the behaviour will be consistent across the board. It avoids having to factor custom URL rules into providers.
6.summary: Create associated methods in matrix to check room availability/state
description: Matrix records are created when communication is enabled and the room configuration is saved in db. Create a new method to reliably check against the roomid or any associated data to check if the room created or available to use in course.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Improve Student Activity Completion
description: Improve Student Activity Completion Areas for improvement: Providing clearer information on the course page around required actions to complete activities Providing the ability inside the activity to mark it as completed Providing information inside the activity showing what a student is required to do for activities with automatic completion Provide clear due date information for each activity Project dev docs page|
| Unsolvable | 1.summary: User story: As a student I want to be able to quickly see on the course page which activities I need to complete so that I know where to focus my attention next
description: . Story As a student I want to be able to quickly see on the course page which activities I need to complete So that I know where to focus my attention next
2.summary: User story: As a student I want to be able to complete an activity from inside the activity so that I don t need to navigate back to the course page to do so
description: . Story As a student I want to be able to complete an activity from inside the activity So that I don t need to navigate back to the course page to do so . Acceptance criteria When I am on the activity with manual completion s landing page (e.g. view.php), I should be able to mark the activity as completed in its landing page. !mark-done.png|thumbnail!
3.summary: User story: As a student I want to be able to clearly see the requirements for an activity with automatic activity completion so that I understand what I need to do to complete it
description: . Story As a student I want to be able to clearly see the requirements for an activity with automatic activity completion So that I understand what I need to do to complete it
4.summary: User story: As a student I want to be able to clearly see the activity dates that are relevant to me so that I can easily plan my schedule in advance
description: . Story As a student I want to be able to clearly see the activity dates that are relevant to me So that I can easily plan my schedule in advance . Acceptance criteria When I am on the course page, I should be able to see the activity dates that are relevant to me When I am on the landing page (e.g. view.php) of an activity with dates (e.g. due dates, etc.), I should be able to see these activity dates that are relevant to me. _Note:_ Activity dates relevant to the user cover the following scenarios: If there are no overrides applicable to the student, then activitys dates (e.g. assignment submission-open date, due date, etc.) should be displayed normally. If there are group overrides applied to the activity dates, then a student belonging to a group with group overrides should see the overridden date(s) for the students applicable group. If there is a user override for a student has been applied to the activity dates, then the student should see the overridden dates. User override dates take precedence over group override dates. A student belonging to a group with group overrides for the activity dates and user overrides should see the user overrides instead. Bottom line is that the activity dates that the students see on their course homepage/activity view page should be consistent with the relevant activity dates that they see on their calendar/timeline.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Improve Student Activity Completion
description: Improve Student Activity Completion Areas for improvement: Providing clearer information on the course page around required actions to complete activities Providing the ability inside the activity to mark it as completed Providing information inside the activity showing what a student is required to do for activities with automatic completion Provide clear due date information for each activity Project dev docs page|
### Response:
1.summary: User story: As a student I want to be able to quickly see on the course page which activities I need to complete so that I know where to focus my attention next
description: . Story As a student I want to be able to quickly see on the course page which activities I need to complete So that I know where to focus my attention next
2.summary: User story: As a student I want to be able to complete an activity from inside the activity so that I don t need to navigate back to the course page to do so
description: . Story As a student I want to be able to complete an activity from inside the activity So that I don t need to navigate back to the course page to do so . Acceptance criteria When I am on the activity with manual completion s landing page (e.g. view.php), I should be able to mark the activity as completed in its landing page. !mark-done.png|thumbnail!
3.summary: User story: As a student I want to be able to clearly see the requirements for an activity with automatic activity completion so that I understand what I need to do to complete it
description: . Story As a student I want to be able to clearly see the requirements for an activity with automatic activity completion So that I understand what I need to do to complete it
4.summary: User story: As a student I want to be able to clearly see the activity dates that are relevant to me so that I can easily plan my schedule in advance
description: . Story As a student I want to be able to clearly see the activity dates that are relevant to me So that I can easily plan my schedule in advance . Acceptance criteria When I am on the course page, I should be able to see the activity dates that are relevant to me When I am on the landing page (e.g. view.php) of an activity with dates (e.g. due dates, etc.), I should be able to see these activity dates that are relevant to me. _Note:_ Activity dates relevant to the user cover the following scenarios: If there are no overrides applicable to the student, then activitys dates (e.g. assignment submission-open date, due date, etc.) should be displayed normally. If there are group overrides applied to the activity dates, then a student belonging to a group with group overrides should see the overridden date(s) for the students applicable group. If there is a user override for a student has been applied to the activity dates, then the student should see the overridden dates. User override dates take precedence over group override dates. A student belonging to a group with group overrides for the activity dates and user overrides should see the user overrides instead. Bottom line is that the activity dates that the students see on their course homepage/activity view page should be consistent with the relevant activity dates that they see on their calendar/timeline.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Introduce a new chart API and library
description: For 3.2 we want to introduce a new chart library (and API) which will: - Replace existing charts (unless the existing ones are too specific) - Render client side - Support accessibility - Support large data sets - Support dynamic data changes - Support most commonly used graphs - Support i18n - Support printing - Be proven to have a bright future (active community, stable, well maintained, ...) - Be abstracted enough to support another library should we need to change - Be made easy to use by our developers (simple API, supports PHP and JS, ...)
| Unsolvable | 1.summary: Convert scormreport_graphs to the new library
description: As the summary says.
2.summary: Convert report_log graphs to the new library
description: We should convert the existing graph static images of the log report to use the new chartjs library.
3.summary: Add support for title
description: Our current library display a title on each chart and we should support that in our new chart API.
4.summary: Add support for axis labels and positions
description: As the summary says.
5.summary: Add support for stepSize/tickInterval
description: Sometimes we would want to force the interval to be 1 as decimals do not make sense. Other times we may want to define a specific interval. Investigate how other libraries implement this, most likely it will be an axis property.
6.summary: Convert the statistics report to the new library
description: As the summary says.
7.summary: Convert the quiz charts to the new library
description: As the summary says.
8.summary: Convert the course overview report to the new chart library
description: As the summary says.
9.summary: Add support for minimum value on axes
description: See summary.
10.summary: Define a set of default colours for series
description: Series should come up with a default set of colours, they only need to be defined in JS.
11.summary: Support multiple colours in the same series
description: For pie, and sometimes bar, charts, it may be useful to be able to set a colour per value, or multiple colours for the same series depending on how the API is set. Pie charts only have one series and having the same colour per part is confusing. Bar charts may be more representative if they had a different colour per bar but only when they have only 1 series.
12.summary: Create an accessible/HTML output module for charts
description: Getting a chart object and rendering it as an HTML table is required for accessibility purposes.
13.summary: Handle RTL in charts
description: I assume that we need to flip the position of the Y axis, and reverse the labels and values in the X axis. I would appreciate if nadavkav could give his impressions on the need to have charts RTL compatible.
14.summary: Set charts to also (optionally) display their data in a table
description: Damyon suggested a collapsible region in which the data table is always displayed. The primary need for the data table is for accessibility. Developers could opt-out from printing the data table, in which case it will only be visible via _accesshide_.
15.summary: Support custom y axis labels
description: See summary.
16.summary: Document the PHP/JS API
description: Add PHP and JS Docs to everything.
17.summary: Add support for line tension
description: We should implement support for line tension as some chart across moodle use line charts with strong tension.
18.summary: Add support for additional axes
description: As summary says.
19.summary: Convert choice module charts to the new library
description: The choice module has charts that is generated using a table and it should be converted to use the new charts API.
20.summary: Add support for horizontal position on bar chart
description: On the choice module the results can be displayed in vertical bars and horizontal bars. At the moment our API just support vertical bars, so it should support both positions.
21.summary: Add support for series labels
description: During the development of the , Ive noticed choice charts displays the percentage of each choice. We need to figure out a way of implementing the percentage to fully match the current behaviour.
22.summary: Convert feedback analysis chart to the new library
description: On feedback module we display horizontal bar charts for the multiple choice answers and it should be converted to use the new library.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Introduce a new chart API and library
description: For 3.2 we want to introduce a new chart library (and API) which will: - Replace existing charts (unless the existing ones are too specific) - Render client side - Support accessibility - Support large data sets - Support dynamic data changes - Support most commonly used graphs - Support i18n - Support printing - Be proven to have a bright future (active community, stable, well maintained, ...) - Be abstracted enough to support another library should we need to change - Be made easy to use by our developers (simple API, supports PHP and JS, ...)
### Response:
1.summary: Convert scormreport_graphs to the new library
description: As the summary says.
2.summary: Convert report_log graphs to the new library
description: We should convert the existing graph static images of the log report to use the new chartjs library.
3.summary: Add support for title
description: Our current library display a title on each chart and we should support that in our new chart API.
4.summary: Add support for axis labels and positions
description: As the summary says.
5.summary: Add support for stepSize/tickInterval
description: Sometimes we would want to force the interval to be 1 as decimals do not make sense. Other times we may want to define a specific interval. Investigate how other libraries implement this, most likely it will be an axis property.
6.summary: Convert the statistics report to the new library
description: As the summary says.
7.summary: Convert the quiz charts to the new library
description: As the summary says.
8.summary: Convert the course overview report to the new chart library
description: As the summary says.
9.summary: Add support for minimum value on axes
description: See summary.
10.summary: Define a set of default colours for series
description: Series should come up with a default set of colours, they only need to be defined in JS.
11.summary: Support multiple colours in the same series
description: For pie, and sometimes bar, charts, it may be useful to be able to set a colour per value, or multiple colours for the same series depending on how the API is set. Pie charts only have one series and having the same colour per part is confusing. Bar charts may be more representative if they had a different colour per bar but only when they have only 1 series.
12.summary: Create an accessible/HTML output module for charts
description: Getting a chart object and rendering it as an HTML table is required for accessibility purposes.
13.summary: Handle RTL in charts
description: I assume that we need to flip the position of the Y axis, and reverse the labels and values in the X axis. I would appreciate if nadavkav could give his impressions on the need to have charts RTL compatible.
14.summary: Set charts to also (optionally) display their data in a table
description: Damyon suggested a collapsible region in which the data table is always displayed. The primary need for the data table is for accessibility. Developers could opt-out from printing the data table, in which case it will only be visible via _accesshide_.
15.summary: Support custom y axis labels
description: See summary.
16.summary: Document the PHP/JS API
description: Add PHP and JS Docs to everything.
17.summary: Add support for line tension
description: We should implement support for line tension as some chart across moodle use line charts with strong tension.
18.summary: Add support for additional axes
description: As summary says.
19.summary: Convert choice module charts to the new library
description: The choice module has charts that is generated using a table and it should be converted to use the new charts API.
20.summary: Add support for horizontal position on bar chart
description: On the choice module the results can be displayed in vertical bars and horizontal bars. At the moment our API just support vertical bars, so it should support both positions.
21.summary: Add support for series labels
description: During the development of the , Ive noticed choice charts displays the percentage of each choice. We need to figure out a way of implementing the percentage to fully match the current behaviour.
22.summary: Convert feedback analysis chart to the new library
description: On feedback module we display horizontal bar charts for the multiple choice answers and it should be converted to use the new library.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: New Report builder reports for 4.1
description: Collect together any new report sources and/or system reports for Moodle 4.1 Its important that we continue converting existing system reports, and create more report sources for custom reporting to make better use of the tool. We (Workplace team) will flesh out this epic, and issues within it, to better define requirements
| Unsolvable | 1.summary: Convert cohort listing reports to Report builder
description: . Moot Italy Visitors The branch used to demonstrate conversion to Report builder is at (as mentioned during the presentation :) ) This issue is about converting the Cohort listing page into using Report Builder. The idea is to use this issue to create a presentation for the Italian Moot and explain step by step how to convert the existing cohorts listing code to a system report explaining these ideas: Create a new system report class and how to call it Reuse existing Report Builder entities Create custom columns (columns not present in the entity and that will just be used in this report) Add filters to the report Add conditions (fixed filters that cannot be modified from UI) Use parameters Add actions to the report (Show/Hide cohort, Edit cohort, Delete cohort, Add members to the cohort) and check permissions using callbacks How to apply custom CSS to report rows Override column names (in case column needs a different name than the one defined in the entity) The cohort entities added in should provide most of the report data
2.summary: Create "Badges" custom report source
description: The purpose of this new report source, is to allow flexible reports to be generated to allow for the reporting of all badges across the site, their criteria and users who have been issued with them . Columns Badge details Name (default) Description (default) Criteria Image Language Version Badge status Expiry date Image authors name Image authors email Image authors URL Badge issued Date issued (default) Expiry date Visible Badge recipient Full name (default) Course . Conditions Badge details Type (default) Name (default) Badge status Badge issued Date issued Expiry date Visible Badge recipient Course . Filters Badge details Name (default) Badge status Type Badge issued Date issued (default) Expiry date Visible Badge recipient Full name (default) Course
3.summary: Custom report source for course participants
description: The purpose of this new report source, is to allow flexible reports to be generated to allow for the reporting of course participants, enrolment, completion, and the last course access date. . Columns Course category Course Enrolment Method Time created Time started Time ended Status User Course completion Completed Progress Time enrolled Time started Time completed Time reaggregated Days taking course Days until completion Grade Required course grade Course access Last access to course . Conditions / Filters Course category Course Enrolment Method Time created Time started Time ended Status User Course completion Completed Time completed Course access Last access to course
4.summary: Create "Notes" custom report source
description: The purpose of this report source is to allow flexible reporting on site, personal and course related notes| . Columns Note Content Context Time created Time modified Recipient Author Course . Conditions/filters Note Content Context Time created Time modified Recipient Author Course This will also demonstrate the pattern of using the same entity (user) multiple times in a single report (once for the note author, once for the recipient) and provide API improvements for the same I also found while working on this, but that can be fixed separately to this one as its a pre-existing bug
5.summary: Create "Blogs" custom report source
description: The purpose of this report source is to allow flexible reporting on site, personal and course related blogs| . Columns Blog Title Body Attachment Publish to Time created Time modified Tags Name Name with link User Course . Conditions/filters Blog Title Body Attachment Publish to Time created Time modified Tags Name User Course
6.summary: Create "Task logs" custom report source
description: We have a task logs system report and entity (). Expose that data as a custom report source - add any missing column/filter elements as appropriate . Columns Task log Name Plugin Type Start time End time Duration Host name PID Database Database reads Database writes Result User . Conditions/filters Task log Name Plugin Type Task output Result Start time End time Duration Database reads Database writes User Directly related to this report source, its noticeable that the sum and average aggregation types should be improved to execute column callbacks, so we should fix that here too Before: !Screenshot_2022-07-08 Task logs(1).png! After: !Screenshot_2022-07-08 Task logs.png! Also noticed while working on this
7.summary: Create "Tags" custom report source
description: The purpose of this report source is to allow flexible reporting on tags (collections, tags and tag instances) across the site . Columns Tag collection Name Is default Component Is searchable Custom URL Tag Name Name with link Description Is standard Is flagged Time modified Tag instance Context Component Item type Item ID Time created Time modified User who created the tag . Conditions/filters Tag collection Name Is default Is searchable Tag Name Is standard Is flagged Time modified Tag instance Time created Time modified User who created the tag Some of the columns require be fixed to aggregate properly
8.summary: Create "Groups" custom report source
description: The purpose of this report source is to allow flexible reporting on groups, members and groupings across the site (and introduce related entities that will be required for further course reporting) . Columns Course Group Name ID number Description Enrolment key Picture Time created Time modified Grouping Name ID number Description Time created Time modified Group member Time added Component User . Conditions/filters Course Group Name ID number Time created Grouping Name ID number Time created Group member Time added User
9.summary: Create "Comments" custom report source
description: The purpose of this report source is to allow reporting on comments made by users in various contexts (and add comment entity that can be easily re-used as appropriate for reports on elements that support commenting) . Columns Comment Content Context Plugin Area Item ID Time created User . Conditions/filters Comment Content Time created User
10.summary: Create "Files" custom report source
description: The purpose of this report is to provide an overview of the Moodle stored files, allowing admins to easily identify courses/activities which are consuming a lot of file space. It can also be used to identify licenses used across the site, identifying those missing attribution The new file entity will also be used in future reports on elements with associated/attached files . Columns File Name Size Path Type Author License Context Plugin Area Item ID Time created User . Conditions/filters File Directory (boolean) Drafts (boolean) Name Size License Time created User Note, we need the sum/average aggregation improvements from in order to improve report data, e.g. when calculating entire filesize of given context/filearea/etc
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: New Report builder reports for 4.1
description: Collect together any new report sources and/or system reports for Moodle 4.1 Its important that we continue converting existing system reports, and create more report sources for custom reporting to make better use of the tool. We (Workplace team) will flesh out this epic, and issues within it, to better define requirements
### Response:
1.summary: Convert cohort listing reports to Report builder
description: . Moot Italy Visitors The branch used to demonstrate conversion to Report builder is at (as mentioned during the presentation :) ) This issue is about converting the Cohort listing page into using Report Builder. The idea is to use this issue to create a presentation for the Italian Moot and explain step by step how to convert the existing cohorts listing code to a system report explaining these ideas: Create a new system report class and how to call it Reuse existing Report Builder entities Create custom columns (columns not present in the entity and that will just be used in this report) Add filters to the report Add conditions (fixed filters that cannot be modified from UI) Use parameters Add actions to the report (Show/Hide cohort, Edit cohort, Delete cohort, Add members to the cohort) and check permissions using callbacks How to apply custom CSS to report rows Override column names (in case column needs a different name than the one defined in the entity) The cohort entities added in should provide most of the report data
2.summary: Create "Badges" custom report source
description: The purpose of this new report source, is to allow flexible reports to be generated to allow for the reporting of all badges across the site, their criteria and users who have been issued with them . Columns Badge details Name (default) Description (default) Criteria Image Language Version Badge status Expiry date Image authors name Image authors email Image authors URL Badge issued Date issued (default) Expiry date Visible Badge recipient Full name (default) Course . Conditions Badge details Type (default) Name (default) Badge status Badge issued Date issued Expiry date Visible Badge recipient Course . Filters Badge details Name (default) Badge status Type Badge issued Date issued (default) Expiry date Visible Badge recipient Full name (default) Course
3.summary: Custom report source for course participants
description: The purpose of this new report source, is to allow flexible reports to be generated to allow for the reporting of course participants, enrolment, completion, and the last course access date. . Columns Course category Course Enrolment Method Time created Time started Time ended Status User Course completion Completed Progress Time enrolled Time started Time completed Time reaggregated Days taking course Days until completion Grade Required course grade Course access Last access to course . Conditions / Filters Course category Course Enrolment Method Time created Time started Time ended Status User Course completion Completed Time completed Course access Last access to course
4.summary: Create "Notes" custom report source
description: The purpose of this report source is to allow flexible reporting on site, personal and course related notes| . Columns Note Content Context Time created Time modified Recipient Author Course . Conditions/filters Note Content Context Time created Time modified Recipient Author Course This will also demonstrate the pattern of using the same entity (user) multiple times in a single report (once for the note author, once for the recipient) and provide API improvements for the same I also found while working on this, but that can be fixed separately to this one as its a pre-existing bug
5.summary: Create "Blogs" custom report source
description: The purpose of this report source is to allow flexible reporting on site, personal and course related blogs| . Columns Blog Title Body Attachment Publish to Time created Time modified Tags Name Name with link User Course . Conditions/filters Blog Title Body Attachment Publish to Time created Time modified Tags Name User Course
6.summary: Create "Task logs" custom report source
description: We have a task logs system report and entity (). Expose that data as a custom report source - add any missing column/filter elements as appropriate . Columns Task log Name Plugin Type Start time End time Duration Host name PID Database Database reads Database writes Result User . Conditions/filters Task log Name Plugin Type Task output Result Start time End time Duration Database reads Database writes User Directly related to this report source, its noticeable that the sum and average aggregation types should be improved to execute column callbacks, so we should fix that here too Before: !Screenshot_2022-07-08 Task logs(1).png! After: !Screenshot_2022-07-08 Task logs.png! Also noticed while working on this
7.summary: Create "Tags" custom report source
description: The purpose of this report source is to allow flexible reporting on tags (collections, tags and tag instances) across the site . Columns Tag collection Name Is default Component Is searchable Custom URL Tag Name Name with link Description Is standard Is flagged Time modified Tag instance Context Component Item type Item ID Time created Time modified User who created the tag . Conditions/filters Tag collection Name Is default Is searchable Tag Name Is standard Is flagged Time modified Tag instance Time created Time modified User who created the tag Some of the columns require be fixed to aggregate properly
8.summary: Create "Groups" custom report source
description: The purpose of this report source is to allow flexible reporting on groups, members and groupings across the site (and introduce related entities that will be required for further course reporting) . Columns Course Group Name ID number Description Enrolment key Picture Time created Time modified Grouping Name ID number Description Time created Time modified Group member Time added Component User . Conditions/filters Course Group Name ID number Time created Grouping Name ID number Time created Group member Time added User
9.summary: Create "Comments" custom report source
description: The purpose of this report source is to allow reporting on comments made by users in various contexts (and add comment entity that can be easily re-used as appropriate for reports on elements that support commenting) . Columns Comment Content Context Plugin Area Item ID Time created User . Conditions/filters Comment Content Time created User
10.summary: Create "Files" custom report source
description: The purpose of this report is to provide an overview of the Moodle stored files, allowing admins to easily identify courses/activities which are consuming a lot of file space. It can also be used to identify licenses used across the site, identifying those missing attribution The new file entity will also be used in future reports on elements with associated/attached files . Columns File Name Size Path Type Author License Context Plugin Area Item ID Time created User . Conditions/filters File Directory (boolean) Drafts (boolean) Name Size License Time created User Note, we need the sum/average aggregation improvements from in order to improve report data, e.g. when calculating entire filesize of given context/filearea/etc
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.10
description: In 3.10 we can remove functionality that was deprecated in 3.6 or earlier (see ) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
| Unsolvable | 1.summary: Update windows timezone list in core_date
description: GENERAL NOTE: If the supported PHP versions were shipped with an older IANA timezone database version at some point, please use the timezone list from the older tz database version. For example, assuming the current supported PHP versions are 7.2, 7.3 and 7.4, and the current tz databse version is _2020a._ As the tz databse version 2020a was released on 23/04/2020, at some point 7.2, 7.3 and 7.4 (prior to 7.4.6) were shipped with the older tz database version. These sites will not have (support) the latest timezone changes from _2020a_ (timezone renaming, deprecation, etc.) and therefore, we should not use or map them in _$badzones_ or deprecate the old timezone strings. INSTRUCTIONS PART 1. Ensure that each windows timezone ( exist in _$badzones_ (_lib/classes/date.php_) and have a mapping to current good (canonical) IANA timezone from the IANA timezone information database ( Please see GENERAL NOTE to determine which timezone database version should be used. Also, ensure that all good IANA timezones have translations. Resources that could help finding the equivalence between the Windows and the IANA timezones: PART 2. Ensure that old IANA timezones are not being used as target in the mapping in _$badzones_ (_lib/classes/date.php_). Every old IANA timezone used should be replaced with the good (canonical) IANA timezone. Please see GENERAL NOTE to determine which timezone database version should be used to find the old timezones. Resources that could help finding the IANA timezone changes: (replace "tzdb-2020a" if a different tz database version is required) PART 3: Ensure that there is a mapping between every old timezone and new timezone name in _$badzones_ (_lib/classes/date.php_). Please see GENERAL NOTE to determine which timezone database version should be used to find the old timezones. Additional resources that could help finding the IANA timezone name changes: (replace "tzdb-2020a" if a different tz database version is required) According to the old timezone names are either deprecated or they are considered to be an alias to the good (canonical) timezone name. For a clearer distinction, add the mappings for the deprecated timezones under the "_A lot more bad legacy (deprecated) time zones._" section in _$badzones_ (lib/classes/date.php), while the aliases under "_Link old timezone names with their new names._" NOTE: The general purpose of PART 3 is to provide automatic timezone name changes, so when a calendar event or a user comes with Asia/Calcutta, the event or user is changed to Asia/Kolkata (or whatever is the new timezone name is). Also, in the future this can be expanded (in followups) for user edit and user upload. PART 4: Deprecate and remove the existing translations (_lang/en/timezones.php_) of the old IANA timezones. Please see GENERAL NOTE to determine which timezone translations are safe to be deprecated and removed. ------------------------ For the testing instructions you can manually edit the .ics file from the cloned issue: Open the .ics file using a text editor. Replace the timezone ID there (i.e. "U.S. Mountain Standard Time") to one of the new ones added. Replace the time entries (i.e. "202001" (2020 is the year and 01 the month) to a more recent date). ------------------------ _Please create a clone of this issue for next version before closing this_
2.summary: Final removal of lib/coursecatlib.php
description: The file throws debugging saying Do not include coursecatlib.php and isnt used anywhere. This was done in 3.6, so we can probably remove this file completely now.
3.summary: Remove deprecated enrolment popup
description: The old enrolment popup was replaced in . Files associated with the old UI should be removed.
4.summary: Remove strings deprecated in 3.6
description: Remove strings from language files under the heading "Deprecated in Moodle 3.6" and the respective lines in deprecated.txt files See also
5.summary: Final deprecation of web services in message/externallib.php
description: A whole bunch were deprecated due to and . Do a grep for in the codebase to find out what can be removed.
6.summary: Final deprecation of lti_get_shortcuts()
description: This function was deprecated in Moodle 3.6 and just needs to follow the final stages of deprecation.
7.summary: Final deprecation: I navigate to "ITEM" node in "MAINNODE > PATH" behat step
description: Go through lib/tests/behat/behat_deprecated.php and theme/boost/tests/behat/behat_theme_boost_behat_deprecated.php and remove function i_navigate_to_node_in().
8.summary: Final deprecation get_roles_on_exact_context() and get_roles_with_assignment_on_context()
description: Final deprecation: get_roles_on_exact_context() and get_roles_with_assignment_on_context()
9.summary: Final deprecation of the events message_contact_blocked and message_contact_unblocked
description: These were deprecated in 3.6 (see ). We can now do the final deprecation. Note - the strings deprecated in get_name() will be handled by .
10.summary: Final deprecation of methods in message/classes/api.php
description: Final deprecation of the methods deprecated in 3.6.
11.summary: Remove behat steps deprecated in 3.6
description: go through lib/tests/behat/behat_deprecated.php and remove steps that were deprecated in Moodle 3.6 (or earlier) please add to the description if you know of any other deprecated behat functionality outside of this file that needs to be removed
12.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.6
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.6 should be replaced with exceptions in 4.0 This includes all functions in lib/deprecatedlib.php that say since 3.6 If any functions from this file do not have this comment but also need to be finally deprecated in 4.0 - please list them in this issue description List of functions: print_textarea, calendar_get_all_allowed_types, groups_get_all_groups_for_courses, events_get_cached, events_uninstall, events_cleanup, events_dequeue, events_get_handlers, get_roles_on_exact_context, get_roles_with_assignment_on_context, message_add_contact, message_remove_contact, message_unblock_contact, message_block_contact, message_get_contact
13.summary: Remove Bootstrap 2 and Bootstrap 4 alpha compatibility files
description: To reduce that amount of CSS shipped with the Boost theme we should start looking at our core CSS and cleanup unused CSS Since the bootstrap base theme is no longer supported and the bootstrap css is from upstream bootstrap version 4.3.1 it is time to remove files theme/boost/scss/moodle/bs2-compat.scss and theme/boost/scss/moodle/bs4alphacompat.scss Of course we need to check carefully if there are no renderers or templates still using legacy Bootstrap Classes.
14.summary: Final deprecation of add_to_log()
description: Its been deprecated since 2.7.
15.summary: Deprecate supports_recursion() & extend_lock() in the Lock API
description: If a lock type supports_recursion() then the locks behave very differently to when they dont. Yet despite this not a single place in core actually calls for supports_recursion(), and if it did then it would have to do a code fork to work around the different behaviors. This feels like an architectural mistake in the design of the lock api, all lock implementations should behave identically so that calling code doesnt need to worry about things like this. Given that the only place that leverages this is the unit tests, it is clear no one wants or needs it or is using this. Ive had a bit of a quick search on github and in the wild for 3rd party uses and couldnt find any. Its also trivial to workaround in the lock types that do support recursion to bring their behavior back in line to the locks which dont, as they already internally store a list of open locks for the current request and could just reject the second lock attempt.
16.summary: Remove the lib/form/htmleditor.php element
description: This was deprecated in and can be removed.
17.summary: CLONE - Remove old class renames
description: core_component looks for COMPONENT/db/renamedclasses.php files, it allows us to avoid traumatic transitions and BC breakages by listing classes that have been removed. We need to clean the list at some point.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.10
description: In 3.10 we can remove functionality that was deprecated in 3.6 or earlier (see ) There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
### Response:
1.summary: Update windows timezone list in core_date
description: GENERAL NOTE: If the supported PHP versions were shipped with an older IANA timezone database version at some point, please use the timezone list from the older tz database version. For example, assuming the current supported PHP versions are 7.2, 7.3 and 7.4, and the current tz databse version is _2020a._ As the tz databse version 2020a was released on 23/04/2020, at some point 7.2, 7.3 and 7.4 (prior to 7.4.6) were shipped with the older tz database version. These sites will not have (support) the latest timezone changes from _2020a_ (timezone renaming, deprecation, etc.) and therefore, we should not use or map them in _$badzones_ or deprecate the old timezone strings. INSTRUCTIONS PART 1. Ensure that each windows timezone ( exist in _$badzones_ (_lib/classes/date.php_) and have a mapping to current good (canonical) IANA timezone from the IANA timezone information database ( Please see GENERAL NOTE to determine which timezone database version should be used. Also, ensure that all good IANA timezones have translations. Resources that could help finding the equivalence between the Windows and the IANA timezones: PART 2. Ensure that old IANA timezones are not being used as target in the mapping in _$badzones_ (_lib/classes/date.php_). Every old IANA timezone used should be replaced with the good (canonical) IANA timezone. Please see GENERAL NOTE to determine which timezone database version should be used to find the old timezones. Resources that could help finding the IANA timezone changes: (replace "tzdb-2020a" if a different tz database version is required) PART 3: Ensure that there is a mapping between every old timezone and new timezone name in _$badzones_ (_lib/classes/date.php_). Please see GENERAL NOTE to determine which timezone database version should be used to find the old timezones. Additional resources that could help finding the IANA timezone name changes: (replace "tzdb-2020a" if a different tz database version is required) According to the old timezone names are either deprecated or they are considered to be an alias to the good (canonical) timezone name. For a clearer distinction, add the mappings for the deprecated timezones under the "_A lot more bad legacy (deprecated) time zones._" section in _$badzones_ (lib/classes/date.php), while the aliases under "_Link old timezone names with their new names._" NOTE: The general purpose of PART 3 is to provide automatic timezone name changes, so when a calendar event or a user comes with Asia/Calcutta, the event or user is changed to Asia/Kolkata (or whatever is the new timezone name is). Also, in the future this can be expanded (in followups) for user edit and user upload. PART 4: Deprecate and remove the existing translations (_lang/en/timezones.php_) of the old IANA timezones. Please see GENERAL NOTE to determine which timezone translations are safe to be deprecated and removed. ------------------------ For the testing instructions you can manually edit the .ics file from the cloned issue: Open the .ics file using a text editor. Replace the timezone ID there (i.e. "U.S. Mountain Standard Time") to one of the new ones added. Replace the time entries (i.e. "202001" (2020 is the year and 01 the month) to a more recent date). ------------------------ _Please create a clone of this issue for next version before closing this_
2.summary: Final removal of lib/coursecatlib.php
description: The file throws debugging saying Do not include coursecatlib.php and isnt used anywhere. This was done in 3.6, so we can probably remove this file completely now.
3.summary: Remove deprecated enrolment popup
description: The old enrolment popup was replaced in . Files associated with the old UI should be removed.
4.summary: Remove strings deprecated in 3.6
description: Remove strings from language files under the heading "Deprecated in Moodle 3.6" and the respective lines in deprecated.txt files See also
5.summary: Final deprecation of web services in message/externallib.php
description: A whole bunch were deprecated due to and . Do a grep for in the codebase to find out what can be removed.
6.summary: Final deprecation of lti_get_shortcuts()
description: This function was deprecated in Moodle 3.6 and just needs to follow the final stages of deprecation.
7.summary: Final deprecation: I navigate to "ITEM" node in "MAINNODE > PATH" behat step
description: Go through lib/tests/behat/behat_deprecated.php and theme/boost/tests/behat/behat_theme_boost_behat_deprecated.php and remove function i_navigate_to_node_in().
8.summary: Final deprecation get_roles_on_exact_context() and get_roles_with_assignment_on_context()
description: Final deprecation: get_roles_on_exact_context() and get_roles_with_assignment_on_context()
9.summary: Final deprecation of the events message_contact_blocked and message_contact_unblocked
description: These were deprecated in 3.6 (see ). We can now do the final deprecation. Note - the strings deprecated in get_name() will be handled by .
10.summary: Final deprecation of methods in message/classes/api.php
description: Final deprecation of the methods deprecated in 3.6.
11.summary: Remove behat steps deprecated in 3.6
description: go through lib/tests/behat/behat_deprecated.php and remove steps that were deprecated in Moodle 3.6 (or earlier) please add to the description if you know of any other deprecated behat functionality outside of this file that needs to be removed
12.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.6
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.6 should be replaced with exceptions in 4.0 This includes all functions in lib/deprecatedlib.php that say since 3.6 If any functions from this file do not have this comment but also need to be finally deprecated in 4.0 - please list them in this issue description List of functions: print_textarea, calendar_get_all_allowed_types, groups_get_all_groups_for_courses, events_get_cached, events_uninstall, events_cleanup, events_dequeue, events_get_handlers, get_roles_on_exact_context, get_roles_with_assignment_on_context, message_add_contact, message_remove_contact, message_unblock_contact, message_block_contact, message_get_contact
13.summary: Remove Bootstrap 2 and Bootstrap 4 alpha compatibility files
description: To reduce that amount of CSS shipped with the Boost theme we should start looking at our core CSS and cleanup unused CSS Since the bootstrap base theme is no longer supported and the bootstrap css is from upstream bootstrap version 4.3.1 it is time to remove files theme/boost/scss/moodle/bs2-compat.scss and theme/boost/scss/moodle/bs4alphacompat.scss Of course we need to check carefully if there are no renderers or templates still using legacy Bootstrap Classes.
14.summary: Final deprecation of add_to_log()
description: Its been deprecated since 2.7.
15.summary: Deprecate supports_recursion() & extend_lock() in the Lock API
description: If a lock type supports_recursion() then the locks behave very differently to when they dont. Yet despite this not a single place in core actually calls for supports_recursion(), and if it did then it would have to do a code fork to work around the different behaviors. This feels like an architectural mistake in the design of the lock api, all lock implementations should behave identically so that calling code doesnt need to worry about things like this. Given that the only place that leverages this is the unit tests, it is clear no one wants or needs it or is using this. Ive had a bit of a quick search on github and in the wild for 3rd party uses and couldnt find any. Its also trivial to workaround in the lock types that do support recursion to bring their behavior back in line to the locks which dont, as they already internally store a list of open locks for the current request and could just reject the second lock attempt.
16.summary: Remove the lib/form/htmleditor.php element
description: This was deprecated in and can be removed.
17.summary: CLONE - Remove old class renames
description: core_component looks for COMPONENT/db/renamedclasses.php files, it allows us to avoid traumatic transitions and BC breakages by listing classes that have been removed. We need to clean the list at some point.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Number of templates not viewable in template library
description: There are a number of templates in moodle that can not be viewed in Site administration Development Template library instead the template source code is displayed. The other problem is that developers copy the incorrect syntax Templates are: block_lp/ core/action_link core/action_menu_ core/actions core/chart core/chooser core/dataformat_selector core/email core/help_icon core/loading core/login core/modal core/prevent core/select_time core/skip_links core_admin/setting_configpasswordunmask (example broken) core_admin/settings_search_results (example broken) core_course/modchooser core_form/editor_textarea core_grades/ core_question/qbank_chooser core_search/result gradereport_singleview/ mod_assign/ (some) mod_forum/ (most of them, mod_forum/forum_post_emaildigestbasic_htmlemail even throws AJAX exception) mod_lti/ (some) mod_quiz/question_chooser report_competency/ theme_boost/ - all these templates throw exception, we need to fix this in the template library API tool_lp/ (many) tool_templatelibrary/list_templates_page (hehe, recursion :) ) These templates were introduced in , , , , , , , , , , , , , , - fred , - brendanheywood , , - ryanwyllie , , , , , - damyon - dmonllao - dobedobedoh I created this issue as an Epic, feel free to add issues to it to fix individual templates. rajeshtaneja, do you think it is reasonable to add a QA test that would ensure that all templates in the templates library have example context?
| Unsolvable | 1.summary: Fix lint issues in mod_lti mod/lti/templates/tool_configure.mustache
description: (1) HTML Validation error, line 33: Element div not allowed as child of element button in this context. (Suppressing further errors from this subtree.) ( )
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Number of templates not viewable in template library
description: There are a number of templates in moodle that can not be viewed in Site administration Development Template library instead the template source code is displayed. The other problem is that developers copy the incorrect syntax Templates are: block_lp/ core/action_link core/action_menu_ core/actions core/chart core/chooser core/dataformat_selector core/email core/help_icon core/loading core/login core/modal core/prevent core/select_time core/skip_links core_admin/setting_configpasswordunmask (example broken) core_admin/settings_search_results (example broken) core_course/modchooser core_form/editor_textarea core_grades/ core_question/qbank_chooser core_search/result gradereport_singleview/ mod_assign/ (some) mod_forum/ (most of them, mod_forum/forum_post_emaildigestbasic_htmlemail even throws AJAX exception) mod_lti/ (some) mod_quiz/question_chooser report_competency/ theme_boost/ - all these templates throw exception, we need to fix this in the template library API tool_lp/ (many) tool_templatelibrary/list_templates_page (hehe, recursion :) ) These templates were introduced in , , , , , , , , , , , , , , - fred , - brendanheywood , , - ryanwyllie , , , , , - damyon - dmonllao - dobedobedoh I created this issue as an Epic, feel free to add issues to it to fix individual templates. rajeshtaneja, do you think it is reasonable to add a QA test that would ensure that all templates in the templates library have example context?
### Response:
1.summary: Fix lint issues in mod_lti mod/lti/templates/tool_configure.mustache
description: (1) HTML Validation error, line 33: Element div not allowed as child of element button in this context. (Suppressing further errors from this subtree.) ( )
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Plugins
summary: Align version 2.5 to the latest versions of Moodle
description: In this version we will drop support of old versions of Moodle in an effort to align releases with the Moodle process. As a first step we need to align this version to support from 3.9 and later (as the oldest)
| Unsolvable | 1.summary: Drop inclusion of Firebase\JWT
description: Description The FireBase\JWT library has been included in Moodle core since Moodle 3.7. The mod_bigbluebuttonbn plugin includes an older version of this library in the vendor directory. It is included to facilitate use of a single plugin version for a very wide range of Moodle versions. Severity High. The version of Firebase\JWT is old, and no longer supported. It is not required for this plugin to continue working as a more recent and supported version is included in the Moodle LMS product. Proposed solution Remove the Firebase\JWT library, the vendor directory, composer files, and related code supporting conditional inclusion and use of the library from the vendor directory. Difficulty Easy. The code is already conditional and is only included in one location.
2.summary: Remove references to Flash Client
description: When the BBB HTML5 client was still in development, it was possible to opt for either the Flash or the HTML5 client by default. Now that the Flash client has been phased out, there is no need to have this setting BIGBLUEBUTTON_CLIENTTYPE_FLASH
3.summary: Remove no longer used settings for scheduled_duration
description: This is a feature deprecated long ago that should be removed enterely from code
4.summary: Completion needs to be refactored
description: 1) mod_bigbluebuttonbn_lib_test::test_bigbluebuttonbn_view 25| debugging() call detected. 26| _get_completion_state() callback functions such as bigbluebuttonbn_get_completion_state have been deprecated and should no longer be used. Please implement the custom completion class mod_bigbluebuttonbn\completion\custom_completion which extends \core_completion\activity_custom_completion.
5.summary: Re-brand BigBlueButtonBN to BigBlueButton
description: BigBlueButtonBN has worked for quite sometime, but it it a very long name. Adjusting to BigBlueButton will not harm any brand but make it work smoothly.
6.summary: Replace $bbbsession array by relevant object
description: The array $bbbsession is used many times in the mod_bigbluebuttonbn code and has several drawbacks: We are not sure that the object is consistent across the code (it is initied and stored in the $SESSION in several locations: view_bbbsession_set, build_bbb_session). Basically, we are never entirely sure of what is in it. It is stored in $SESSION variable sometimes Part of the array store: database information (bigbluebutton object) current context (username, course, context) bigbluebutton instance settings (openingtime, participant list...) global settings (recordallfromstart, information on bbb server, general url such as logoutURL) And more ( would need to check here if there is no info friom the server that would be cached in this array) Basically this has to be refactored. We could imagine to split it into different entities: An helper entity to retrieve global settings (or a small static class that would do just that) An helper to help and retrieve the right settings from the instance (and the logic behind each settings). Context information that would need to be shared across the same session. Let just make it as minimal as possible. Anything that can be cached would then need to be cached instead of stored in the session (if not linked to a session). The task is a bit daunting so it would likely be better to phase it in several stages.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Plugins
summary: Align version 2.5 to the latest versions of Moodle
description: In this version we will drop support of old versions of Moodle in an effort to align releases with the Moodle process. As a first step we need to align this version to support from 3.9 and later (as the oldest)
### Response:
1.summary: Drop inclusion of Firebase\JWT
description: Description The FireBase\JWT library has been included in Moodle core since Moodle 3.7. The mod_bigbluebuttonbn plugin includes an older version of this library in the vendor directory. It is included to facilitate use of a single plugin version for a very wide range of Moodle versions. Severity High. The version of Firebase\JWT is old, and no longer supported. It is not required for this plugin to continue working as a more recent and supported version is included in the Moodle LMS product. Proposed solution Remove the Firebase\JWT library, the vendor directory, composer files, and related code supporting conditional inclusion and use of the library from the vendor directory. Difficulty Easy. The code is already conditional and is only included in one location.
2.summary: Remove references to Flash Client
description: When the BBB HTML5 client was still in development, it was possible to opt for either the Flash or the HTML5 client by default. Now that the Flash client has been phased out, there is no need to have this setting BIGBLUEBUTTON_CLIENTTYPE_FLASH
3.summary: Remove no longer used settings for scheduled_duration
description: This is a feature deprecated long ago that should be removed enterely from code
4.summary: Completion needs to be refactored
description: 1) mod_bigbluebuttonbn_lib_test::test_bigbluebuttonbn_view 25| debugging() call detected. 26| _get_completion_state() callback functions such as bigbluebuttonbn_get_completion_state have been deprecated and should no longer be used. Please implement the custom completion class mod_bigbluebuttonbn\completion\custom_completion which extends \core_completion\activity_custom_completion.
5.summary: Re-brand BigBlueButtonBN to BigBlueButton
description: BigBlueButtonBN has worked for quite sometime, but it it a very long name. Adjusting to BigBlueButton will not harm any brand but make it work smoothly.
6.summary: Replace $bbbsession array by relevant object
description: The array $bbbsession is used many times in the mod_bigbluebuttonbn code and has several drawbacks: We are not sure that the object is consistent across the code (it is initied and stored in the $SESSION in several locations: view_bbbsession_set, build_bbb_session). Basically, we are never entirely sure of what is in it. It is stored in $SESSION variable sometimes Part of the array store: database information (bigbluebutton object) current context (username, course, context) bigbluebutton instance settings (openingtime, participant list...) global settings (recordallfromstart, information on bbb server, general url such as logoutURL) And more ( would need to check here if there is no info friom the server that would be cached in this array) Basically this has to be refactored. We could imagine to split it into different entities: An helper entity to retrieve global settings (or a small static class that would do just that) An helper to help and retrieve the right settings from the instance (and the logic behind each settings). Context information that would need to be shared across the same session. Let just make it as minimal as possible. Anything that can be cached would then need to be cached instead of stored in the session (if not linked to a session). The task is a bit daunting so it would likely be better to phase it in several stages.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: META: Evaluate Administration Block for Plugin Inconsistencies
description: I would like to ensure that we are being consistent in the way that we manage Moodle Plugins. I have noticed some inconsistencies that I would encourage tweaking to avoid confusion. I will create sub-tasks for on this issue so that each one can be evaluated. Peace - Anthony
| Unsolvable | 1.summary: Evaluate renaming Moodle Plugins General plugins (Local) category to Local plugins (General)
description: In Moodle Plugins the category is currently called General plugins. In the Admin block it is called Local plugins. I would recommend renaming the Moodle Plugins category to Local plugins (General). Technically this should be a MDLSITE issue related to plugins; however, it appears the tracker does not different projects for subtasks.
2.summary: Consider renaming Moodle Plugins category Messaging to Message outputs
description: The category names given for Moodle plugins are usually nouns; however, Messaging is a verb and inconsistent with the name found in Moodle which is Admin->Plugins->Message outputs. If at a latter time there were various types of Messaging related plugins then I think the category should be called Messages and then have Message outputs as one of the sub-categories; however currently there are only Message output plugins.
3.summary: Consider moving and renaming Moodle Plugins Users-Enrolment category to Enrolments
description: Currently in Moodle Plugins, Enrolment is found under Users; however, in Moodle itself it is found at Admin->Plugins->Enrolments. I would recommend moving the Users-Enrolment subcategory to its own category and rename it to Enrolments (plural) to be consistent with using plural nouns to name the categories/elements for plugins. Peace - Anthony
4.summary: Consider renaming Moodle Plugins category Web service protocols to Web services (Protocols)
description: Currently, web services are found in Admin->Plugins->Web services but the Moodle Plugins category is name Web service protocols. Ideally, I think the category should be rename Web services; however, if we want to keep the language of protocols I think it should be a descriptor in parentheses. Peace - Anthony
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: META: Evaluate Administration Block for Plugin Inconsistencies
description: I would like to ensure that we are being consistent in the way that we manage Moodle Plugins. I have noticed some inconsistencies that I would encourage tweaking to avoid confusion. I will create sub-tasks for on this issue so that each one can be evaluated. Peace - Anthony
### Response:
1.summary: Evaluate renaming Moodle Plugins General plugins (Local) category to Local plugins (General)
description: In Moodle Plugins the category is currently called General plugins. In the Admin block it is called Local plugins. I would recommend renaming the Moodle Plugins category to Local plugins (General). Technically this should be a MDLSITE issue related to plugins; however, it appears the tracker does not different projects for subtasks.
2.summary: Consider renaming Moodle Plugins category Messaging to Message outputs
description: The category names given for Moodle plugins are usually nouns; however, Messaging is a verb and inconsistent with the name found in Moodle which is Admin->Plugins->Message outputs. If at a latter time there were various types of Messaging related plugins then I think the category should be called Messages and then have Message outputs as one of the sub-categories; however currently there are only Message output plugins.
3.summary: Consider moving and renaming Moodle Plugins Users-Enrolment category to Enrolments
description: Currently in Moodle Plugins, Enrolment is found under Users; however, in Moodle itself it is found at Admin->Plugins->Enrolments. I would recommend moving the Users-Enrolment subcategory to its own category and rename it to Enrolments (plural) to be consistent with using plural nouns to name the categories/elements for plugins. Peace - Anthony
4.summary: Consider renaming Moodle Plugins category Web service protocols to Web services (Protocols)
description: Currently, web services are found in Admin->Plugins->Web services but the Moodle Plugins category is name Web service protocols. Ideally, I think the category should be rename Web services; however, if we want to keep the language of protocols I think it should be a descriptor in parentheses. Peace - Anthony
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Group messaging improvements for 3.7
description: Epic for reviewing all the improvements coming from
| Unsolvable | 1.summary: Allow conversations to be muted/unmuted
description: New feature coming in Moodle 3.7
2.summary: The "star" switch for adding to Contacts is completely confusing, cant tell between ON and OFF modes
description: Reported in
3.summary: Support self conversations in the app
description: Support self conversations in the app. The WebServices seem to return the information fine, I was able to view the conversation in the list and write to myself. Wed have to fix some things in the app though (add the new "merge" param, treat the type 3, change some strings to match the web behaviour, etc.).
4.summary: Apply UI changes in messaging for 3.7
description: There were some changes in the UI for 3.7: Group conversations without icons are misaligned Speech bubble tail missing Search: Show only one message when no results found Search: Do not show header and result message when nothing is found Search: Highlight texts that match searched text Contacts: Make contact names bold Search: Show date stamp instead of time stamp If there is an unread message in group/private but not in favourites, that option is expanded at start. We dont do that in the app now. Messaging: improve ARIA labels to message drawer
5.summary: Allow teachers to delete messages for all users within their conversations in the app
description: Allow teachers to delete messages for all users within their conversations
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Group messaging improvements for 3.7
description: Epic for reviewing all the improvements coming from
### Response:
1.summary: Allow conversations to be muted/unmuted
description: New feature coming in Moodle 3.7
2.summary: The "star" switch for adding to Contacts is completely confusing, cant tell between ON and OFF modes
description: Reported in
3.summary: Support self conversations in the app
description: Support self conversations in the app. The WebServices seem to return the information fine, I was able to view the conversation in the list and write to myself. Wed have to fix some things in the app though (add the new "merge" param, treat the type 3, change some strings to match the web behaviour, etc.).
4.summary: Apply UI changes in messaging for 3.7
description: There were some changes in the UI for 3.7: Group conversations without icons are misaligned Speech bubble tail missing Search: Show only one message when no results found Search: Do not show header and result message when nothing is found Search: Highlight texts that match searched text Contacts: Make contact names bold Search: Show date stamp instead of time stamp If there is an unread message in group/private but not in favourites, that option is expanded at start. We dont do that in the app now. Messaging: improve ARIA labels to message drawer
5.summary: Allow teachers to delete messages for all users within their conversations in the app
description: Allow teachers to delete messages for all users within their conversations
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Tweaks & iteration based on internal testing & feedback from beta users
description: Testers can more easily find what they are looking for thanks to UI & small functionality improvements
| Unsolvable | 1.summary: Update MoodleNet UI 2.0 mockups
description: Based on the latest MoodleNet UI 2.0 mockups available on Invision, we need to work on the following: 1. Threads When a user clicks on the comment icon of a comment within a Community they should be able to reply to it to create a thread. 2. Share box This would work a bit like Mastodon, with a share box to the top left in both Communities and Collections. The workflow for Collections needs to include adding a resource (both by URL and upload) and associated metadata (taxonomy/folksonomy) 3. Liked resources tab on Profile When users like a resource within a collection its both a vote and a bookmark. For them to easily find likes-as-bookmarks, there should be space on their profile to find them. These can also be shown to other users. 4. Change filter to sort on Collection page The functionality should be to switch between sorting resources within a collection by: Most recent (default) Most liked These will be displayed after the (optional, up to 10) pinned resources 5. Collection-level discussions Were allowing discussions at the Collection level, so we need a space for those to take place, perhaps as a tab? 6. Resources can only be liked or pinned Lets remove the ability to reply or boost resources within Collections.
2.summary: Create copy for new MoodleNet UI mock-ups
description: The new MoodleNet UI mockups dont feature educational content. Lets change that before sharing outside of our team.
3.summary: Apply Moodle brand and colour scheme
description: ^Moodle Brand Style Guide .pdf ^Top bar should be Moodle orange, and sidebar (if we keep it!) charcoal grey^
4.summary: Add link to join community to add a resource message
description: From tester: "Not sure where to put this, but is joining the same as following? Should there be a Join link when looking at the list of resources (especially if you want to add a resource)?" !1EV2z6o.png!
5.summary: Remove extra link input in add resource modal
description: Link is repeated twice when adding a resource (remove box next to Link)
6.summary: Add version number to UI
description: Starting with v0.5 alpha, we should add the MoodleNet version number to the UI.
7.summary: Add tagline to MoodleNet
description: Lets add the tagline Share. Curate. Discuss to MoodleNet, starting with the next release! !MN-cohort2-tagline.png!
8.summary: Change in a few seconds to a few seconds ago in comment threads
description: A small tweak, but slightly improved grammar!
9.summary: Update home page copy
description: New copy to launch with v0.9 alpha (or before, if its ready!)
10.summary: Users should be able to reset their own password via email
description: We need transactional email set up for this.
11.summary: Update new.moodle.net
description: The existing new.moodle.net page should be updated as follows: Move section entitled "Foundational principles of MoodleNet" below section entitled "Timeline of MoodleNets development" Change background of "Test" box in the timeline from grey to Moodle orange (may also need to change text colour?) Update screenshot of MoodleNet to more recent version (e.g. one attached) !moodlenet-screenshot.png!
12.summary: Enhance discussion thread UI
description: Our current discussion UI on desktop is split into two panes, which is causing issues. Its not so intuitive to users, and we have some bugs to fix with it. The solution that bernini has proposed is similar to Telegram, Flarum, and other discussion areas. There is a single, flat structure, with users able to reply to previous comments by quoting them and @ mentioning people.
13.summary: Update login page with new graphic
description: Doug to liaise with Bryan to update graphic to right-hand side of login page. Perhaps remove the word Moodlenet and mention that its for educators?
14.summary: Move new community button from top bar
description: The new community button should go elsewhere - perhaps in the first result when clicking on all communities?
15.summary: Default tab for collections should be Resources
description: !default-tab-collections.png|width=800!
16.summary: Improve accessibility in light theme
description: The light theme features orange text on a white background, which isnt great for accessibility.
17.summary: Add context to comments in profile view
description: Im not sure how easy this is to fix, but it would be nice if on the profile view users could see the context of comments. In the example below, the context is within a collection which is part of a community. !comment context.png|width=501,height=309!
18.summary: Default tab for communities should be collections
description: Right now, the default tab for communities is timeline. This should be collections instead.
19.summary: Tweak the new.moodle.net homepage
description: Move timeline up Highlight current status
20.summary: Place licence and copyright information at the top of every source code file
description: We need to add copyright information in a file within our GitLab repo: MoodleNet Copyright 2019 Moodle Pty Ltd Portions of this file are derived from CommonsPub: Copyright 2019 CommonsPub Authors
21.summary: Update featured communities and collections for v0.9.3
description: Please update the featured communities to: The Lounge - El Sal n - H5P for Language Learning - Moodle Developers - Mountain Leaders - Moodle HackFest / DevJam - The featured collections should be: Recursos electr nicos - Assessment - Badge basics - Getting started - Aplicaciones, software.. - Course Design Ideas -
22.summary: Disable discussion message box until user joins community
description: Tester: "Ive been caught out a couple of times when starting a thread in a community. Having composed, previewed and post a not authorized alert pops up. I think the start thread option should be disabled until the user joins to prevent this."
23.summary: Thread preview button ends up a long way down the screen if there are lots of threads
description: Tester: "Particularly noticeable in the lounge when starting a new thread the preview button to post is a long scroll to the bottom"
24.summary: On Discussion > Start new thread shift cursor focus to message box
description: Tester: "Would be nice when you click Start new thread that the user cursor is focused in the compose box rather than an extra click"
25.summary: List popular communities/collections
description: Need 2 endpoints to get list of popular communities or collections. Question is how do we rank them?
26.summary: Show error messages in nicer way than browser popup
description: Show error messages in nicer way than browser popup
27.summary: Show appropriate error message for failed requests
description: A request to the server can fail for several external reasons, drop connections, timeouts, internal server errors. We have to handle them showing a message to the user. I just tested with my wifi turned off, and the console contains "Error: Network error: Failed to fetch" but nothing is shown to the user. Also the submit button on forms is disabled and so I cant try again.
28.summary: Update copy of GraphQL errors shown to users
description: GraphQL errors are explained in this issue: The easiest way to implement is just presenting the message to the user, but can be customized as needed. More errors examples in:
29.summary: View instance timeline
description: Building on | users should be able to see a timeline of everything on their instance. This has potential performance implications which we need to consider, so bernini should work closely with alexcastano to explore.
30.summary: Create new MoodleNet overview slide deck
description: We havent updated the MoodleNet non-technical overview slide deck since December. In preparation for the MoodleMoot presentation in April, we should have a standard slide deck to go on the wiki.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Tweaks & iteration based on internal testing & feedback from beta users
description: Testers can more easily find what they are looking for thanks to UI & small functionality improvements
### Response:
1.summary: Update MoodleNet UI 2.0 mockups
description: Based on the latest MoodleNet UI 2.0 mockups available on Invision, we need to work on the following: 1. Threads When a user clicks on the comment icon of a comment within a Community they should be able to reply to it to create a thread. 2. Share box This would work a bit like Mastodon, with a share box to the top left in both Communities and Collections. The workflow for Collections needs to include adding a resource (both by URL and upload) and associated metadata (taxonomy/folksonomy) 3. Liked resources tab on Profile When users like a resource within a collection its both a vote and a bookmark. For them to easily find likes-as-bookmarks, there should be space on their profile to find them. These can also be shown to other users. 4. Change filter to sort on Collection page The functionality should be to switch between sorting resources within a collection by: Most recent (default) Most liked These will be displayed after the (optional, up to 10) pinned resources 5. Collection-level discussions Were allowing discussions at the Collection level, so we need a space for those to take place, perhaps as a tab? 6. Resources can only be liked or pinned Lets remove the ability to reply or boost resources within Collections.
2.summary: Create copy for new MoodleNet UI mock-ups
description: The new MoodleNet UI mockups dont feature educational content. Lets change that before sharing outside of our team.
3.summary: Apply Moodle brand and colour scheme
description: ^Moodle Brand Style Guide .pdf ^Top bar should be Moodle orange, and sidebar (if we keep it!) charcoal grey^
4.summary: Add link to join community to add a resource message
description: From tester: "Not sure where to put this, but is joining the same as following? Should there be a Join link when looking at the list of resources (especially if you want to add a resource)?" !1EV2z6o.png!
5.summary: Remove extra link input in add resource modal
description: Link is repeated twice when adding a resource (remove box next to Link)
6.summary: Add version number to UI
description: Starting with v0.5 alpha, we should add the MoodleNet version number to the UI.
7.summary: Add tagline to MoodleNet
description: Lets add the tagline Share. Curate. Discuss to MoodleNet, starting with the next release! !MN-cohort2-tagline.png!
8.summary: Change in a few seconds to a few seconds ago in comment threads
description: A small tweak, but slightly improved grammar!
9.summary: Update home page copy
description: New copy to launch with v0.9 alpha (or before, if its ready!)
10.summary: Users should be able to reset their own password via email
description: We need transactional email set up for this.
11.summary: Update new.moodle.net
description: The existing new.moodle.net page should be updated as follows: Move section entitled "Foundational principles of MoodleNet" below section entitled "Timeline of MoodleNets development" Change background of "Test" box in the timeline from grey to Moodle orange (may also need to change text colour?) Update screenshot of MoodleNet to more recent version (e.g. one attached) !moodlenet-screenshot.png!
12.summary: Enhance discussion thread UI
description: Our current discussion UI on desktop is split into two panes, which is causing issues. Its not so intuitive to users, and we have some bugs to fix with it. The solution that bernini has proposed is similar to Telegram, Flarum, and other discussion areas. There is a single, flat structure, with users able to reply to previous comments by quoting them and @ mentioning people.
13.summary: Update login page with new graphic
description: Doug to liaise with Bryan to update graphic to right-hand side of login page. Perhaps remove the word Moodlenet and mention that its for educators?
14.summary: Move new community button from top bar
description: The new community button should go elsewhere - perhaps in the first result when clicking on all communities?
15.summary: Default tab for collections should be Resources
description: !default-tab-collections.png|width=800!
16.summary: Improve accessibility in light theme
description: The light theme features orange text on a white background, which isnt great for accessibility.
17.summary: Add context to comments in profile view
description: Im not sure how easy this is to fix, but it would be nice if on the profile view users could see the context of comments. In the example below, the context is within a collection which is part of a community. !comment context.png|width=501,height=309!
18.summary: Default tab for communities should be collections
description: Right now, the default tab for communities is timeline. This should be collections instead.
19.summary: Tweak the new.moodle.net homepage
description: Move timeline up Highlight current status
20.summary: Place licence and copyright information at the top of every source code file
description: We need to add copyright information in a file within our GitLab repo: MoodleNet Copyright 2019 Moodle Pty Ltd Portions of this file are derived from CommonsPub: Copyright 2019 CommonsPub Authors
21.summary: Update featured communities and collections for v0.9.3
description: Please update the featured communities to: The Lounge - El Sal n - H5P for Language Learning - Moodle Developers - Mountain Leaders - Moodle HackFest / DevJam - The featured collections should be: Recursos electr nicos - Assessment - Badge basics - Getting started - Aplicaciones, software.. - Course Design Ideas -
22.summary: Disable discussion message box until user joins community
description: Tester: "Ive been caught out a couple of times when starting a thread in a community. Having composed, previewed and post a not authorized alert pops up. I think the start thread option should be disabled until the user joins to prevent this."
23.summary: Thread preview button ends up a long way down the screen if there are lots of threads
description: Tester: "Particularly noticeable in the lounge when starting a new thread the preview button to post is a long scroll to the bottom"
24.summary: On Discussion > Start new thread shift cursor focus to message box
description: Tester: "Would be nice when you click Start new thread that the user cursor is focused in the compose box rather than an extra click"
25.summary: List popular communities/collections
description: Need 2 endpoints to get list of popular communities or collections. Question is how do we rank them?
26.summary: Show error messages in nicer way than browser popup
description: Show error messages in nicer way than browser popup
27.summary: Show appropriate error message for failed requests
description: A request to the server can fail for several external reasons, drop connections, timeouts, internal server errors. We have to handle them showing a message to the user. I just tested with my wifi turned off, and the console contains "Error: Network error: Failed to fetch" but nothing is shown to the user. Also the submit button on forms is disabled and so I cant try again.
28.summary: Update copy of GraphQL errors shown to users
description: GraphQL errors are explained in this issue: The easiest way to implement is just presenting the message to the user, but can be customized as needed. More errors examples in:
29.summary: View instance timeline
description: Building on | users should be able to see a timeline of everything on their instance. This has potential performance implications which we need to consider, so bernini should work closely with alexcastano to explore.
30.summary: Create new MoodleNet overview slide deck
description: We havent updated the MoodleNet non-technical overview slide deck since December. In preparation for the MoodleMoot presentation in April, we should have a standard slide deck to go on the wiki.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Collection of messaging issues to be worked on for 3.7
description: Issues to be collated here include those related to further improving: Accessibility Performance (caching, improving search) UI tweaks etc
| Unsolvable | 1.summary: Messaging: Improve performance of get_conversations via caching
description: Add cache wherever needed or search for alternatives to optimise the performance for the messaging after adding the group messaging features.
2.summary: Allow creation of group conversations from the auto-create groups edit page and from the import
description: Add the new option "Group messaging" in the auto-create group form in order to allow the creation of group conversations as the same way that is done in . Add support to the enablemessaging field from the import groups tool.
3.summary: Remove old messaging UI and replace with new widget
description: Unfortunately the old messaging UI needed to stay for the 3.6 release. By default landing on the message/index.php page will simply open the new messaging drawer except for in one specific case where a person with sufficient capabilities (i.e. admin) is able to view the conversation between two other users. This functionality can be access from only one place in Moodle which is from the event logs in the site admin. Clicking on the related URL for a messaging log (for example blocking a user or deleting a message) will take the admin to the old messaging interface and load up that conversation. We need to determine what we want to do with that functionality, either remove it or implement it in the new messaging UI. Once the decision is made we can remove the old UI. Dont forget that we need to also remove all of the related CSS, templates in both themes when removing the old UI. Update (03 Jan 2019): Rather than remove the old UI we will also embed the new messaging UI on the old index.php page. Giving users an option to use messaging with the drawer or this page which will provide a wider view with more space to read and write messages. There will have to be a link on the new messaging drawer to allow people to navigate to the full messages/index.php page.
4.summary: Accessibility improvements to message drawer
description: Improve accessibility of the new message drawer E.g. Add aria labels for cancel edit message button (the little cross when selecting messages) Add better aria labels to the menus in messaging (simply saying "Info" doesnt give the user any context) Add better contrast levels to hovering of messages or perhaps even change how that works Keyboard navigation of messages (up/down) messages can be focused when a dialogue is open
5.summary: Messaging: make a decision on the use of html in messages
description: We need to make a decision about how to or whether to handle this, moving forward. We might be better off disabling it. I believe this was a legacy function, meaning we will likely have old messages which contain html - this also needs consideration. Update 10 Jan 2018: We dont want to allow HTML in messages. We can retain the bulk message formatting option for teachers and admin and provide a capability to those roles for this purpose.
6.summary: Add new setting page for messaging related settings
description: Currently messaging related settings sit under Site administration > Advanced features. This should not be defined as an Advanced feature and should become common use in any Moodle site. We should define a unique location for these settings in the main Site Administration category called Messaging. We should add all Messaging related settings to a new page called Messaging settings in the Messaging category. The content from the Manage message outputs page page should go in a new Notification settings page with all the content from Default message outputs. Note that the eye icon for enabling the message outputs (Manage message outputs page) should be a checkbox to make clear it enables/disables rather than just show or hides notification settings for the user. Links to messaging plugins settings page should be moved from Plugin admin page to the new Messaging category in the main site administration page.
7.summary: Provide a means for message processors to identify and handle group messages
description: As discussed on , wed like a formal way for processors to be allowed to opt in to processing of (or be made aware of) messages sent to group conversations. Currently, as per , no processors are called at all when this type of message is sent. This is excluded, based on conversation type, in the message/manager, and was done to avoid huge numbers of emails, sms, etc being sent out to all recipients in a group conversation every time a single message is sent. Ideally, wed want a way for processors to be aware of the type of the conversation to which the message is being sent, and make their own decisions based on that. At the moment, processors can only see the convid in the eventdata, and would then need to check the conversation type and make assertions based on that. Some ideas we threw around just now were: - new message provider in lib/db/messages (might be a lot of work as instantmessage is referenced a fair bit and its state on/off is tied to the state of the messaging feature itself) - admin config for message processors, allowing admins to specify whether or not a given processor handles messages to groups. Wed need to update the core outputs too as part of this work.
8.summary: Improve appearance of the messaging app on the index.php page
description: was responsible for removing a lot of the old code (including the old UI) which was replaced with the drawer, albeit on a very large page. We need to go through and make it look nice.
9.summary: Messaging: Add support for personal space
description: For personal space in messaging, a number of things are required: - Sending a bulk message from the course or site to ones self must also trigger the email processor for that sender. Currently (3.6 ) it does not. This is in the message manager. - personal space conversations should be returned by the relevant APIs and web services. - personal space conversations should be displayed in the UI - A user should be able to reply to a personal space conversations - (as per 3.5 and older) a user should not be able to initiate a personal space conversation with themselves via the messaging UI. It can be achieved only via the bulk messaging. We also need to make sure that options like "Block" etc - which dont really make sense when talking about the current user - are removed from the UI.
10.summary: Site default for "Press on enter"
description: I love having "Press on Enter" but can we have am admin setting to set the default value please?
11.summary: Search: Highlight texts that match searched text
description: Highlight texts that match searched text !highlighted text.png|thumbnail!
12.summary: Allow conversations to be muted/unmuted
description: This would allow users to mute busy conversations they may not want to be notified of. There is still the hack in core if ($conv->type == \core_message\api::MESSAGE_CONVERSATION_TYPE_INDIVIDUAL) in lib/classes/message/manager.php that will prevent notifications for group messages, this will be dealt with in .
13.summary: Clean HTML in messages
description: We need to apply the Moodle standard trusttext approach to messages text to have the certainty that the text of the messages was cleaned as forum posts or entries and comments in the glossary. _Docs_: _Note_: we dont need that cleaning on input if the contents arent editable. And at the moment, it wont. Maybe, in the future, it could be a great feature to add the chance to edit your messages. To sum up, this a summary description table about the use of trusttext in messages: +Individual/Group Conversation from messaging (FORMAT_MOODLE)+ || ||trusttext enabled ||trusttext disabled || |Text to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes| +Bulk User Action (FORMAT_HTML)+ || ||trusttext enabled ||trusttext disabled || |Clean Text|No |Yes| |Moodle Filters|Yes|Yes| +Bulk User Action (FORMAT_MARKDOWN)+ || ||trusttext enabled ||trusttext disabled || |Markdown to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes| +Send a message from Participation List (FORMAT_MOODLE)+ Currently, the messages sent through the list of participants are individual conversations and therefore the context is system. || ||trusttext enabled ||trusttext disabled || |Text to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes|
14.summary: Messaging: timestamp should include days and years in main conversations list
description: Like "Monday, 11th March 2019". Update: Spoke to UX and the outcome was: For conversations listed on the main view (Starred, Group, Private), we want to: - Display the time in the format "14:18" for conversations having a message posted today. - Display the date in the format "29/01/19" for conversations older than today. This likely means we cant simply use the strftimetime24 in the template and must preformat the dates before rendering the template
15.summary: Messaging: Allow teachers to delete messages for all users within their conversations
description: Teachers should be given a capability which allows them to delete a message for all users, regardless of who posted the message. This might be used to remove inappropriate content from group chats, for example. This should not give teachers the right to view conversations/messages which they are not a part of. Some notes around a possible solution: Deletion controls might be a third option (alongside "Delete" and "Cancel") in the confirmation box presented to a teacher when deleting a message. Web services need expansion to support delete for all notion. Currently, we dont have a means to rescind a message already fetched and loaded into the UI. We need to consider how this might be achieved, however, that should be a separate issue, as it will likely be more involved than simply getting the message deletion working.
16.summary: Improve the group messaging digest email by including images
description: The original mock-up includes a user and group image (see attached image). I have been trying to utilise with no luck. The reason - will prevent a token from working if it is created with a userid of 0 (which will happen in a scheduled task). I dont see how it is possible from a scheduled task to avoid this. Whenever you call moodle_url::make_pluginfile_url() and specify you want to create a token it calls which then creates a token using $USER->id if it doesnt exist (see The user already exists, but there is no token, so when creating the URL for them (see snippets below) it automatically creates a token (with userid 0 since its from a scheduled task where $USER->id is 0 (there is no option to pass a user id)). Frankly, I am not sure what is happening in forum to prevent this, but it is late and I have been staring at code for a while. My guess is it sets up the tokens before it generates the URLs (which seems counter-intuitive looking at the API which leans towards creating the token on the fly). Perhaps what I am trying to achieve is not possible. I could hack the $USER->id but obviously that is not an acceptable option. code:php $group = new \stdClass(); $group->id = $conversation->groupid; $group->picture = $conversation->picture; $group->hidepicture = $conversation->hidepicture; $group->courseid = $conversation->courseid; $grouppictureurl = $renderer->image_url(g/g1)->out(false); // Default image. if ($url = get_group_picture_url($group, $group->courseid, false, true)) $grouppictureurl = $url->out(false); code code:php $user = new \stdClass(); $usernamefields = explode(, ,\user_picture::fields()); foreach ($usernamefields as $usernamefield) $user->$usernamefield = $message->$usernamefield; $user->id = $message->useridfrom; $userpicture = new \user_picture($user); $userpicture->includetoken = true; $userpictureurl = $userpicture->get_url($PAGE)->out(false); code
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Collection of messaging issues to be worked on for 3.7
description: Issues to be collated here include those related to further improving: Accessibility Performance (caching, improving search) UI tweaks etc
### Response:
1.summary: Messaging: Improve performance of get_conversations via caching
description: Add cache wherever needed or search for alternatives to optimise the performance for the messaging after adding the group messaging features.
2.summary: Allow creation of group conversations from the auto-create groups edit page and from the import
description: Add the new option "Group messaging" in the auto-create group form in order to allow the creation of group conversations as the same way that is done in . Add support to the enablemessaging field from the import groups tool.
3.summary: Remove old messaging UI and replace with new widget
description: Unfortunately the old messaging UI needed to stay for the 3.6 release. By default landing on the message/index.php page will simply open the new messaging drawer except for in one specific case where a person with sufficient capabilities (i.e. admin) is able to view the conversation between two other users. This functionality can be access from only one place in Moodle which is from the event logs in the site admin. Clicking on the related URL for a messaging log (for example blocking a user or deleting a message) will take the admin to the old messaging interface and load up that conversation. We need to determine what we want to do with that functionality, either remove it or implement it in the new messaging UI. Once the decision is made we can remove the old UI. Dont forget that we need to also remove all of the related CSS, templates in both themes when removing the old UI. Update (03 Jan 2019): Rather than remove the old UI we will also embed the new messaging UI on the old index.php page. Giving users an option to use messaging with the drawer or this page which will provide a wider view with more space to read and write messages. There will have to be a link on the new messaging drawer to allow people to navigate to the full messages/index.php page.
4.summary: Accessibility improvements to message drawer
description: Improve accessibility of the new message drawer E.g. Add aria labels for cancel edit message button (the little cross when selecting messages) Add better aria labels to the menus in messaging (simply saying "Info" doesnt give the user any context) Add better contrast levels to hovering of messages or perhaps even change how that works Keyboard navigation of messages (up/down) messages can be focused when a dialogue is open
5.summary: Messaging: make a decision on the use of html in messages
description: We need to make a decision about how to or whether to handle this, moving forward. We might be better off disabling it. I believe this was a legacy function, meaning we will likely have old messages which contain html - this also needs consideration. Update 10 Jan 2018: We dont want to allow HTML in messages. We can retain the bulk message formatting option for teachers and admin and provide a capability to those roles for this purpose.
6.summary: Add new setting page for messaging related settings
description: Currently messaging related settings sit under Site administration > Advanced features. This should not be defined as an Advanced feature and should become common use in any Moodle site. We should define a unique location for these settings in the main Site Administration category called Messaging. We should add all Messaging related settings to a new page called Messaging settings in the Messaging category. The content from the Manage message outputs page page should go in a new Notification settings page with all the content from Default message outputs. Note that the eye icon for enabling the message outputs (Manage message outputs page) should be a checkbox to make clear it enables/disables rather than just show or hides notification settings for the user. Links to messaging plugins settings page should be moved from Plugin admin page to the new Messaging category in the main site administration page.
7.summary: Provide a means for message processors to identify and handle group messages
description: As discussed on , wed like a formal way for processors to be allowed to opt in to processing of (or be made aware of) messages sent to group conversations. Currently, as per , no processors are called at all when this type of message is sent. This is excluded, based on conversation type, in the message/manager, and was done to avoid huge numbers of emails, sms, etc being sent out to all recipients in a group conversation every time a single message is sent. Ideally, wed want a way for processors to be aware of the type of the conversation to which the message is being sent, and make their own decisions based on that. At the moment, processors can only see the convid in the eventdata, and would then need to check the conversation type and make assertions based on that. Some ideas we threw around just now were: - new message provider in lib/db/messages (might be a lot of work as instantmessage is referenced a fair bit and its state on/off is tied to the state of the messaging feature itself) - admin config for message processors, allowing admins to specify whether or not a given processor handles messages to groups. Wed need to update the core outputs too as part of this work.
8.summary: Improve appearance of the messaging app on the index.php page
description: was responsible for removing a lot of the old code (including the old UI) which was replaced with the drawer, albeit on a very large page. We need to go through and make it look nice.
9.summary: Messaging: Add support for personal space
description: For personal space in messaging, a number of things are required: - Sending a bulk message from the course or site to ones self must also trigger the email processor for that sender. Currently (3.6 ) it does not. This is in the message manager. - personal space conversations should be returned by the relevant APIs and web services. - personal space conversations should be displayed in the UI - A user should be able to reply to a personal space conversations - (as per 3.5 and older) a user should not be able to initiate a personal space conversation with themselves via the messaging UI. It can be achieved only via the bulk messaging. We also need to make sure that options like "Block" etc - which dont really make sense when talking about the current user - are removed from the UI.
10.summary: Site default for "Press on enter"
description: I love having "Press on Enter" but can we have am admin setting to set the default value please?
11.summary: Search: Highlight texts that match searched text
description: Highlight texts that match searched text !highlighted text.png|thumbnail!
12.summary: Allow conversations to be muted/unmuted
description: This would allow users to mute busy conversations they may not want to be notified of. There is still the hack in core if ($conv->type == \core_message\api::MESSAGE_CONVERSATION_TYPE_INDIVIDUAL) in lib/classes/message/manager.php that will prevent notifications for group messages, this will be dealt with in .
13.summary: Clean HTML in messages
description: We need to apply the Moodle standard trusttext approach to messages text to have the certainty that the text of the messages was cleaned as forum posts or entries and comments in the glossary. _Docs_: _Note_: we dont need that cleaning on input if the contents arent editable. And at the moment, it wont. Maybe, in the future, it could be a great feature to add the chance to edit your messages. To sum up, this a summary description table about the use of trusttext in messages: +Individual/Group Conversation from messaging (FORMAT_MOODLE)+ || ||trusttext enabled ||trusttext disabled || |Text to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes| +Bulk User Action (FORMAT_HTML)+ || ||trusttext enabled ||trusttext disabled || |Clean Text|No |Yes| |Moodle Filters|Yes|Yes| +Bulk User Action (FORMAT_MARKDOWN)+ || ||trusttext enabled ||trusttext disabled || |Markdown to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes| +Send a message from Participation List (FORMAT_MOODLE)+ Currently, the messages sent through the list of participants are individual conversations and therefore the context is system. || ||trusttext enabled ||trusttext disabled || |Text to html|Yes|Yes| |Clean Text|No|Yes| |Moodle Filters|Yes|Yes|
14.summary: Messaging: timestamp should include days and years in main conversations list
description: Like "Monday, 11th March 2019". Update: Spoke to UX and the outcome was: For conversations listed on the main view (Starred, Group, Private), we want to: - Display the time in the format "14:18" for conversations having a message posted today. - Display the date in the format "29/01/19" for conversations older than today. This likely means we cant simply use the strftimetime24 in the template and must preformat the dates before rendering the template
15.summary: Messaging: Allow teachers to delete messages for all users within their conversations
description: Teachers should be given a capability which allows them to delete a message for all users, regardless of who posted the message. This might be used to remove inappropriate content from group chats, for example. This should not give teachers the right to view conversations/messages which they are not a part of. Some notes around a possible solution: Deletion controls might be a third option (alongside "Delete" and "Cancel") in the confirmation box presented to a teacher when deleting a message. Web services need expansion to support delete for all notion. Currently, we dont have a means to rescind a message already fetched and loaded into the UI. We need to consider how this might be achieved, however, that should be a separate issue, as it will likely be more involved than simply getting the message deletion working.
16.summary: Improve the group messaging digest email by including images
description: The original mock-up includes a user and group image (see attached image). I have been trying to utilise with no luck. The reason - will prevent a token from working if it is created with a userid of 0 (which will happen in a scheduled task). I dont see how it is possible from a scheduled task to avoid this. Whenever you call moodle_url::make_pluginfile_url() and specify you want to create a token it calls which then creates a token using $USER->id if it doesnt exist (see The user already exists, but there is no token, so when creating the URL for them (see snippets below) it automatically creates a token (with userid 0 since its from a scheduled task where $USER->id is 0 (there is no option to pass a user id)). Frankly, I am not sure what is happening in forum to prevent this, but it is late and I have been staring at code for a while. My guess is it sets up the tokens before it generates the URLs (which seems counter-intuitive looking at the API which leans towards creating the token on the fly). Perhaps what I am trying to achieve is not possible. I could hack the $USER->id but obviously that is not an acceptable option. code:php $group = new \stdClass(); $group->id = $conversation->groupid; $group->picture = $conversation->picture; $group->hidepicture = $conversation->hidepicture; $group->courseid = $conversation->courseid; $grouppictureurl = $renderer->image_url(g/g1)->out(false); // Default image. if ($url = get_group_picture_url($group, $group->courseid, false, true)) $grouppictureurl = $url->out(false); code code:php $user = new \stdClass(); $usernamefields = explode(, ,\user_picture::fields()); foreach ($usernamefields as $usernamefield) $user->$usernamefield = $message->$usernamefield; $user->id = $message->useridfrom; $userpicture = new \user_picture($user); $userpicture->includetoken = true; $userpictureurl = $userpicture->get_url($PAGE)->out(false); code
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Behat tests for the Moodle App
description: Epic for adding Behat tests to the Moodle app
| Unsolvable | 1.summary: Behat tests for the forum
description: Add Behat tests to the forum to cover: Reply a post offline New discussion offline Edit a not sent reply offline Edit a not sent new discussion offline Edit a forum post (only online) Delete a forum post (only online) Sync Forum Auto-sync forum Prefetch forum Add/view ratings Star and pin discussions
2.summary: Behat tests for the choice
description: Add Behat tests to the choice to cover: Answer a choice (multi or single, update answer) Delete choice View results Answer and change answer offline Sync choice Auto-sync choice Prefetch
3.summary: Behat tests for the survey
description: Add Behat tests to the survey to cover: Answer a survey View results Answer survey offline Sync survey Auto-sync survey Prefetch
4.summary: Behat tests for the courses
description: Add Behat tests to the courses to cover: "Dashboard" tab displayed in >= 3.3 sites See my courses Search for a course Links to actions in Timeline work for teachers/students
5.summary: Behat tests for the course
description: Add Behat tests to the course to cover: View course contents View section contents Navigation between sections using the bottom arrows Self enrol Guest access View blocks bellow/beside contents also when All sections selected
6.summary: Behat tests for the messages
description: Add Behat tests to the messages to cover: View recent conversations and contacts Search users Send/receive messages in existing conversations User profile: send message, add/remove contact Send message offline Auto-sync messages Search for messages Star/Unstar User blocking feature Mute Unmute conversations Self conversations
7.summary: Behat tests for the glossary
description: Add Behat tests to the glossary to cover: View a glossary and its terms Change filters (include search) See comments Prefetch Sync Add/view ratings
8.summary: Behat tests for the comments
description: Add Behat tests to the Comments to cover: Add comments Add comments offline Delete comments Delete comments offline Sync comments
9.summary: Behat tests for the assignment
description: Add Behat tests to the Assignment to cover: View assign description, attachments, due date, ... View list of student submissions (as teacher) View own submission or student submission Edit/Add submission (online text) Submit for grading Add new attempt from previous submission Add submission offline (online text) Edit an offline submission before synchronizing it Submit for grading offline Sync submissions
10.summary: Behat tests for the quiz
description: Add Behat tests to the Quiz to cover: View a quiz entry page (attempts, status, etc.) Attempt a quiz (all question types) Submit a quiz Review a quiz attempt
11.summary: Behat tests for the chat
description: Add Behat tests to the Chat to cover: Receive and send messages See connected users, beep and talk to Past sessions shown for >=3.5
12.summary: Behat tests for the login
description: Add Behat tests to the login to cover: Add a non existing site Delete a site Require minium version of the app for a site Site name in displayed when adding a new site
13.summary: Update behat tests for the Moodle App
description: Tests are failing, some because of the changes in the activity chooser and some because of the changes on the app. Update is needed.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Behat tests for the Moodle App
description: Epic for adding Behat tests to the Moodle app
### Response:
1.summary: Behat tests for the forum
description: Add Behat tests to the forum to cover: Reply a post offline New discussion offline Edit a not sent reply offline Edit a not sent new discussion offline Edit a forum post (only online) Delete a forum post (only online) Sync Forum Auto-sync forum Prefetch forum Add/view ratings Star and pin discussions
2.summary: Behat tests for the choice
description: Add Behat tests to the choice to cover: Answer a choice (multi or single, update answer) Delete choice View results Answer and change answer offline Sync choice Auto-sync choice Prefetch
3.summary: Behat tests for the survey
description: Add Behat tests to the survey to cover: Answer a survey View results Answer survey offline Sync survey Auto-sync survey Prefetch
4.summary: Behat tests for the courses
description: Add Behat tests to the courses to cover: "Dashboard" tab displayed in >= 3.3 sites See my courses Search for a course Links to actions in Timeline work for teachers/students
5.summary: Behat tests for the course
description: Add Behat tests to the course to cover: View course contents View section contents Navigation between sections using the bottom arrows Self enrol Guest access View blocks bellow/beside contents also when All sections selected
6.summary: Behat tests for the messages
description: Add Behat tests to the messages to cover: View recent conversations and contacts Search users Send/receive messages in existing conversations User profile: send message, add/remove contact Send message offline Auto-sync messages Search for messages Star/Unstar User blocking feature Mute Unmute conversations Self conversations
7.summary: Behat tests for the glossary
description: Add Behat tests to the glossary to cover: View a glossary and its terms Change filters (include search) See comments Prefetch Sync Add/view ratings
8.summary: Behat tests for the comments
description: Add Behat tests to the Comments to cover: Add comments Add comments offline Delete comments Delete comments offline Sync comments
9.summary: Behat tests for the assignment
description: Add Behat tests to the Assignment to cover: View assign description, attachments, due date, ... View list of student submissions (as teacher) View own submission or student submission Edit/Add submission (online text) Submit for grading Add new attempt from previous submission Add submission offline (online text) Edit an offline submission before synchronizing it Submit for grading offline Sync submissions
10.summary: Behat tests for the quiz
description: Add Behat tests to the Quiz to cover: View a quiz entry page (attempts, status, etc.) Attempt a quiz (all question types) Submit a quiz Review a quiz attempt
11.summary: Behat tests for the chat
description: Add Behat tests to the Chat to cover: Receive and send messages See connected users, beep and talk to Past sessions shown for >=3.5
12.summary: Behat tests for the login
description: Add Behat tests to the login to cover: Add a non existing site Delete a site Require minium version of the app for a site Site name in displayed when adding a new site
13.summary: Update behat tests for the Moodle App
description: Tests are failing, some because of the changes in the activity chooser and some because of the changes on the app. Update is needed.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Prepare workshop module for the mobile app
description: In this epic Im listing all the new Web Services and API changes to be applied in the Workshop module
| Unsolvable | 1.summary: New Web Service mod_workshop_get_workshops_by_courses
description: To retrieve all the workshop in the given courses
2.summary: New Web Service mod_workshop_view_workshop
description: To mark view completed and launch the mod viewed event
3.summary: New Web Service mod_workshop_view_submission
description: To be called when a submission is viewed
4.summary: New Web Service mod_workshop_get_access_information
description: To retrieve the current user status in a given workshop before starting or continuing it. With this information, the app will be able to print the appropriate information regarding the workshop status. It will also return the user capabilities (whether he can submit, per-assess, switch phases, etc..) This function will also return the different subplugins used for allocation, assesstment form and for final grading (the app will support only core ones)
5.summary: New Web Service mod_workshop_get_submissions
description: To retrieve all the existing submissions in a workshop (or the specified user one)
6.summary: New Web Service mod_workshop_get_submission
description: To retrieve a single submission by id.
7.summary: New Web Service mod_workshop_add_submission
description: To add a new submission
8.summary: New Web Service mod_workshop_delete_submission
description: To delete a submission by id.
9.summary: New Web Service mod_workshop_update_submission
description: To update an existing submission
10.summary: New Web Service mod_workshop_get_submission_assessments
description: To retrieve all the assessments done in the submission
11.summary: New Web Service mod_workshop_get_assessment
description: To retrieve an assessment by id
12.summary: New Web Service mod_workshop_get_assessment_form_definition
description: To retrieve the assessment form definition (data required to be able to display the assessment form)
13.summary: New Web Service mod_workshop_add_assessment
description: To add a new assessment
14.summary: New Web Service mod_workshop_update_assessment
description: To update an existing assessment
15.summary: New Web Service mod_workshop_get_grades
description: To return the assessment and submission grade for the given user.
16.summary: New Web Service mod_workshop_evaluate_assessment
description: Used by teachers to add the assessment grade, feedback, etc...
17.summary: New Web Service mod_workshop_get_grades_report
description: To retrieve the assessment grades report
18.summary: Implement the check_updates callback in the workshop module
description: We need this callback so the mobile app is able to check for updates in the workshop module in order to update the download/update status of the activity in the course.
19.summary: New Web Service mod_workshop_get_user_plan
description: Return the planner information for the given user
20.summary: New Web Service mod_workshop_get_reviewer_assessments (originally mod_workshop_get_user_assessments)
description: Return all the assessments assigned or done by the given user.
21.summary: New WS mod_workshop_evaluate_submission
description: Used by teachers to evaluate students submissions, provide feedback or override the submission grade
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Prepare workshop module for the mobile app
description: In this epic Im listing all the new Web Services and API changes to be applied in the Workshop module
### Response:
1.summary: New Web Service mod_workshop_get_workshops_by_courses
description: To retrieve all the workshop in the given courses
2.summary: New Web Service mod_workshop_view_workshop
description: To mark view completed and launch the mod viewed event
3.summary: New Web Service mod_workshop_view_submission
description: To be called when a submission is viewed
4.summary: New Web Service mod_workshop_get_access_information
description: To retrieve the current user status in a given workshop before starting or continuing it. With this information, the app will be able to print the appropriate information regarding the workshop status. It will also return the user capabilities (whether he can submit, per-assess, switch phases, etc..) This function will also return the different subplugins used for allocation, assesstment form and for final grading (the app will support only core ones)
5.summary: New Web Service mod_workshop_get_submissions
description: To retrieve all the existing submissions in a workshop (or the specified user one)
6.summary: New Web Service mod_workshop_get_submission
description: To retrieve a single submission by id.
7.summary: New Web Service mod_workshop_add_submission
description: To add a new submission
8.summary: New Web Service mod_workshop_delete_submission
description: To delete a submission by id.
9.summary: New Web Service mod_workshop_update_submission
description: To update an existing submission
10.summary: New Web Service mod_workshop_get_submission_assessments
description: To retrieve all the assessments done in the submission
11.summary: New Web Service mod_workshop_get_assessment
description: To retrieve an assessment by id
12.summary: New Web Service mod_workshop_get_assessment_form_definition
description: To retrieve the assessment form definition (data required to be able to display the assessment form)
13.summary: New Web Service mod_workshop_add_assessment
description: To add a new assessment
14.summary: New Web Service mod_workshop_update_assessment
description: To update an existing assessment
15.summary: New Web Service mod_workshop_get_grades
description: To return the assessment and submission grade for the given user.
16.summary: New Web Service mod_workshop_evaluate_assessment
description: Used by teachers to add the assessment grade, feedback, etc...
17.summary: New Web Service mod_workshop_get_grades_report
description: To retrieve the assessment grades report
18.summary: Implement the check_updates callback in the workshop module
description: We need this callback so the mobile app is able to check for updates in the workshop module in order to update the download/update status of the activity in the course.
19.summary: New Web Service mod_workshop_get_user_plan
description: Return the planner information for the given user
20.summary: New Web Service mod_workshop_get_reviewer_assessments (originally mod_workshop_get_user_assessments)
description: Return all the assessments assigned or done by the given user.
21.summary: New WS mod_workshop_evaluate_submission
description: Used by teachers to evaluate students submissions, provide feedback or override the submission grade
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.2.2 upgrade
description: Moodle 3.2.2 scheduled release date: 13 March 2017
| Unsolvable | 1.summary: Upgrade moodle.org to 3.2.2
description:
2.summary: Upgrade learn.moodle.net to 3.2.2
description:
3.summary: Upgrade lang.moodle.org to 3.2.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.2.2
description:
5.summary: Upgrade demo.moodle.net to 3.2.2
description:
6.summary: Upgrade dev.moodle.org to 3.2.2
description:
7.summary: Upgrade moodle.net to 3.2.2
description:
8.summary: Upgrade download.moodle.org to 3.2.2
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.2.2 upgrade
description: Moodle 3.2.2 scheduled release date: 13 March 2017
### Response:
1.summary: Upgrade moodle.org to 3.2.2
description:
2.summary: Upgrade learn.moodle.net to 3.2.2
description:
3.summary: Upgrade lang.moodle.org to 3.2.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.2.2
description:
5.summary: Upgrade demo.moodle.net to 3.2.2
description:
6.summary: Upgrade dev.moodle.org to 3.2.2
description:
7.summary: Upgrade moodle.net to 3.2.2
description:
8.summary: Upgrade download.moodle.org to 3.2.2
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Reduce JS with outdated javascript-static.js code
description: javascript-static.js is full of historical artefacts which get loaded on every page, we should try and get rid of some of it
| Unsolvable | 1.summary: Deprecate init_javascript_enhancement() and smartselect code
description: This functionality was previously used in hubs, but it was a half-job only had one implementation (smartselect) and that smartselect was completely broken in boost. code This function is designed to add an initialisation call for a JavaScript enhancement that should exist within javascript-static M.form.init_enhancementname. code In we got rid of the core uses of smartselect. We should deprecate this method and remove the JS.
2.summary: Remove fix_column_widths ie6 hack applied on every single page for 12 years
description: Nearly 12 years ago| we applied a hack to every page to fix blocks in IE 6. I think its time we stopped applying this hack on every page.
3.summary: Deprecate M.util.focus_login_form M.util.focus_login_error
description: M.util.focus_login_form and M.util.focus_login_error are in javascript-static for every page.
4.summary: Remove old legacy global js functions
description: Weve got a number of functions in javascript-static (e.g. checkall) which have been in the global namespace for nearly 14 years and are not appropiate to modern moodle
5.summary: Deprecate M.util.show_confirm_dialog
description: Use the AMD module core/modal_factory instead.
6.summary: Deprecate M.yui.add_module
description: Ideally we should deprecate use of $OUTPUT->requires->js_module() too, but we may be able to move use of this to a YUI module which is itself lazily loaded to kill this off from javascript-static.js
7.summary: Remove M.util.init_skiplink
description: This really should have been done during but nevermind :/
8.summary: Move custom menus away from YUI
description: If at all possible. At the very least, kill it from javascript-static.js. There is zero reason for it to be there. Its just wrong.
9.summary: Remove M.util.init_toggle_class_on_click
description: It was previously used in course render, but is not longer in use. Doesnt look like its in use by any contrib plugins ether from this search for code on github|
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Reduce JS with outdated javascript-static.js code
description: javascript-static.js is full of historical artefacts which get loaded on every page, we should try and get rid of some of it
### Response:
1.summary: Deprecate init_javascript_enhancement() and smartselect code
description: This functionality was previously used in hubs, but it was a half-job only had one implementation (smartselect) and that smartselect was completely broken in boost. code This function is designed to add an initialisation call for a JavaScript enhancement that should exist within javascript-static M.form.init_enhancementname. code In we got rid of the core uses of smartselect. We should deprecate this method and remove the JS.
2.summary: Remove fix_column_widths ie6 hack applied on every single page for 12 years
description: Nearly 12 years ago| we applied a hack to every page to fix blocks in IE 6. I think its time we stopped applying this hack on every page.
3.summary: Deprecate M.util.focus_login_form M.util.focus_login_error
description: M.util.focus_login_form and M.util.focus_login_error are in javascript-static for every page.
4.summary: Remove old legacy global js functions
description: Weve got a number of functions in javascript-static (e.g. checkall) which have been in the global namespace for nearly 14 years and are not appropiate to modern moodle
5.summary: Deprecate M.util.show_confirm_dialog
description: Use the AMD module core/modal_factory instead.
6.summary: Deprecate M.yui.add_module
description: Ideally we should deprecate use of $OUTPUT->requires->js_module() too, but we may be able to move use of this to a YUI module which is itself lazily loaded to kill this off from javascript-static.js
7.summary: Remove M.util.init_skiplink
description: This really should have been done during but nevermind :/
8.summary: Move custom menus away from YUI
description: If at all possible. At the very least, kill it from javascript-static.js. There is zero reason for it to be there. Its just wrong.
9.summary: Remove M.util.init_toggle_class_on_click
description: It was previously used in course render, but is not longer in use. Doesnt look like its in use by any contrib plugins ether from this search for code on github|
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Moodle Mobile GSOC 2017
description: Epic with all the GSOC 2017 related issues
| Unsolvable | 1.summary: Configure the App for Travis build and SauceLabs testing via Travis
description: Enable testing of the app via SauceLabs
2.summary: Fix all the existing failing E2E tests
description: There are some E2E tests that needs fixing
3.summary: Add E2E tests for newly added features/modules in Moodle Mobile v3.1.x, v3.2.x, v3.3.0
description: We need more tests for covering new features
4.summary: Update End-to-End testing environment documentation
description: Documentation needs updating to reflect latest changes
5.summary: Remove Karma Unit tests and its dependencies
description: The existing Karma Unit Tests are failing and are currently irrelevant with the app, so they can be removed safely along with its related npm dependencies.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Moodle Mobile GSOC 2017
description: Epic with all the GSOC 2017 related issues
### Response:
1.summary: Configure the App for Travis build and SauceLabs testing via Travis
description: Enable testing of the app via SauceLabs
2.summary: Fix all the existing failing E2E tests
description: There are some E2E tests that needs fixing
3.summary: Add E2E tests for newly added features/modules in Moodle Mobile v3.1.x, v3.2.x, v3.3.0
description: We need more tests for covering new features
4.summary: Update End-to-End testing environment documentation
description: Documentation needs updating to reflect latest changes
5.summary: Remove Karma Unit tests and its dependencies
description: The existing Karma Unit Tests are failing and are currently irrelevant with the app, so they can be removed safely along with its related npm dependencies.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Collection of followup issues from Better Office Integrations Project
description: This issue collects together further improvements and regressions from the "Better Office Integrations" project for Moodle 3.3.
| Unsolvable | 1.summary: Add option to trust email of an oauth provider
description: As discussed last week. The use case: institution uses Google for their domain, google oauth provider can be considered trusted for that domain. The administrator should have the option to enable When an account is created it should be possible for the user to SSO and login and not be sent to check their email for confirmation.
2.summary: Allow Moodle to act as an openid provider
description: In Moodle 3.3 we added core support for OpenID as a consumer - we should also support Moodle as an OpenID provider (which would supercede a lot of the MNet functionality). Obviously different Moodle sites should allow connecting together.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Collection of followup issues from Better Office Integrations Project
description: This issue collects together further improvements and regressions from the "Better Office Integrations" project for Moodle 3.3.
### Response:
1.summary: Add option to trust email of an oauth provider
description: As discussed last week. The use case: institution uses Google for their domain, google oauth provider can be considered trusted for that domain. The administrator should have the option to enable When an account is created it should be possible for the user to SSO and login and not be sent to check their email for confirmation.
2.summary: Allow Moodle to act as an openid provider
description: In Moodle 3.3 we added core support for OpenID as a consumer - we should also support Moodle as an OpenID provider (which would supercede a lot of the MNet functionality). Obviously different Moodle sites should allow connecting together.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Add database module support on Mobile app
description: Add database support on the Mobile app using the WS created on .
| Unsolvable | 1.summary: Support database single view
description: Support database single view. Includes subplugins support.
2.summary: Support database list view
description: Support database list view. Includes basic subplugins support.
3.summary: Support database search
description: Support database search
4.summary: Support database add and edit entry
description: Support database add entry
5.summary: Support database comments
description: Support database edit entry
6.summary: Support database approve entry
description: Support database approve entry
7.summary: Support database delete entry
description: Support database delete entry
8.summary: Support database syncing and offline
description: Support database syncing and offline for: Add entry Update entry Approve entry Delete entry
9.summary: Refurbish database according UX
description: Refurbish database according UX
10.summary: Support main info of database activity
description: Support the main page of database activity. This issue includes: Availability. Links to activity sections. Basic prefetch.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Add database module support on Mobile app
description: Add database support on the Mobile app using the WS created on .
### Response:
1.summary: Support database single view
description: Support database single view. Includes subplugins support.
2.summary: Support database list view
description: Support database list view. Includes basic subplugins support.
3.summary: Support database search
description: Support database search
4.summary: Support database add and edit entry
description: Support database add entry
5.summary: Support database comments
description: Support database edit entry
6.summary: Support database approve entry
description: Support database approve entry
7.summary: Support database delete entry
description: Support database delete entry
8.summary: Support database syncing and offline
description: Support database syncing and offline for: Add entry Update entry Approve entry Delete entry
9.summary: Refurbish database according UX
description: Refurbish database according UX
10.summary: Support main info of database activity
description: Support the main page of database activity. This issue includes: Availability. Links to activity sections. Basic prefetch.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic: Collect together deprecated code changes for Moodle 2.9
description: There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Many have a deadline of 2.9. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functio issues and not lose sight of them, this issue will be used to collect them together.
| Unsolvable | 1.summary: Remove behat deprecated step definitions
description: Final deprecation of behat steps that were deprecated in Moodle 2.7
2.summary: Remove second unused param from add_association api in class blog_entry
description: blog_entry->add_associations($action = null) blog_entry->add_association($contextid, $action = null) $action should be removed from both apis
3.summary: Remove javascript-static.js Deprecations
description: As raised in
4.summary: Remove r0/r1 from table tr classlist
description: Refer for full discussion. r0/r1 classes should be removed from table generating libaries:- flexible_table::print_row html_writer::table
5.summary: Remove ajaxenabled function()
description: Deprecated in
6.summary: delete deprecated upload_manager and clam scanning code
description: see the affected classes/functions are in lib/uploadlib.php and clam_ in lib/deprecatedlib.php
7.summary: Remove count_login_failures() from core.
description: count_login_failures() was deprecated in Moodle 2.7 and should be safe to remove it now.
8.summary: Conditional availability: Remove functions/classes deprecated in
description: The following were deprecated in and should be removed in Moodle 2.9 (note that this states version 2.8 because 2.9 is not an available option yet): Entire file lib/conditionlib.php (and lib/tests/conditionlib_test.php) Function coursemodule_visible_for_user (in lib/deprecatedlib.php) In modinfolib.php cm_info class: availablefrom, availableuntil fields (all mentions) and get_deprecated_available_date function get_show_availability function is_user_access_restricted_by_conditional_access function In modinfolib.php section_info class: get_showavailability, get_availablefrom, get_availableuntil, get_groupingid
9.summary: Remove lib/pluginlib.php in Moodle 2.9
description: lib/pluginlib.php contained classes deprecated in 2.6. The file itself was given a debugging notice in 2.8 and is set to be removed in 2.9
10.summary: Remove text/plugin renamed class aliases in 2.9
description: saw a better method of handling renamed classes and their deprecated shoots. As part of that work 4 classes, all renamed and deprecated in 2.6 by autoloading were converted. textlib collatorlib plugin_manager plugininfo_base These four classes will have had proper debugging though 2.8 and should be removed in 2.9
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic: Collect together deprecated code changes for Moodle 2.9
description: There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Many have a deadline of 2.9. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functio issues and not lose sight of them, this issue will be used to collect them together.
### Response:
1.summary: Remove behat deprecated step definitions
description: Final deprecation of behat steps that were deprecated in Moodle 2.7
2.summary: Remove second unused param from add_association api in class blog_entry
description: blog_entry->add_associations($action = null) blog_entry->add_association($contextid, $action = null) $action should be removed from both apis
3.summary: Remove javascript-static.js Deprecations
description: As raised in
4.summary: Remove r0/r1 from table tr classlist
description: Refer for full discussion. r0/r1 classes should be removed from table generating libaries:- flexible_table::print_row html_writer::table
5.summary: Remove ajaxenabled function()
description: Deprecated in
6.summary: delete deprecated upload_manager and clam scanning code
description: see the affected classes/functions are in lib/uploadlib.php and clam_ in lib/deprecatedlib.php
7.summary: Remove count_login_failures() from core.
description: count_login_failures() was deprecated in Moodle 2.7 and should be safe to remove it now.
8.summary: Conditional availability: Remove functions/classes deprecated in
description: The following were deprecated in and should be removed in Moodle 2.9 (note that this states version 2.8 because 2.9 is not an available option yet): Entire file lib/conditionlib.php (and lib/tests/conditionlib_test.php) Function coursemodule_visible_for_user (in lib/deprecatedlib.php) In modinfolib.php cm_info class: availablefrom, availableuntil fields (all mentions) and get_deprecated_available_date function get_show_availability function is_user_access_restricted_by_conditional_access function In modinfolib.php section_info class: get_showavailability, get_availablefrom, get_availableuntil, get_groupingid
9.summary: Remove lib/pluginlib.php in Moodle 2.9
description: lib/pluginlib.php contained classes deprecated in 2.6. The file itself was given a debugging notice in 2.8 and is set to be removed in 2.9
10.summary: Remove text/plugin renamed class aliases in 2.9
description: saw a better method of handling renamed classes and their deprecated shoots. As part of that work 4 classes, all renamed and deprecated in 2.6 by autoloading were converted. textlib collatorlib plugin_manager plugininfo_base These four classes will have had proper debugging though 2.8 and should be removed in 2.9
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Boost theme accessibility issues
description: Issue related to the accessibility of the Boost theme.
| Unsolvable | 1.summary: Boost: Multiple navigation landmarks are present which do not have unique names
description: There are 3 navigation landmarks/regions present on a Boost course landing page. Each landmark should use aria-label or aria-labeledby to provide a unique name, such as course navigation and site navigation Suggestion: Identify a descriptive name for each landmark/region based on the contents of the region and apply the name using aria-label or aria-labeledby.
2.summary: Improve assignment page title
description: The navigation panel indicates visually which is the current page. This is not presented to screen readers in any way. Actually the page title does this in most places. Im going to change this issue to just focus on assignment because we can add more information to the page title there.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Boost theme accessibility issues
description: Issue related to the accessibility of the Boost theme.
### Response:
1.summary: Boost: Multiple navigation landmarks are present which do not have unique names
description: There are 3 navigation landmarks/regions present on a Boost course landing page. Each landmark should use aria-label or aria-labeledby to provide a unique name, such as course navigation and site navigation Suggestion: Identify a descriptive name for each landmark/region based on the contents of the region and apply the name using aria-label or aria-labeledby.
2.summary: Improve assignment page title
description: The navigation panel indicates visually which is the current page. This is not presented to screen readers in any way. Actually the page title does this in most places. Im going to change this issue to just focus on assignment because we can add more information to the page title there.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Update general Moodle navigation
description: We are aiming to overhaul the general navigation around Moodle for version 4.0. One of the main changes is to have a secondary navigation menu that is more context aware and allows quicker access to frequently used items. final wireframe| Project spec|
| Unsolvable | 1.summary: Explore moving main menu items to the secondary navigation (backend)
description: This builds on the issue which aimed to document current nav architecture. This issue should start to build a picture of what might be involved to achieve some of the new nav changes. The focus is on exploring a design. This should also consider how tertiary nav could be implemented, as per the design mocks.
2.summary: Write specification document for 4.0 navigation changes
description: Write up the specification document to outline how we will tackle this project and get sign off from the product owner. Should include: Name Vision statement Personas User stories Design documents Constraints
3.summary: Implement base class & file structure
description: . Implement base class & file structure. Within this sub-task we want the base structure of the new Moodle 4.0 navigation to be implemented. . Acceptance criteria Using the example structure within this issue, create the required sub directories & files Using the example within this issue, implement the base functions within the secondary navigation class Implement new magic method for Secondary navigation $PAGE->secondarynavigationview calls the function magic_get_secondarynavview within lib/pagelib. This would create a new secondary_navigation_view and triggers the initialise function within secondary_navigation_view. . Example structure: /lib/classes /navigation /views /secondary.php . Example class stub: class secondary_navigation_view extends navigation_node // Sets up the view with basic settings and preparse it for use. public function __construct(array $properties) // Initialise the view based navigation based on the current context. public function initialise() /This function recursively scans nodes until it finds the active node or there are no more nodes. etc.....
4.summary: Add required functions for navigation_node within secondary_nav_view
description: . Add required functions for navigation_node. Within this sub-task we need to add functionality to fetch navigation_nodes to populate the navigation view by calling the settings_navigation functions that generate either course, module or user context nodes. It may be likely that we emulate a lot of the initialise() to populate this new navigation. . Acceptance criteria Contents of secondary navigation changes depending on the users context Confirm that menu items added by core modules appear within secondary navigation Third party modules can add navigation items via _extend_settings_navigation
5.summary: Implement PHPUnit testing across new functionality
description: . Implement PHPUnit testing across new functionality. Aim to get as much of the preceding work within the new navigation system covered via PHPUnit. . Acceptance criteria Match if not exceed testing that exists on current navigation classes Cover the creation & fetching of secondary_navigation Assert that expected navigation items exist within the navigation based on context
6.summary: Update the secondary navigation view to send site administration information in tab form.
description: Currently site administration information in the secondary navigation view is taken from the navigation tree. This needs to be updated to use the information that is sent to the template, that is used in the boost theme, to show the initial site administration page. We want the current boost behaviour in the new navigation system.
7.summary: Implement primary navigation
description: . Implement primary navigation. This is a grouping issue to ensure both aspects of the primary navigation can be matched up with each other once begins being worked upon. The current plan & expectation is that will proceed to integration before this is due to how issues can be sent to integration.
8.summary: Implement frontend functionality for primary navigation
description: . Implement frontend functionality for primary navigation. This issue serves as a way to maintain the frontend tasks in a seperate branch until both the primary & secondary navigation backends are integrated. This issue should not be sent to integration once done. Instead a branch should be maintained on top of weeklies and itll be sent to integration in the migration issue. Current parts being worked on: Custom menu items that have children have an accordion effect when selected. We have a "more" section that collects navigation items as the screen width is reduced.
9.summary: Implement secondary navigation
description: . Implement secondary navigation. This is a grouping issue to ensure both aspects of the secondary navigation can be matched up with each other once begins being worked upon. The current plan & expectation is that will proceed to integration before this is due to how issues can be sent to integration.
10.summary: Implement frontend functionality for secondary navigation
description: . Implement frontend functionality for secondary navigation. This issue serves as a way to maintain the frontend tasks in a seperate branch until both the primary & secondary navigation backends are integrated. This issue should not be sent to integration once done. Instead a branch should be maintained on top of weeklies and itll be sent to integration in the migration issue.
11.summary: Implement backend functionality for primary navigation
description: Implement backend functionality for primary navigation. This issue serves as an integration point, once all of the subtasks have been completed, this issue can be sent to integration. Frontend related issues will be maintained in a seperate MDL until both Primary & Secondary navigation frontends are done.
12.summary: Implement backend functionality for secondary navigation
description: Implement backend functionality for secondary navigation. This issue serves as an integration point, once all of the subtasks have been completed, this issue can be sent to integration. Frontend related issues will be maintained in a seperate MDL until both Primary & Secondary navigation frontends are done.
13.summary: Implement base structure & population of primary navigation view
description: . Implement base class & file structure. Within this sub-task we want the base structure of the new Moodle 4.0 navigation to be implemented. . Add required functions for navigation_node. Within this sub-task we need to add functionality to fetch navigation_nodes to populate the navigation view by calling the settings_navigation functions that generates the system context nodes. It may be likely that we emulate a lot of the initialise() to populate this new navigation. . Acceptance criteria Using the example structure within this issue, create the required sub directories & files Using the example within this issue, implement the base functions within the primary navigation class Implement new magic method for primary navigation $PAGE->primarynavigationview calls the function magic_get_primarynavview within lib/pagelib. This would create a new primary_navigation_view and triggers the initialise function within primary_navigation_view. Confirm the primary navigation elements in the design for the primary navigation are returned by the new class . Example structure: /lib/classes /navigation /views /primary.php . Example class stub: class primary_navigation_view extends navigation_node // Sets up the view with basic settings and preparse it for use. public function __construct(array $properties) // Initialise the view based navigation based on the current context. public function initialise() /This function recursively scans nodes until it finds the active node or there are no more nodes. etc..... . Footnote: This issue is slightly different from its counterpart within the secondary navigation series of issues. This issue rolls both the basic creation of files & classes with the implementation of the initialise function and population of the primary navigation view.
14.summary: Implement PHPUnit testing across new functionality
description: . Implement PHPUnit testing across new functionality. Aim to get as much of the preceding work within the new navigation system covered via PHPUnit. . Acceptance criteria Match if not exceed testing that exists on current navigation classes Cover the creation & fetching of primary_navigation Assert that expected navigation items exist within the navigation based on context
15.summary: Create a module based navigation bar
description: . Create a module based navigation bar. This issue serves as an area to maintain a branch until we reach the migration issue. This means that once the subtasks have been completed a branch will need to be maintained upon the latest weeklies until we reach the migration issue where we can push this issue to integration. . User stories ||Story||Acceptance Criteria / Confirmation|| |As any user, I want to navigate back to the course with the navigation bar, so that I can quickly go to a different piece of learning content| As any user, I should be able to use the context header bar within a module to navigate back to the start of the course| |As any user, I want to navigate back to the section the module is in from the navigation bar, so that I can find other pieces of learning content that are similar to the current content I am reviewing|As any user, I should be able to use the context header bar within a module to navigate back to the section of the course that the current module is placed in | |As a teacher, I can need to grade a learners forum activity, so that I can provide my learners with feedback on their activity| Within a forum module instance I can open the forum grading functionality and grade users participation within the forum| |As a learner, I can want to view my grades for a forum activity, so that I can discover if my participation is satisfactory| Within a forum activity I should still have the ability to view my grade using the existing forum grading functionality| |As a teacher, I can turn editing on within a course, so that I can add new content or modify existing content with a course|Depending on other Moodle 4.0 UX projects this may change I can easily turn on course editing within the course to add new modules | |As any user, I can search a forum that I am in, so that I can find relevant posts or discussions before making a new post| I can still search forums in a similar or identical way as I currently can (pre Moodle 4.0)|
16.summary: Investigate the existing navbar
description: . Investigate the existing navbar. Based on the current designs it appears that the context header will be receiving some changes to the navigation bar. To facilitate this we need to investigate how this navigation bar is being created, rendered and shown to the user. It appears that currently within the prototype, the navigation bar only appears when the user is a couple of "levels" deep i.e. in a course module or in the site administration within a tab, the assignee should also look around Moodle to see if there are other locations where the navigation bar is the only way to navigate to ensure the user always has a way to navigate if we were to remove the navigation bar in other contexts. . Acceptance criteria A small report on how the navigation bar is created, rendered & output Notes on other areas where a navigation bar may be required
17.summary: Implement a module context navbar
description: . Implement a module context navbar. Based upon the research in the previous issue & the Moodle 4.0 Navigation prototype| - (Requires update to Figma) implement the new course context header / navigation bar within theme_boost, theme_classic should remain unchanged so some work may be required with moving existing renderers & templates may be required (just guessing here) . User stories ||Story||Approach|| |As any user, I want to navigate back to the course with the navigation bar, so that I can quickly go to a different piece of learning content|As any user, I should be able to use the context header bar within a module to navigate back to the start of the course| |As any user, I want to navigate back to the section the module is in from the navigation bar, so that I can find other pieces of learning content that are similar to the current content I am reviewing|As any user, I should be able to use the context header bar within a module to navigate back to the section of the course that the current module is placed in| |As any user, I can search a forum that I am in, so that I can find relevant posts or discussions before making a new post|I can still search forums in a similar or identical way as I currently can (pre Moodle 4.0)| . Acceptance criteria The navigation bar behaves and matches the prototype designs Context header elements rearranged to match the designs New navigation elements are accessible Follows WCAG AA LTR & RTL compatibility New files and sub directories created in logical locations User interactions Disappears upon scrolling down the page Reappears upon scrolling page up to the head . Areas to focus on Module name Navigation bar Module image Removal of tertiary navigation / settings gear menu
18.summary: Modify navigation bar Behat tests to ensure tests still pass
description: . Modify Behat tests to ensure tests still pass. During the development of the new navigation bar it is possible that existing behat tests may start failing. Before we consider the navigation bar work done, we need to ensure we are not introducing new failures by migrating existing behat tests to the new navigation where required. It could be possible that we need to deprecate existing behat steps or migrate them over to theme_classics behat step overrides and implement new steps for theme_boost/Moodle core . Acceptance criteria Existing behat tests continue to pass across both classic & boost (no introduced failures)
19.summary: Convert usermenu to use templates
description: -Currently the user menu is rendered via html write statements in the outputrenderers.php user_menu() fn.- -This needs to be converted to use templates and will feed into the combining issue - - The user menu is rendered partially via html(for the profile button metadata) and partially through templates(via the action_menu class). After a discussion with Adrian, it was decided to progress on before working on this. Also this issue would include rendering of a user_menu partial that would be sent to the front end instead of providing nodes like the other menu available.
20.summary: Combine both the custom menu & primary navigation renderers
description: Given the new navigation, We need to be able to fetch the contents of both the primary navigation & custom menu in one array of navigation nodes to assist with rendering. This is likely backend work that needs to be addressed and the new call provided to Bas. Cheers,
21.summary: Update language menu to move from the top navigation into the user menu when logged in.
description: The language menu is to be in the top navigation bar when the user is not logged in. Once the user is logged in the language menu is to move into the user menu. At the moment the user menu does not allow for a drop down to be included, so this must be updated.
22.summary: New flag to force items into more menu
description: As part of updates and discussions within the team it was decided to introduce a new flag to indicate whether an item should permanently reside within the more menu. We also want to be able to limit the maximum number of items shown in the secondary navigation. After this number is reached the remaining items are moved into the "more" section (with the items always located in the more menu). Lets create a constant to hold this value. We can test what value works best and easily change it if needed. This applies only to secondary navigation. The patch should include the changes to the frontend as well. No need to create a separate issue for this. Base code of the nav project branch.
23.summary: Define the secondary navigation nodes that should be always displayed in the more menu in the module context
description: We need to set certain secondary navigation nodes to be always displayed by in the "more" menu in the module context. The following nodes need to be forced into the "more" menu: Filters Permissions Check permissions Logs Locally assigned roles Backup Restore Competency breakdown
24.summary: Allow plugins to define their own secondary nav ordering
description: Allow plugins to define their own secondary nav ordering
25.summary: Provide active node text and menu title
description: This issue has 2 requirements: Provide the text for the active node on the main secondary nav node. This is so the frontend can easily display the active node text without looping through each of this children In the mockups and on smaller screens, the secondary navigation displays a menu header. This needs to be context based: Activity menu - when in an activity Course menu - when in a course
26.summary: Document the current working of the navigationlib
description: Take a look at lib/navigationlib.php to see what would need to be moved into a new function to return the secondary navigation items. Take a look at this| page to see the headings in the tabs for the secondary navigation and the items contained in each area. No coding to be done here, just research to inform an approach to take.
27.summary: Update the context_header in boost to move the breadcrumb to the top.
description: To make the navigation match the proposed figma mockup for the navigation 4.0 project, the context header needs to be updated in the following ways: The breadcrumb is to be moved above the title. In the module context: An additional prefix string is to be added with the type of activity this is. The prefix text is to be dimmed. The image of the activity is to the added to the left of the header and prefix text. UX mockup: !Screenshot from 2021-06-24 13-43-44.png|thumbnail!
28.summary: Create landing page for the reports link in the secondary navigation
description: Each of the items in the secondary navigation (in a course context) need to be links to pages. Currently the reports item in the navigation has no page to navigate to. The proposal is to have the link point to one of the report pages and for there to be a select box to navigate to the other report pages from there. I would suggest that the default page be the logs report. Items in the tertiary dropdown menu should be ordered as such: Logs Live logs Activity report Course participation Activity completion Competency breakdown Insights Statistics Event monitoring rules Lets add a user setting to remember the last report that was selected and return to that page when the reports link is clicked (The same as the gradebook works).
29.summary: Get navigation ready for integration
description: Ensure both Behat & PHPUnit are passing before sending the entire epic to integration
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Update general Moodle navigation
description: We are aiming to overhaul the general navigation around Moodle for version 4.0. One of the main changes is to have a secondary navigation menu that is more context aware and allows quicker access to frequently used items. final wireframe| Project spec|
### Response:
1.summary: Explore moving main menu items to the secondary navigation (backend)
description: This builds on the issue which aimed to document current nav architecture. This issue should start to build a picture of what might be involved to achieve some of the new nav changes. The focus is on exploring a design. This should also consider how tertiary nav could be implemented, as per the design mocks.
2.summary: Write specification document for 4.0 navigation changes
description: Write up the specification document to outline how we will tackle this project and get sign off from the product owner. Should include: Name Vision statement Personas User stories Design documents Constraints
3.summary: Implement base class & file structure
description: . Implement base class & file structure. Within this sub-task we want the base structure of the new Moodle 4.0 navigation to be implemented. . Acceptance criteria Using the example structure within this issue, create the required sub directories & files Using the example within this issue, implement the base functions within the secondary navigation class Implement new magic method for Secondary navigation $PAGE->secondarynavigationview calls the function magic_get_secondarynavview within lib/pagelib. This would create a new secondary_navigation_view and triggers the initialise function within secondary_navigation_view. . Example structure: /lib/classes /navigation /views /secondary.php . Example class stub: class secondary_navigation_view extends navigation_node // Sets up the view with basic settings and preparse it for use. public function __construct(array $properties) // Initialise the view based navigation based on the current context. public function initialise() /This function recursively scans nodes until it finds the active node or there are no more nodes. etc.....
4.summary: Add required functions for navigation_node within secondary_nav_view
description: . Add required functions for navigation_node. Within this sub-task we need to add functionality to fetch navigation_nodes to populate the navigation view by calling the settings_navigation functions that generate either course, module or user context nodes. It may be likely that we emulate a lot of the initialise() to populate this new navigation. . Acceptance criteria Contents of secondary navigation changes depending on the users context Confirm that menu items added by core modules appear within secondary navigation Third party modules can add navigation items via _extend_settings_navigation
5.summary: Implement PHPUnit testing across new functionality
description: . Implement PHPUnit testing across new functionality. Aim to get as much of the preceding work within the new navigation system covered via PHPUnit. . Acceptance criteria Match if not exceed testing that exists on current navigation classes Cover the creation & fetching of secondary_navigation Assert that expected navigation items exist within the navigation based on context
6.summary: Update the secondary navigation view to send site administration information in tab form.
description: Currently site administration information in the secondary navigation view is taken from the navigation tree. This needs to be updated to use the information that is sent to the template, that is used in the boost theme, to show the initial site administration page. We want the current boost behaviour in the new navigation system.
7.summary: Implement primary navigation
description: . Implement primary navigation. This is a grouping issue to ensure both aspects of the primary navigation can be matched up with each other once begins being worked upon. The current plan & expectation is that will proceed to integration before this is due to how issues can be sent to integration.
8.summary: Implement frontend functionality for primary navigation
description: . Implement frontend functionality for primary navigation. This issue serves as a way to maintain the frontend tasks in a seperate branch until both the primary & secondary navigation backends are integrated. This issue should not be sent to integration once done. Instead a branch should be maintained on top of weeklies and itll be sent to integration in the migration issue. Current parts being worked on: Custom menu items that have children have an accordion effect when selected. We have a "more" section that collects navigation items as the screen width is reduced.
9.summary: Implement secondary navigation
description: . Implement secondary navigation. This is a grouping issue to ensure both aspects of the secondary navigation can be matched up with each other once begins being worked upon. The current plan & expectation is that will proceed to integration before this is due to how issues can be sent to integration.
10.summary: Implement frontend functionality for secondary navigation
description: . Implement frontend functionality for secondary navigation. This issue serves as a way to maintain the frontend tasks in a seperate branch until both the primary & secondary navigation backends are integrated. This issue should not be sent to integration once done. Instead a branch should be maintained on top of weeklies and itll be sent to integration in the migration issue.
11.summary: Implement backend functionality for primary navigation
description: Implement backend functionality for primary navigation. This issue serves as an integration point, once all of the subtasks have been completed, this issue can be sent to integration. Frontend related issues will be maintained in a seperate MDL until both Primary & Secondary navigation frontends are done.
12.summary: Implement backend functionality for secondary navigation
description: Implement backend functionality for secondary navigation. This issue serves as an integration point, once all of the subtasks have been completed, this issue can be sent to integration. Frontend related issues will be maintained in a seperate MDL until both Primary & Secondary navigation frontends are done.
13.summary: Implement base structure & population of primary navigation view
description: . Implement base class & file structure. Within this sub-task we want the base structure of the new Moodle 4.0 navigation to be implemented. . Add required functions for navigation_node. Within this sub-task we need to add functionality to fetch navigation_nodes to populate the navigation view by calling the settings_navigation functions that generates the system context nodes. It may be likely that we emulate a lot of the initialise() to populate this new navigation. . Acceptance criteria Using the example structure within this issue, create the required sub directories & files Using the example within this issue, implement the base functions within the primary navigation class Implement new magic method for primary navigation $PAGE->primarynavigationview calls the function magic_get_primarynavview within lib/pagelib. This would create a new primary_navigation_view and triggers the initialise function within primary_navigation_view. Confirm the primary navigation elements in the design for the primary navigation are returned by the new class . Example structure: /lib/classes /navigation /views /primary.php . Example class stub: class primary_navigation_view extends navigation_node // Sets up the view with basic settings and preparse it for use. public function __construct(array $properties) // Initialise the view based navigation based on the current context. public function initialise() /This function recursively scans nodes until it finds the active node or there are no more nodes. etc..... . Footnote: This issue is slightly different from its counterpart within the secondary navigation series of issues. This issue rolls both the basic creation of files & classes with the implementation of the initialise function and population of the primary navigation view.
14.summary: Implement PHPUnit testing across new functionality
description: . Implement PHPUnit testing across new functionality. Aim to get as much of the preceding work within the new navigation system covered via PHPUnit. . Acceptance criteria Match if not exceed testing that exists on current navigation classes Cover the creation & fetching of primary_navigation Assert that expected navigation items exist within the navigation based on context
15.summary: Create a module based navigation bar
description: . Create a module based navigation bar. This issue serves as an area to maintain a branch until we reach the migration issue. This means that once the subtasks have been completed a branch will need to be maintained upon the latest weeklies until we reach the migration issue where we can push this issue to integration. . User stories ||Story||Acceptance Criteria / Confirmation|| |As any user, I want to navigate back to the course with the navigation bar, so that I can quickly go to a different piece of learning content| As any user, I should be able to use the context header bar within a module to navigate back to the start of the course| |As any user, I want to navigate back to the section the module is in from the navigation bar, so that I can find other pieces of learning content that are similar to the current content I am reviewing|As any user, I should be able to use the context header bar within a module to navigate back to the section of the course that the current module is placed in | |As a teacher, I can need to grade a learners forum activity, so that I can provide my learners with feedback on their activity| Within a forum module instance I can open the forum grading functionality and grade users participation within the forum| |As a learner, I can want to view my grades for a forum activity, so that I can discover if my participation is satisfactory| Within a forum activity I should still have the ability to view my grade using the existing forum grading functionality| |As a teacher, I can turn editing on within a course, so that I can add new content or modify existing content with a course|Depending on other Moodle 4.0 UX projects this may change I can easily turn on course editing within the course to add new modules | |As any user, I can search a forum that I am in, so that I can find relevant posts or discussions before making a new post| I can still search forums in a similar or identical way as I currently can (pre Moodle 4.0)|
16.summary: Investigate the existing navbar
description: . Investigate the existing navbar. Based on the current designs it appears that the context header will be receiving some changes to the navigation bar. To facilitate this we need to investigate how this navigation bar is being created, rendered and shown to the user. It appears that currently within the prototype, the navigation bar only appears when the user is a couple of "levels" deep i.e. in a course module or in the site administration within a tab, the assignee should also look around Moodle to see if there are other locations where the navigation bar is the only way to navigate to ensure the user always has a way to navigate if we were to remove the navigation bar in other contexts. . Acceptance criteria A small report on how the navigation bar is created, rendered & output Notes on other areas where a navigation bar may be required
17.summary: Implement a module context navbar
description: . Implement a module context navbar. Based upon the research in the previous issue & the Moodle 4.0 Navigation prototype| - (Requires update to Figma) implement the new course context header / navigation bar within theme_boost, theme_classic should remain unchanged so some work may be required with moving existing renderers & templates may be required (just guessing here) . User stories ||Story||Approach|| |As any user, I want to navigate back to the course with the navigation bar, so that I can quickly go to a different piece of learning content|As any user, I should be able to use the context header bar within a module to navigate back to the start of the course| |As any user, I want to navigate back to the section the module is in from the navigation bar, so that I can find other pieces of learning content that are similar to the current content I am reviewing|As any user, I should be able to use the context header bar within a module to navigate back to the section of the course that the current module is placed in| |As any user, I can search a forum that I am in, so that I can find relevant posts or discussions before making a new post|I can still search forums in a similar or identical way as I currently can (pre Moodle 4.0)| . Acceptance criteria The navigation bar behaves and matches the prototype designs Context header elements rearranged to match the designs New navigation elements are accessible Follows WCAG AA LTR & RTL compatibility New files and sub directories created in logical locations User interactions Disappears upon scrolling down the page Reappears upon scrolling page up to the head . Areas to focus on Module name Navigation bar Module image Removal of tertiary navigation / settings gear menu
18.summary: Modify navigation bar Behat tests to ensure tests still pass
description: . Modify Behat tests to ensure tests still pass. During the development of the new navigation bar it is possible that existing behat tests may start failing. Before we consider the navigation bar work done, we need to ensure we are not introducing new failures by migrating existing behat tests to the new navigation where required. It could be possible that we need to deprecate existing behat steps or migrate them over to theme_classics behat step overrides and implement new steps for theme_boost/Moodle core . Acceptance criteria Existing behat tests continue to pass across both classic & boost (no introduced failures)
19.summary: Convert usermenu to use templates
description: -Currently the user menu is rendered via html write statements in the outputrenderers.php user_menu() fn.- -This needs to be converted to use templates and will feed into the combining issue - - The user menu is rendered partially via html(for the profile button metadata) and partially through templates(via the action_menu class). After a discussion with Adrian, it was decided to progress on before working on this. Also this issue would include rendering of a user_menu partial that would be sent to the front end instead of providing nodes like the other menu available.
20.summary: Combine both the custom menu & primary navigation renderers
description: Given the new navigation, We need to be able to fetch the contents of both the primary navigation & custom menu in one array of navigation nodes to assist with rendering. This is likely backend work that needs to be addressed and the new call provided to Bas. Cheers,
21.summary: Update language menu to move from the top navigation into the user menu when logged in.
description: The language menu is to be in the top navigation bar when the user is not logged in. Once the user is logged in the language menu is to move into the user menu. At the moment the user menu does not allow for a drop down to be included, so this must be updated.
22.summary: New flag to force items into more menu
description: As part of updates and discussions within the team it was decided to introduce a new flag to indicate whether an item should permanently reside within the more menu. We also want to be able to limit the maximum number of items shown in the secondary navigation. After this number is reached the remaining items are moved into the "more" section (with the items always located in the more menu). Lets create a constant to hold this value. We can test what value works best and easily change it if needed. This applies only to secondary navigation. The patch should include the changes to the frontend as well. No need to create a separate issue for this. Base code of the nav project branch.
23.summary: Define the secondary navigation nodes that should be always displayed in the more menu in the module context
description: We need to set certain secondary navigation nodes to be always displayed by in the "more" menu in the module context. The following nodes need to be forced into the "more" menu: Filters Permissions Check permissions Logs Locally assigned roles Backup Restore Competency breakdown
24.summary: Allow plugins to define their own secondary nav ordering
description: Allow plugins to define their own secondary nav ordering
25.summary: Provide active node text and menu title
description: This issue has 2 requirements: Provide the text for the active node on the main secondary nav node. This is so the frontend can easily display the active node text without looping through each of this children In the mockups and on smaller screens, the secondary navigation displays a menu header. This needs to be context based: Activity menu - when in an activity Course menu - when in a course
26.summary: Document the current working of the navigationlib
description: Take a look at lib/navigationlib.php to see what would need to be moved into a new function to return the secondary navigation items. Take a look at this| page to see the headings in the tabs for the secondary navigation and the items contained in each area. No coding to be done here, just research to inform an approach to take.
27.summary: Update the context_header in boost to move the breadcrumb to the top.
description: To make the navigation match the proposed figma mockup for the navigation 4.0 project, the context header needs to be updated in the following ways: The breadcrumb is to be moved above the title. In the module context: An additional prefix string is to be added with the type of activity this is. The prefix text is to be dimmed. The image of the activity is to the added to the left of the header and prefix text. UX mockup: !Screenshot from 2021-06-24 13-43-44.png|thumbnail!
28.summary: Create landing page for the reports link in the secondary navigation
description: Each of the items in the secondary navigation (in a course context) need to be links to pages. Currently the reports item in the navigation has no page to navigate to. The proposal is to have the link point to one of the report pages and for there to be a select box to navigate to the other report pages from there. I would suggest that the default page be the logs report. Items in the tertiary dropdown menu should be ordered as such: Logs Live logs Activity report Course participation Activity completion Competency breakdown Insights Statistics Event monitoring rules Lets add a user setting to remember the last report that was selected and return to that page when the reports link is clicked (The same as the gradebook works).
29.summary: Get navigation ready for integration
description: Ensure both Behat & PHPUnit are passing before sending the entire epic to integration
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle sites 2.8.2 upgrade
description: Moodle 2.8.2 scheduled release: 12 Jan 2015 Target completion date of this epic: 12 Jan 2015
| Unsolvable | 1.summary: Upgrade demo.moodle.net to 2.8.2
description:
2.summary: Upgrade school.demo.moodle.net to 2.8.2
description:
3.summary: Upgrade dev.moodle.org to 2.8.2
description:
4.summary: Upgrade moodle.org to 2.8.2
description:
5.summary: Upgrade moodle.net to 2.8.2
description:
6.summary: Upgrade research.moodle.net to 2.8.2
description:
7.summary: Upgrade download.moodle.org to 2.8.2
description:
8.summary: Upgrade lang.moodle.org to 2.8.2
description:
9.summary: Upgrade learn.moodle.net to 2.8.2
description:
10.summary: Upgrade moodlemoot.org sites to 2.8.2
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle sites 2.8.2 upgrade
description: Moodle 2.8.2 scheduled release: 12 Jan 2015 Target completion date of this epic: 12 Jan 2015
### Response:
1.summary: Upgrade demo.moodle.net to 2.8.2
description:
2.summary: Upgrade school.demo.moodle.net to 2.8.2
description:
3.summary: Upgrade dev.moodle.org to 2.8.2
description:
4.summary: Upgrade moodle.org to 2.8.2
description:
5.summary: Upgrade moodle.net to 2.8.2
description:
6.summary: Upgrade research.moodle.net to 2.8.2
description:
7.summary: Upgrade download.moodle.org to 2.8.2
description:
8.summary: Upgrade lang.moodle.org to 2.8.2
description:
9.summary: Upgrade learn.moodle.net to 2.8.2
description:
10.summary: Upgrade moodlemoot.org sites to 2.8.2
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.3.2 upgrade
description: Moodle 3.3.2 is scheduled for release on 11 September 2017
| Unsolvable | 1.summary: Upgrade moodle.org to 3.3.2
description:
2.summary: Upgrade learn.moodle.net to 3.3.2
description:
3.summary: Upgrade lang.moodle.org to 3.3.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.3.2
description:
5.summary: Upgrade demo.moodle.net to 3.3.2
description:
6.summary: Upgrade dev.moodle.org to 3.3.2
description:
7.summary: Upgrade moodle.net to 3.3.2
description:
8.summary: Upgrade download.moodle.org to 3.3.2
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.3.2 upgrade
description: Moodle 3.3.2 is scheduled for release on 11 September 2017
### Response:
1.summary: Upgrade moodle.org to 3.3.2
description:
2.summary: Upgrade learn.moodle.net to 3.3.2
description:
3.summary: Upgrade lang.moodle.org to 3.3.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.3.2
description:
5.summary: Upgrade demo.moodle.net to 3.3.2
description:
6.summary: Upgrade dev.moodle.org to 3.3.2
description:
7.summary: Upgrade moodle.net to 3.3.2
description:
8.summary: Upgrade download.moodle.org to 3.3.2
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Deprecate Atto in favour of Tiny 6
description: Atto was designed as a lightweight, accessible, in-house editor for Moodle. While it has arguably achieved all of these goals, it was written nearly a decade ago, uses deprecated technologies, and is difficult to maintain. In addition: Moodle lacks the dedicated, in-house, knowledge to maintain a rich text editor Maintaining our own editor detracts from our core business goals of writing a kick-ass LMS to empower educators. The JavaScript world has moved on, but because Atto is built upon the now-deprecated YUI framework, it is increasingly difficult for us to add new features using modern language features. The library we use to normalise content selection (Rangy) was abandoned shortly after we started to use it, and has a number of known issues that detract from the experience of using Atto. Many of the language features that Atto is based around were experimental at the time of its original writing and never made it to the browser specification. Their continued use is not advisable. Atto is fine for editing short content, but when editing larger, or more complex, content it becomes more challenging. In particular, the undo/redo are problematic, and image handling is tricky. . Possible solutions As with any problem, we have multiple solutions available - each has their own benefits and problems. To add to this, Moodle also has a number of restrictions which we place upon ourselves and which make any product selection more complex and/or prohibitive, in particular: Our plugin structure does not support files being parachuted into place. We have a strict plugin architecture which must be followed for community plugins to work. We do not use any server-side JS processing, such as WebPack. All of our JS is shipped with Moodle, or community Moodle plugins, as pre-compiled code ready for production. This prevents us from using any editor which tree-shakes code based on configuration, or whose APIs are mangled during their build process. We use our own Translation system (AMOS) We use our own dialogues, menu bars, and other UI features . Rewrite Atto Perhaps the most obvious solution is to rewrite Atto as a series of ES Modules to match our other JavaScript content. In doing so we would also have to find an alternative to the rangy library, and to the deprecated Document.execCommand() browser API. In an ideal world we would also maintain backwards compatibility with existing Atto plugins, but this would be extremely difficult given the move from YUI to ESM, the necessary change of underlying API, and the replacement of Rangy. The complexity of this project would be high, and Moodle would still be maintaining its own text editor, which is a huge distraction from our core business. . Replace Atto Atto is not the only rich text editor available, and many other Open Source editors exist. These include editors like CKEditor, Tiny, and Quill. Others do exist but are not included here as they are opinionated in their design and/or abandoned. However, replacing Atto is not a trivial task. Whilst this approach would work around the issues of finding alternatives to Rangy and the use of deprecated browser APIs, it would not solve the issues of breaking compatibility with all existing third-party plugins; however it can provide a wealth of existing functionality with years of dedicated research and development instead. In many cases the current Moodle plugins can be replaced with existing plugins, negating the need to develop them again for Moodle. . CKEditor The limitations above immediately preclude the use of CKEditor 5, which requires WebPack, and tree shakes the entire platform. It would not be possible for third-party developers to write plugins for multiple versions of Moodle, and a new compilation step would be required, and could only run when all possible plugins are in place. Configuration would not be trivial. . QuillJS QuillJS is an editor framework. Whilst it can provide an editor without any further configuration, to do anything more Moodle would need to create all interfaces using our own existing components and integrate these with the QuillJS APIs. This is closer to the Replace Atto approach, but with a well-supported underlying editor API. This approach would still require all of the current overheads of maintaining an editor, albeit without most of the more complex editor parts. . Tiny Tiny is a full-featured editor, which comes with a number of standard plugins which replace many of Atto s standard features - these include standard formatting, font and colour selection, alignment and justification, undo/redo, word count, source-code viewing, table support, links, emojis, copy, and paste. Many of these features will work as-is for Moodle. Some use the Tiny modal and form frameworks and we would have to decide whether to use these in Moodle, or to rewrite them using the standard Moodle interfaces. This decision would not have to be made immediately. . Other options I looked at a number of other possible editors, but these were either opinionated in their choice of technology (for example jQuery, specific Bootstrap versions), or were abandoned. . Important If you are aware of other editors which meet these criterion, and you feel we should include them in this consideration now is the time to mention them. Given the above analysis, we are currently looking at adopting Tiny version 6 as a replacement for Atto.
| Unsolvable | 1.summary: Create TinyMCE H5P plugin
description: This will need the same functionality as the Atto H5P plugin.
2.summary: Create TinyMCE Draft save/restore integration
description: In Atto this is handled as a plugin. We should see whether that is appropriate in this case. There is an existing TinyMCE autosave plugin, but this does not upload to the server (it uses LocalStorage) and is therefore unsuited to our requirements. We should be able to base what we do on that plugiun to some extent, but replacing the LocalStorage with remote storage and changing the back-off to not negatively affect server performance.
3.summary: Ensure that tests continue to work
description: We need to ensure that tests continue to work if Tiny is the default editor (except for Atto-specific tests). We will need to ensure that things like the core editing functionality continue to work (bold, italic, etc.) and that we ahve appropriate steps to click on buttons and menu items too.
4.summary: Create basic integration of Tiny 6.x with Moodle
description: Create the basic integration of Tiny 6 with Moodle, including: basic integration any module loading required to support this instructions to import the latest version of Tiny when required subplugin support (but no subplugins) Things left to separate issues: configuration of the toolbar and/or menu items the creation of plugins for Moodle-specific features (many standard features are already present in Tiny) translation support Other areas to consider: Tiny has its own modal dialogue system ( We need to decide whether to: use their dialogs for our own plugins use our own dialogs for our own plugins use our own dialogs for our plugins and rewrite theirs to use our dialogs create our own Tiny Theme (not recommended by Tiny, and not documented)
5.summary: Add Tiny6 Translation
description: We will need to support translation of the TinyMCE User Interface. The Tiny UI uses the tinymce.addI18N function which takes: a language code (i.e. de for german) an object with: English string Translated string To facilitate this I think well have to write an import tool to take a complete language file and generate a list of translated strings with unique keys, etc. Well then need a lang.php generator which spits out any translated values alongside their original English translation as a JSON object. We can then fetch this from within ouor TinyMCE loader and call it something like: code const langData = await fetch(`$M.cfg.wwwroot/lib/editor/tiny/lang.php/$lang`); tinymce.addI18n(lang, langData); code
6.summary: Supplement loading TinyMCE with a Loader
description: We need to ensure that we load all TinyMCE content using a service loader. This is similar to the lang.php in the current prototype, and existing core services such as: lib/requirejs.php theme/styles.php This should support loading of all TinyMCE core files including: JavaScript: CSS It needs to consider: jsrev cssrev caching of files in tempdir See existing examples for some of the things we need to consider. . Additional thoughts Ideally we should have a core framework for all loaders and we should load very basic information from the plugin on the content they need to load. However I would ideally like to make the TinyMCE plugin available in the Plugins Database for 3.11, and 4.0 to encourage uptake and. authorship of new contrib plugins. It may be that we do make a core loader but bundle it into the editor_tiny plugin for the contrib distribution to support this.
7.summary: Create TinyMCE Media plugin with Image editing
description: Eventually this should be a single plugin which adds: Insert Image Insert Video Drag/Drop handling Media management See for information on drag/drop uploading within TinyMCE. We should find a way to disable the native drag/drop handling when the editor does not support file uploads at all. This should integrate with the Repository API. Decision to be made on whether our custom plugins should use the Moodle dialogues, or the TinyMCE ones. . In this issue This issue is all about getting the _image_ insertion working. That is: drag/drop upload replicating the current TinyMCE standard / Atto standard image features into a Moodle modal ideally displaying a preview If context menus are easy, then they can be done here too, otherwise we can move that to a separate issue. Note: The epic contains a start on the above to get the drag/drop working and to add a fake implementation of the button.
8.summary: Create TinyMCE Media manager functionality in the tiny_media plugin
description: Once the first part of our custom TinyMCE media plugin is implemented (, which adds image functionality), we can introduce media manager functionality, which allows you to manage all media (image/video/audio) content that has been added to the current instance of the editor using the new media plugin. For this iteration of the TinyMCE integration project, this just requires porting the existing media manager functionality from Atto over to TinyMCE 6. Since Atto simply displays that manager in an iframe, this should just be a matter of finding the relevant place in TinyMCE to add this, and taking the same approach (ie displaying an iframe of the file manager in the same way). One of the reasons the manager is required, is that when you delete an image within the editor, the file still exists in the draft area, so is carried over when the content is saved. To avoid that, you must go into the media manager, and delete the image. There are possibly ways this could be handled automatically in future, but this is out of scope for the current work. This may form part of the plugin created in , or will _possibly_ need to be a separate plugin, so deciding that forms part of this issue. Note: To work on this issue, you will need to create a branch based on both and (assuming this is not worked on before those land in core, which is likely).
9.summary: Create Video insertion/editing functionality in the tiny_media plugin
description: Once lands we should extend that plugin to support the creation of video plugins, including: subtitles alternatives drag/drop handling anything else..?
10.summary: Create TinyMCE RecordRTC plugin
description: Create a TinyMCE recordrtc plugin which supports: recording Audio recording Video Usual restrictions apply (requires file area configuration).
11.summary: Configure available headings and formatting options
description: The standard TinyMCE configuration allows for specifying H1 and H2 level headings, which we have traditionally removed in Atto. We need to decide upn the available formatting types, which we can do with the block_formats option: We need to look at whether there are any other options we wish to remove, restrict, or otherwise configure. This may include items such as (not an exhaustive list): text and background colours font family configuration font size configuration
12.summary: Create TinyMCE Accessibility checker
description: New custom plugin shipped with core. This should apply the same checks as the current Atto a11y tool. We should look at whether its possible to incorporate the existing Screenreader helper plugin into the same tool, and whether either/both plugins are still required.
13.summary: Create TinyMCE Equation editor plugin
description: We need to look at how we allow the use of MathJAX (and similar) within TinyMCE.
14.summary: Set editor for editor-specific tests
description: We should make it possible to set the current editor for editor-specific tests. This is required as part of , but is a feature useful for other editors on stable branches.
15.summary: Provide way to set HTML Editor content regardless of the current editor
description: The HTML Editor Behat field type is currently specific to Atto and it should not be. We should amend the API to allow any editor to provide relevant functions to set content.
16.summary: Allow Tiny branding to be disabled by admin
description: This is a part of which will look at alternative solutions too. This gives administrators the option of disabling the Tiny branding. The following is the relevant part of the license: quote Product attribution is required for free users utilizing the Tiny Cloud infrastructure. If using TinyMCE under the MIT license, then support for the open source project would be appreciated by keeping attribution turned on in your editor. For information on TinyMCE attribution requirements, see: Logo & attribution requirements. quote This is further interated at quote While it is unclear under the MIT open source license to include attribution, we do encourage it. TinyMCE open source is provided free of charge, and is made possible by contributions of the community. The larger the community is, the better TinyMCE will become. Please consider including attribution. quote We _can_ remove the branding from the status bar, and move it elsewhere and they provide the following guidance: quote If the status bar is removed or not visible on the editor, you can include attribution per the following: POWERED BY TINY or the Tiny logo placed in a readily visible location in your application when the editor is loaded. The word Tiny or the Tiny logo should have a hyperlink to The location of the product attribution is to be: In the right-hand corner of the status bar of the TinyMCE editor; or An alternate location adjacent to the TinyMCE editor that is no less prominent. quote So a few options spring to mind: give administrators an option of whether to show the branding in the status bar (checkbox, default on) move the attribution to the page footer, and only show it once per page, for example: quote Moodle text editor powered by Tiny| quote The current situation is shown below: !Screen Shot 2022-10-11 at 14.02.22.png|thumbnail!
17.summary: Initial TinyMCE 6 integration for Moodle 4.1
description: This issue is to capture the initial integration of TinyMCE6 with Moodle 4.1.
18.summary: Add Behat step to force editors to save their content back to the textarea
description: TinyMCE (and others) only persist their data back to the textarea at certain points (such as when submitting the form). This meanst that the steps we use to get values do not work as expected. Alongside our settable editors, we should give editors a chance to save persist their values to the textarea.
19.summary: Standardise HTML output when comparing editor values
description: At the moment, the behat editor field is very tilted towards supporting Atto. It should standardise the editor HTML content before comparison. This change also addresses a related bug in the i_type (When I type "This is some text" whereby, if there is a new line character (\n) it is treated differently in Firefox to Chrome. This is solved by swapping any newline with the W3C ENTER character string: \xEE\x80\x87.
20.summary: Behat i_type should normalise newlines
description: The following step will behave different between Chrome and Firefox: code And I type the following text in the "Description" TinyMCE editor: """ This is not important """ code In Chrome, the newline will be treated as a Paragraph tag In Firefox it is treated as a Line break. The i_type function should swap the "\n" character to a W3C ENTER character string: \xEE\x80\x87.
21.summary: Verify the standard toolbar and menu configuration
description: Now that all of the core plugins have been written, we need to look at tweaking and adjusting the toolbar configuration.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Deprecate Atto in favour of Tiny 6
description: Atto was designed as a lightweight, accessible, in-house editor for Moodle. While it has arguably achieved all of these goals, it was written nearly a decade ago, uses deprecated technologies, and is difficult to maintain. In addition: Moodle lacks the dedicated, in-house, knowledge to maintain a rich text editor Maintaining our own editor detracts from our core business goals of writing a kick-ass LMS to empower educators. The JavaScript world has moved on, but because Atto is built upon the now-deprecated YUI framework, it is increasingly difficult for us to add new features using modern language features. The library we use to normalise content selection (Rangy) was abandoned shortly after we started to use it, and has a number of known issues that detract from the experience of using Atto. Many of the language features that Atto is based around were experimental at the time of its original writing and never made it to the browser specification. Their continued use is not advisable. Atto is fine for editing short content, but when editing larger, or more complex, content it becomes more challenging. In particular, the undo/redo are problematic, and image handling is tricky. . Possible solutions As with any problem, we have multiple solutions available - each has their own benefits and problems. To add to this, Moodle also has a number of restrictions which we place upon ourselves and which make any product selection more complex and/or prohibitive, in particular: Our plugin structure does not support files being parachuted into place. We have a strict plugin architecture which must be followed for community plugins to work. We do not use any server-side JS processing, such as WebPack. All of our JS is shipped with Moodle, or community Moodle plugins, as pre-compiled code ready for production. This prevents us from using any editor which tree-shakes code based on configuration, or whose APIs are mangled during their build process. We use our own Translation system (AMOS) We use our own dialogues, menu bars, and other UI features . Rewrite Atto Perhaps the most obvious solution is to rewrite Atto as a series of ES Modules to match our other JavaScript content. In doing so we would also have to find an alternative to the rangy library, and to the deprecated Document.execCommand() browser API. In an ideal world we would also maintain backwards compatibility with existing Atto plugins, but this would be extremely difficult given the move from YUI to ESM, the necessary change of underlying API, and the replacement of Rangy. The complexity of this project would be high, and Moodle would still be maintaining its own text editor, which is a huge distraction from our core business. . Replace Atto Atto is not the only rich text editor available, and many other Open Source editors exist. These include editors like CKEditor, Tiny, and Quill. Others do exist but are not included here as they are opinionated in their design and/or abandoned. However, replacing Atto is not a trivial task. Whilst this approach would work around the issues of finding alternatives to Rangy and the use of deprecated browser APIs, it would not solve the issues of breaking compatibility with all existing third-party plugins; however it can provide a wealth of existing functionality with years of dedicated research and development instead. In many cases the current Moodle plugins can be replaced with existing plugins, negating the need to develop them again for Moodle. . CKEditor The limitations above immediately preclude the use of CKEditor 5, which requires WebPack, and tree shakes the entire platform. It would not be possible for third-party developers to write plugins for multiple versions of Moodle, and a new compilation step would be required, and could only run when all possible plugins are in place. Configuration would not be trivial. . QuillJS QuillJS is an editor framework. Whilst it can provide an editor without any further configuration, to do anything more Moodle would need to create all interfaces using our own existing components and integrate these with the QuillJS APIs. This is closer to the Replace Atto approach, but with a well-supported underlying editor API. This approach would still require all of the current overheads of maintaining an editor, albeit without most of the more complex editor parts. . Tiny Tiny is a full-featured editor, which comes with a number of standard plugins which replace many of Atto s standard features - these include standard formatting, font and colour selection, alignment and justification, undo/redo, word count, source-code viewing, table support, links, emojis, copy, and paste. Many of these features will work as-is for Moodle. Some use the Tiny modal and form frameworks and we would have to decide whether to use these in Moodle, or to rewrite them using the standard Moodle interfaces. This decision would not have to be made immediately. . Other options I looked at a number of other possible editors, but these were either opinionated in their choice of technology (for example jQuery, specific Bootstrap versions), or were abandoned. . Important If you are aware of other editors which meet these criterion, and you feel we should include them in this consideration now is the time to mention them. Given the above analysis, we are currently looking at adopting Tiny version 6 as a replacement for Atto.
### Response:
1.summary: Create TinyMCE H5P plugin
description: This will need the same functionality as the Atto H5P plugin.
2.summary: Create TinyMCE Draft save/restore integration
description: In Atto this is handled as a plugin. We should see whether that is appropriate in this case. There is an existing TinyMCE autosave plugin, but this does not upload to the server (it uses LocalStorage) and is therefore unsuited to our requirements. We should be able to base what we do on that plugiun to some extent, but replacing the LocalStorage with remote storage and changing the back-off to not negatively affect server performance.
3.summary: Ensure that tests continue to work
description: We need to ensure that tests continue to work if Tiny is the default editor (except for Atto-specific tests). We will need to ensure that things like the core editing functionality continue to work (bold, italic, etc.) and that we ahve appropriate steps to click on buttons and menu items too.
4.summary: Create basic integration of Tiny 6.x with Moodle
description: Create the basic integration of Tiny 6 with Moodle, including: basic integration any module loading required to support this instructions to import the latest version of Tiny when required subplugin support (but no subplugins) Things left to separate issues: configuration of the toolbar and/or menu items the creation of plugins for Moodle-specific features (many standard features are already present in Tiny) translation support Other areas to consider: Tiny has its own modal dialogue system ( We need to decide whether to: use their dialogs for our own plugins use our own dialogs for our own plugins use our own dialogs for our plugins and rewrite theirs to use our dialogs create our own Tiny Theme (not recommended by Tiny, and not documented)
5.summary: Add Tiny6 Translation
description: We will need to support translation of the TinyMCE User Interface. The Tiny UI uses the tinymce.addI18N function which takes: a language code (i.e. de for german) an object with: English string Translated string To facilitate this I think well have to write an import tool to take a complete language file and generate a list of translated strings with unique keys, etc. Well then need a lang.php generator which spits out any translated values alongside their original English translation as a JSON object. We can then fetch this from within ouor TinyMCE loader and call it something like: code const langData = await fetch(`$M.cfg.wwwroot/lib/editor/tiny/lang.php/$lang`); tinymce.addI18n(lang, langData); code
6.summary: Supplement loading TinyMCE with a Loader
description: We need to ensure that we load all TinyMCE content using a service loader. This is similar to the lang.php in the current prototype, and existing core services such as: lib/requirejs.php theme/styles.php This should support loading of all TinyMCE core files including: JavaScript: CSS It needs to consider: jsrev cssrev caching of files in tempdir See existing examples for some of the things we need to consider. . Additional thoughts Ideally we should have a core framework for all loaders and we should load very basic information from the plugin on the content they need to load. However I would ideally like to make the TinyMCE plugin available in the Plugins Database for 3.11, and 4.0 to encourage uptake and. authorship of new contrib plugins. It may be that we do make a core loader but bundle it into the editor_tiny plugin for the contrib distribution to support this.
7.summary: Create TinyMCE Media plugin with Image editing
description: Eventually this should be a single plugin which adds: Insert Image Insert Video Drag/Drop handling Media management See for information on drag/drop uploading within TinyMCE. We should find a way to disable the native drag/drop handling when the editor does not support file uploads at all. This should integrate with the Repository API. Decision to be made on whether our custom plugins should use the Moodle dialogues, or the TinyMCE ones. . In this issue This issue is all about getting the _image_ insertion working. That is: drag/drop upload replicating the current TinyMCE standard / Atto standard image features into a Moodle modal ideally displaying a preview If context menus are easy, then they can be done here too, otherwise we can move that to a separate issue. Note: The epic contains a start on the above to get the drag/drop working and to add a fake implementation of the button.
8.summary: Create TinyMCE Media manager functionality in the tiny_media plugin
description: Once the first part of our custom TinyMCE media plugin is implemented (, which adds image functionality), we can introduce media manager functionality, which allows you to manage all media (image/video/audio) content that has been added to the current instance of the editor using the new media plugin. For this iteration of the TinyMCE integration project, this just requires porting the existing media manager functionality from Atto over to TinyMCE 6. Since Atto simply displays that manager in an iframe, this should just be a matter of finding the relevant place in TinyMCE to add this, and taking the same approach (ie displaying an iframe of the file manager in the same way). One of the reasons the manager is required, is that when you delete an image within the editor, the file still exists in the draft area, so is carried over when the content is saved. To avoid that, you must go into the media manager, and delete the image. There are possibly ways this could be handled automatically in future, but this is out of scope for the current work. This may form part of the plugin created in , or will _possibly_ need to be a separate plugin, so deciding that forms part of this issue. Note: To work on this issue, you will need to create a branch based on both and (assuming this is not worked on before those land in core, which is likely).
9.summary: Create Video insertion/editing functionality in the tiny_media plugin
description: Once lands we should extend that plugin to support the creation of video plugins, including: subtitles alternatives drag/drop handling anything else..?
10.summary: Create TinyMCE RecordRTC plugin
description: Create a TinyMCE recordrtc plugin which supports: recording Audio recording Video Usual restrictions apply (requires file area configuration).
11.summary: Configure available headings and formatting options
description: The standard TinyMCE configuration allows for specifying H1 and H2 level headings, which we have traditionally removed in Atto. We need to decide upn the available formatting types, which we can do with the block_formats option: We need to look at whether there are any other options we wish to remove, restrict, or otherwise configure. This may include items such as (not an exhaustive list): text and background colours font family configuration font size configuration
12.summary: Create TinyMCE Accessibility checker
description: New custom plugin shipped with core. This should apply the same checks as the current Atto a11y tool. We should look at whether its possible to incorporate the existing Screenreader helper plugin into the same tool, and whether either/both plugins are still required.
13.summary: Create TinyMCE Equation editor plugin
description: We need to look at how we allow the use of MathJAX (and similar) within TinyMCE.
14.summary: Set editor for editor-specific tests
description: We should make it possible to set the current editor for editor-specific tests. This is required as part of , but is a feature useful for other editors on stable branches.
15.summary: Provide way to set HTML Editor content regardless of the current editor
description: The HTML Editor Behat field type is currently specific to Atto and it should not be. We should amend the API to allow any editor to provide relevant functions to set content.
16.summary: Allow Tiny branding to be disabled by admin
description: This is a part of which will look at alternative solutions too. This gives administrators the option of disabling the Tiny branding. The following is the relevant part of the license: quote Product attribution is required for free users utilizing the Tiny Cloud infrastructure. If using TinyMCE under the MIT license, then support for the open source project would be appreciated by keeping attribution turned on in your editor. For information on TinyMCE attribution requirements, see: Logo & attribution requirements. quote This is further interated at quote While it is unclear under the MIT open source license to include attribution, we do encourage it. TinyMCE open source is provided free of charge, and is made possible by contributions of the community. The larger the community is, the better TinyMCE will become. Please consider including attribution. quote We _can_ remove the branding from the status bar, and move it elsewhere and they provide the following guidance: quote If the status bar is removed or not visible on the editor, you can include attribution per the following: POWERED BY TINY or the Tiny logo placed in a readily visible location in your application when the editor is loaded. The word Tiny or the Tiny logo should have a hyperlink to The location of the product attribution is to be: In the right-hand corner of the status bar of the TinyMCE editor; or An alternate location adjacent to the TinyMCE editor that is no less prominent. quote So a few options spring to mind: give administrators an option of whether to show the branding in the status bar (checkbox, default on) move the attribution to the page footer, and only show it once per page, for example: quote Moodle text editor powered by Tiny| quote The current situation is shown below: !Screen Shot 2022-10-11 at 14.02.22.png|thumbnail!
17.summary: Initial TinyMCE 6 integration for Moodle 4.1
description: This issue is to capture the initial integration of TinyMCE6 with Moodle 4.1.
18.summary: Add Behat step to force editors to save their content back to the textarea
description: TinyMCE (and others) only persist their data back to the textarea at certain points (such as when submitting the form). This meanst that the steps we use to get values do not work as expected. Alongside our settable editors, we should give editors a chance to save persist their values to the textarea.
19.summary: Standardise HTML output when comparing editor values
description: At the moment, the behat editor field is very tilted towards supporting Atto. It should standardise the editor HTML content before comparison. This change also addresses a related bug in the i_type (When I type "This is some text" whereby, if there is a new line character (\n) it is treated differently in Firefox to Chrome. This is solved by swapping any newline with the W3C ENTER character string: \xEE\x80\x87.
20.summary: Behat i_type should normalise newlines
description: The following step will behave different between Chrome and Firefox: code And I type the following text in the "Description" TinyMCE editor: """ This is not important """ code In Chrome, the newline will be treated as a Paragraph tag In Firefox it is treated as a Line break. The i_type function should swap the "\n" character to a W3C ENTER character string: \xEE\x80\x87.
21.summary: Verify the standard toolbar and menu configuration
description: Now that all of the core plugins have been written, we need to look at tweaking and adjusting the toolbar configuration.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.3 upgrade
description: Moodle 3.3 is scheduled for release on Monday 15 May 2017.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.3
description:
2.summary: Upgrade learn.moodle.net to 3.3
description:
3.summary: Upgrade lang.moodle.org to 3.3
description:
4.summary: Upgrade school.demo.moodle.net to 3.3
description:
5.summary: Upgrade demo.moodle.net to 3.3
description:
6.summary: Upgrade dev.moodle.org to 3.3
description:
7.summary: Upgrade moodle.net to 3.3
description:
8.summary: Upgrade download.moodle.org to 3.3
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.3 upgrade
description: Moodle 3.3 is scheduled for release on Monday 15 May 2017.
### Response:
1.summary: Upgrade moodle.org to 3.3
description:
2.summary: Upgrade learn.moodle.net to 3.3
description:
3.summary: Upgrade lang.moodle.org to 3.3
description:
4.summary: Upgrade school.demo.moodle.net to 3.3
description:
5.summary: Upgrade demo.moodle.net to 3.3
description:
6.summary: Upgrade dev.moodle.org to 3.3
description:
7.summary: Upgrade moodle.net to 3.3
description:
8.summary: Upgrade download.moodle.org to 3.3
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle.net initial improvements
description:
| Unsolvable | 1.summary: Moodle.net features brainstorm
description: MOOCH is in a good state but lack of: - WOW design : superb logo, Moodle form that look in a 2012 standard, ... - a UI more friendly. For example: the icon message next to each course description is not really visible, contact form should better be AJAX contact form that you can type on the fly than reloading the entire page ... In my opinion it is not the priority to focus on how it looks for hub admin (one guy) but for anyone else... Can you come up with: 1- some design prototypes 2- in the same time, youll probably come up with many ideas/frustration about the UI. List them :)
2.summary: Add black bar + logo in the header and basic styling to Moodle.net
description:
3.summary: Set up next.moodle.net
description:
4.summary: Automatically tweet/etc course content from Moodle.net
description: Courses are automatically tweeted, which is good (although controlling the tweets would be better -see ) However, when content is added to the database at nothing is broadcast. It would be nice to have course content tweeted also.
5.summary: Change Moodle.net server to use sites.git
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle.net initial improvements
description:
### Response:
1.summary: Moodle.net features brainstorm
description: MOOCH is in a good state but lack of: - WOW design : superb logo, Moodle form that look in a 2012 standard, ... - a UI more friendly. For example: the icon message next to each course description is not really visible, contact form should better be AJAX contact form that you can type on the fly than reloading the entire page ... In my opinion it is not the priority to focus on how it looks for hub admin (one guy) but for anyone else... Can you come up with: 1- some design prototypes 2- in the same time, youll probably come up with many ideas/frustration about the UI. List them :)
2.summary: Add black bar + logo in the header and basic styling to Moodle.net
description:
3.summary: Set up next.moodle.net
description:
4.summary: Automatically tweet/etc course content from Moodle.net
description: Courses are automatically tweeted, which is good (although controlling the tweets would be better -see ) However, when content is added to the database at nothing is broadcast. It would be nice to have course content tweeted also.
5.summary: Change Moodle.net server to use sites.git
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: META: Antivirus scanning improvements
description: The current "hard-coded" way of ClamAV antivirus scanning implementation is not scalable - any improvements to virus scanning needs to be done to existing code, making it more bulky and difficult to use something different than ClamAV (e.g. on non-linux platforms). The most straightforward way to eliminate the scalability issue is to re-implements antivirus scanning using plugins infrastructure. This will allow further improvements of ClamAV (which will become a core plugin ) and allow external contributor to design plugins for other antivirus products. This meta issue has been created to combine core improvements to anti-virus scanning in Moodle. Forum discussion is here|
| Unsolvable | 1.summary: Antivirus: Implement plugins infrastructure for antivirus and create ClamAV plugin.
description: This task will bring antivirus plugins infrastructure to core and move existing ClamAV scanning functionality to plugin level. The improvement does not bring any new features, it is merely a re-factoring of existing functionality.
2.summary: Antivirus: Implement ClamAV virus scanning using unix sockets.
description: Using unix socket is a significantly faster way of scanning files than using command line exec call, but it is only available on unix-like systems. This will be implemented as an option for ClamAV plugin letting user choose if they want to use sockets or command line utility. Command line will remain the default option. . How scanning works For more details on sockets commands that ClamAV accepts, see the manual| In this particular case we use SCAN command with full file path as parameter. ClamAV user should be able to access the file - adding clamav user to www-data group should do the trick. There is no easier way to resolve access unfortunately, granting read permission of uploaded file to everyone is not a good option, thus not used here. Potentially, FILDES command can be used to overcome the need to resolve access, but to use it, minimum php version needs to be bumped to 5.5 (socket_sendmsg function is required that implements needed to build bsd4.4 style package with file descriptor encapsulated). There is a potential possibility of using TCP sockets, e.g. if ClamAV is run on the different system, but it is not good performance-wise (all files will need to be network-transferred for scanning), thus, this option has not been implemented. . Statistical analysis In order to verify a statistical significance between running methods the test script has been designed. The test has been run 100 times for each file of different size (1mb, 10mb, 50mb, 100mb, 500mb) and for each running method (command line and socket), the time taken to scan file has been recorded in milliseconds. General descriptive statistics and graph representing it is shown below. !clamav_stat.jpg|thumbnail! || ||Command line||Unix socket|| |1 Mb|M = 16.738, SD = 5.384|M = 9.360, SD = 2.15| |10 Mb|M = 35.148, SD = 13.890|M = 29.533, SD = 5.270| |50 Mb|M = 8.943, SD = 2.898|M = 0.928, SD = 0.229| |100 Mb|M = 8.967, SD = 2.796|M = 0.619, SD = 0.334| |500 Mb|M = 9.332, SD = 3.101|M = 1.312, SD = 0.388| Two-sample t-test has been applied to groups of variables recorded for same file scanned using two different running methods. The result demonstrated significant difference at confidence interval of 95 in all compared groups of samples. See attached pdf for detailed results.
3.summary: Antivirus: Implement antiviruses_scan_data function to scan data stream.
description: We already have antiviruses_scan_file (--) function designed to scan file. It worth creating a separate function to scan data (stored in variable value). While for command-line running mode it would still need to be stored in the file first (similar to what is done here| but in the ClamAV plugin level), unix-socket running mode gives possibility to scan data directly using INSTREAM command. This function potentially could be used to scan html data submitted by users to avoid issues similar to --.
4.summary: Antivirus clamav: Remove "Quarantine directory" settings parameter.
description: It looks like "Quarantine directory" (antivirus_clamav/quarantinedir) setting that has been moved to antivirus_clamav recently is no longer in use and has been deprecated long time ago in . It can be safely removed.
5.summary: Antivirus: Support remote scanning using TCP sockets.
description: With the growing popularity of containerization, it would be good to extend ClamAV antivirus plugin to support virus scanning using TCP sockets (i.e. over the network). When scalability is in place, this feature eliminates the need to run ClamAV service on each container/host that provides web service, thus reduces complexity and performance overhead. In case of containers, this approach is also aligned with best practice of having one process per container.
6.summary: Increase the Antivirus default chunk size (ClamAV)
description: Back in , kabalin proposed a 1kb chunksize in lib/antivirus/clamav/scanner.php: code / Default socket data stream chunk size / define(ANTIVIRUS_CLAMAV_SOCKET_CHUNKSIZE, 1024); code It turns out that for any reasonably large files, this will result in so many steps (1 million writes to the ClamAV socket for a 1Gb file) that the socket would die with a "fwrite(): send of \d bytes failed with errno=32 Broken pipe" error. For a somewhat reasonable memory consumption, I propose to raise this to 32Mb, statically. (Of course, it would be possible to make it configurable, but its a lot more work. :-) )
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: META: Antivirus scanning improvements
description: The current "hard-coded" way of ClamAV antivirus scanning implementation is not scalable - any improvements to virus scanning needs to be done to existing code, making it more bulky and difficult to use something different than ClamAV (e.g. on non-linux platforms). The most straightforward way to eliminate the scalability issue is to re-implements antivirus scanning using plugins infrastructure. This will allow further improvements of ClamAV (which will become a core plugin ) and allow external contributor to design plugins for other antivirus products. This meta issue has been created to combine core improvements to anti-virus scanning in Moodle. Forum discussion is here|
### Response:
1.summary: Antivirus: Implement plugins infrastructure for antivirus and create ClamAV plugin.
description: This task will bring antivirus plugins infrastructure to core and move existing ClamAV scanning functionality to plugin level. The improvement does not bring any new features, it is merely a re-factoring of existing functionality.
2.summary: Antivirus: Implement ClamAV virus scanning using unix sockets.
description: Using unix socket is a significantly faster way of scanning files than using command line exec call, but it is only available on unix-like systems. This will be implemented as an option for ClamAV plugin letting user choose if they want to use sockets or command line utility. Command line will remain the default option. . How scanning works For more details on sockets commands that ClamAV accepts, see the manual| In this particular case we use SCAN command with full file path as parameter. ClamAV user should be able to access the file - adding clamav user to www-data group should do the trick. There is no easier way to resolve access unfortunately, granting read permission of uploaded file to everyone is not a good option, thus not used here. Potentially, FILDES command can be used to overcome the need to resolve access, but to use it, minimum php version needs to be bumped to 5.5 (socket_sendmsg function is required that implements needed to build bsd4.4 style package with file descriptor encapsulated). There is a potential possibility of using TCP sockets, e.g. if ClamAV is run on the different system, but it is not good performance-wise (all files will need to be network-transferred for scanning), thus, this option has not been implemented. . Statistical analysis In order to verify a statistical significance between running methods the test script has been designed. The test has been run 100 times for each file of different size (1mb, 10mb, 50mb, 100mb, 500mb) and for each running method (command line and socket), the time taken to scan file has been recorded in milliseconds. General descriptive statistics and graph representing it is shown below. !clamav_stat.jpg|thumbnail! || ||Command line||Unix socket|| |1 Mb|M = 16.738, SD = 5.384|M = 9.360, SD = 2.15| |10 Mb|M = 35.148, SD = 13.890|M = 29.533, SD = 5.270| |50 Mb|M = 8.943, SD = 2.898|M = 0.928, SD = 0.229| |100 Mb|M = 8.967, SD = 2.796|M = 0.619, SD = 0.334| |500 Mb|M = 9.332, SD = 3.101|M = 1.312, SD = 0.388| Two-sample t-test has been applied to groups of variables recorded for same file scanned using two different running methods. The result demonstrated significant difference at confidence interval of 95 in all compared groups of samples. See attached pdf for detailed results.
3.summary: Antivirus: Implement antiviruses_scan_data function to scan data stream.
description: We already have antiviruses_scan_file (--) function designed to scan file. It worth creating a separate function to scan data (stored in variable value). While for command-line running mode it would still need to be stored in the file first (similar to what is done here| but in the ClamAV plugin level), unix-socket running mode gives possibility to scan data directly using INSTREAM command. This function potentially could be used to scan html data submitted by users to avoid issues similar to --.
4.summary: Antivirus clamav: Remove "Quarantine directory" settings parameter.
description: It looks like "Quarantine directory" (antivirus_clamav/quarantinedir) setting that has been moved to antivirus_clamav recently is no longer in use and has been deprecated long time ago in . It can be safely removed.
5.summary: Antivirus: Support remote scanning using TCP sockets.
description: With the growing popularity of containerization, it would be good to extend ClamAV antivirus plugin to support virus scanning using TCP sockets (i.e. over the network). When scalability is in place, this feature eliminates the need to run ClamAV service on each container/host that provides web service, thus reduces complexity and performance overhead. In case of containers, this approach is also aligned with best practice of having one process per container.
6.summary: Increase the Antivirus default chunk size (ClamAV)
description: Back in , kabalin proposed a 1kb chunksize in lib/antivirus/clamav/scanner.php: code / Default socket data stream chunk size / define(ANTIVIRUS_CLAMAV_SOCKET_CHUNKSIZE, 1024); code It turns out that for any reasonably large files, this will result in so many steps (1 million writes to the ClamAV socket for a 1Gb file) that the socket would die with a "fwrite(): send of \d bytes failed with errno=32 Broken pipe" error. For a somewhat reasonable memory consumption, I propose to raise this to 32Mb, statically. (Of course, it would be possible to make it configurable, but its a lot more work. :-) )
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: META: Translation site reboot
description: to have a maroon colour scheme.
| Unsolvable | 1.summary: Translation site navigation
description: lang.moodle.org currently has the name Moodle languages portal, however with the new top menu, perhaps it could be renamed Moodle translation? Current menu/submenu items include: Translation docs - AMOS user manual - Help for newcomers - Translation forum - (actually a course named Translating Moodle) Languages forum on moodle.org Language packs - Suggested menu items for future: About - (content to be rewritten) AMOS - Forums - Documentation - (see comment below) Translation credits -
2.summary: Add black sites bar to translation site
description:
3.summary: Move lang.moodle.org to business.srv.in.moodle.com
description:
4.summary: Upgrade lang.moodle.org to 2.7
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: META: Translation site reboot
description: to have a maroon colour scheme.
### Response:
1.summary: Translation site navigation
description: lang.moodle.org currently has the name Moodle languages portal, however with the new top menu, perhaps it could be renamed Moodle translation? Current menu/submenu items include: Translation docs - AMOS user manual - Help for newcomers - Translation forum - (actually a course named Translating Moodle) Languages forum on moodle.org Language packs - Suggested menu items for future: About - (content to be rewritten) AMOS - Forums - Documentation - (see comment below) Translation credits -
2.summary: Add black sites bar to translation site
description:
3.summary: Move lang.moodle.org to business.srv.in.moodle.com
description:
4.summary: Upgrade lang.moodle.org to 2.7
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Front-end development should adhere to a styleguide
description: Front-end development should adhere to a styleguide to make it easier for the community to contribute and to ensure consistency.
| Solvable | 1.summary: Create styleguide
description: Ivan to fill in details
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Front-end development should adhere to a styleguide
description: Front-end development should adhere to a styleguide to make it easier for the community to contribute and to ensure consistency.
### Response:
1.summary: Create styleguide
description: Ivan to fill in details
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Remove Zend framework from core.
description: This is a massive library (12 mb of code) and we are hardly using it. We are also too scared to upgrade it, so it may have security issues etc. We use it in core for xmlrpc, soap and amf web service protocols - all of these should be moved to the plugins DB.
| Unsolvable | 1.summary: Delete Zend framework
description: Final step for this epic.
2.summary: Remove Zend AMF from Moodles AMF web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend AMF from Moodles AMF web service implementation.
3.summary: Remove Zend XML-RPC from Moodles XML-RPC web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend XML-RPC from Moodles XML-RPC web service implementation.
4.summary: Remove Zend SOAP from Moodles SOAP web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend SOAP from Moodles SOAP web service implementation.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Remove Zend framework from core.
description: This is a massive library (12 mb of code) and we are hardly using it. We are also too scared to upgrade it, so it may have security issues etc. We use it in core for xmlrpc, soap and amf web service protocols - all of these should be moved to the plugins DB.
### Response:
1.summary: Delete Zend framework
description: Final step for this epic.
2.summary: Remove Zend AMF from Moodles AMF web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend AMF from Moodles AMF web service implementation.
3.summary: Remove Zend XML-RPC from Moodles XML-RPC web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend XML-RPC from Moodles XML-RPC web service implementation.
4.summary: Remove Zend SOAP from Moodles SOAP web service
description: Since we are removing Zend framework in Moodle core, we have to remove Zend SOAP from Moodles SOAP web service implementation.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Prepare Moodle for PHP 7.2
description: And again, my favorite epic. New PHP version is coming soon (end of 2017)! Moodle 3rd party libraries that use deprecated functions: ADODb - - patch applied and pull request sent upstream. Pull request accepted Bennu - Horde - - all fixed upstream Markdown - - patch applied, it is already in markdown repo but was not tagged yet xhprof - - patch applied and pull request sent upstream scssphp - - patch applied and pull request sent upstream. Pull request accepted CAS - - patch applied and pull request sent upstream. Pull request accepted tcpdf - - patch applied, pull request already existed FPDI - - patch not sent upstream, see comments on the issue htmlpurifier (idn_to_ascii) - - patch applied, pull request sent upstream. Pull request accepted
| Unsolvable | 1.summary: PHP7.2 replace usages of deprecated functions in core
description: PHP7.2 Function create_function() is deprecated
2.summary: PHP7.2 xmlrpc_encode_request() crashes
description: unittests involving call to xmlrpc_encode_request() crash completely on PHP 7.2 RC3 PHP7.0 code $ php -v PHP 7.0.23-1+ubuntu14.04.1+deb.sury.org+1 (cli) (built: Aug 31 2017 12:52:39) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.0.23-1+ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies $ php -r "echo xmlrpc_encode_request(func, text, );" func text code PHP7.2RC4 code $ php -v PHP 7.2.0RC4 (cli) (built: Oct 22 2017 13:39:08) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.2.0-dev, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.2.0RC4, Copyright (c) 1999-2017, by Zend Technologies $ php -r "echo xmlrpc_encode_request(func, text, );" zend_mm_heap corrupted code
3.summary: PHP7.2 Patch bennu library for PHP 7.2. compatibility
description: one single place where bennu uses function create_function that was deprecated in php 7.2 code diff --git a/lib/bennu/iCalendar_properties.php b/lib/bennu/iCalendar_properties.php index 260c42a..6a7a562 100644 --- a/lib/bennu/iCalendar_properties.php +++ b/lib/bennu/iCalendar_properties.php -107,7 +107,10 class iCalendar_property $valarray = explode(\\,, $this->value); // Undo transparent formatting - $replace_function = create_function($a, return rfc2445_undo_value_formatting($a, .$this->val_type.);); + $valtype = $this->val_type; + $replace_function = function($a) use ($valtype) + return rfc2445_undo_value_formatting($a, $valtype); + ; $valarray = array_map($replace_function, $valarray); // Now, if this property cannot have multiple values, dont return as an array code bennu itself seems long asleep
4.summary: Add environment check for versions where PHP 7.2 is NOT supported
description: On Moodle 3.2 and 3.3 add an environment check that PHP 7.2 is not supported See also and
5.summary: PHP7.2 supported on Moodle 3.4 - include in travis. Bump phpunit to 6.4
description: As suggested by matteo (thanks!) bq. should .travis.yml be improved too, for running PHP 7.2 on the master branch only, e.g. via a matrix.include entry?
6.summary: Verify moodle-plugin-ci are working ok with phpunit6 (and php72)
description: This is a followup of , were phpunit6 support was added to 3.4. With that integrated, we should be able to verify that plugins using the cool moodle-pligin-ci| are able to be tested agains 3.4 branches with all current supported PHP versions (70,71 and 72). No changes need to be verified in older branches, just 34 (master right now). Ciao :-)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Prepare Moodle for PHP 7.2
description: And again, my favorite epic. New PHP version is coming soon (end of 2017)! Moodle 3rd party libraries that use deprecated functions: ADODb - - patch applied and pull request sent upstream. Pull request accepted Bennu - Horde - - all fixed upstream Markdown - - patch applied, it is already in markdown repo but was not tagged yet xhprof - - patch applied and pull request sent upstream scssphp - - patch applied and pull request sent upstream. Pull request accepted CAS - - patch applied and pull request sent upstream. Pull request accepted tcpdf - - patch applied, pull request already existed FPDI - - patch not sent upstream, see comments on the issue htmlpurifier (idn_to_ascii) - - patch applied, pull request sent upstream. Pull request accepted
### Response:
1.summary: PHP7.2 replace usages of deprecated functions in core
description: PHP7.2 Function create_function() is deprecated
2.summary: PHP7.2 xmlrpc_encode_request() crashes
description: unittests involving call to xmlrpc_encode_request() crash completely on PHP 7.2 RC3 PHP7.0 code $ php -v PHP 7.0.23-1+ubuntu14.04.1+deb.sury.org+1 (cli) (built: Aug 31 2017 12:52:39) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.0.0, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.0.23-1+ubuntu14.04.1+deb.sury.org+1, Copyright (c) 1999-2017, by Zend Technologies $ php -r "echo xmlrpc_encode_request(func, text, );" func text code PHP7.2RC4 code $ php -v PHP 7.2.0RC4 (cli) (built: Oct 22 2017 13:39:08) ( NTS ) Copyright (c) 1997-2017 The PHP Group Zend Engine v3.2.0-dev, Copyright (c) 1998-2017 Zend Technologies with Zend OPcache v7.2.0RC4, Copyright (c) 1999-2017, by Zend Technologies $ php -r "echo xmlrpc_encode_request(func, text, );" zend_mm_heap corrupted code
3.summary: PHP7.2 Patch bennu library for PHP 7.2. compatibility
description: one single place where bennu uses function create_function that was deprecated in php 7.2 code diff --git a/lib/bennu/iCalendar_properties.php b/lib/bennu/iCalendar_properties.php index 260c42a..6a7a562 100644 --- a/lib/bennu/iCalendar_properties.php +++ b/lib/bennu/iCalendar_properties.php -107,7 +107,10 class iCalendar_property $valarray = explode(\\,, $this->value); // Undo transparent formatting - $replace_function = create_function($a, return rfc2445_undo_value_formatting($a, .$this->val_type.);); + $valtype = $this->val_type; + $replace_function = function($a) use ($valtype) + return rfc2445_undo_value_formatting($a, $valtype); + ; $valarray = array_map($replace_function, $valarray); // Now, if this property cannot have multiple values, dont return as an array code bennu itself seems long asleep
4.summary: Add environment check for versions where PHP 7.2 is NOT supported
description: On Moodle 3.2 and 3.3 add an environment check that PHP 7.2 is not supported See also and
5.summary: PHP7.2 supported on Moodle 3.4 - include in travis. Bump phpunit to 6.4
description: As suggested by matteo (thanks!) bq. should .travis.yml be improved too, for running PHP 7.2 on the master branch only, e.g. via a matrix.include entry?
6.summary: Verify moodle-plugin-ci are working ok with phpunit6 (and php72)
description: This is a followup of , were phpunit6 support was added to 3.4. With that integrated, we should be able to verify that plugins using the cool moodle-pligin-ci| are able to be tested agains 3.4 branches with all current supported PHP versions (70,71 and 72). No changes need to be verified in older branches, just 34 (master right now). Ciao :-)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Default site completion criteria settings for Moodle 4.3
description: This epic contains all the related issues for implementing the default site completion criteria settings. All of the issues belong to the following groups: Ux designs for the completion criteria settings. Clean up the technical debts, to make them easier to maintain. Implement the default site completion criteria settings. . Issue dependency tree Homogenize the course completion conditions Improve the completion conditions form Redesign the Default activity completion page Add site admin link to "Default activity completion" site page Consider the default site completion settings in course creation Use tertiary navigation selector in Course completion settings addHelpButton() function doesnt allow to pass parameters to get_string Order activities by display name in Default activity completion Remove duplicated IDs for the "Save changes" buttons . MVP designs Prototype|
| Unsolvable | 1.summary: addHelpButton() function doesnt allow to pass parameters to get_string
description: addHelpButton() function doesnt allow to pass variables to get_string so tooltip help strings cant use variables to better help the user. Discovered while working on , addHelpButton() doesnt accept variables, so we cant add to "Set reminder in Timeline" the correct string proposed by jverdaguer and the PX team. Once we have this improvement, the help tooltip for "Set reminder in Timeline" should be changed to "This allows you to set a reminder for students to work on this activity. It will appear on the Timeline block in their Dashboard as "Activity type requires action".
2.summary: Create a new Courses > Default settings section in Site administration
description: Create a new Courses > Default settings section in the Site administration and move Course default settings and Course custom fields to the new settings section. !sitelinktodefaultactivitycompletion.png|thumbnail!
3.summary: Redesign the Default activity completion page
description: Redesign the "Default activity completion" page (course/defaultcompletion.php), following the prototype| (except for the "Save changes" button that will be reviewed in ): Update the description text. Display all the completion activities forms on the same page, following the prototype. Remove the checkboxes and bulk activity type edition for the course/defaultcompletion.php page. !coursedefaultcompletionsettings_coursepage.png|thumbnail! Out of scope The way the completion forms are displayed, replacing select with radio buttons will be done in . The sticky footer for the Save changes and all the activity completion forms will be merged in . It will also add automatically the Expand/Collapse all button to the right side of the page following the prototype.
4.summary: Improve the completion conditions form
description: The UX team has redesigned the "Default activity completion" page to display the completion conditions in a different way, hiding some settings (instead of hiding them), to guide the user and display only the conditions that apply based on the current values they select. This issue will review the current activity completion forms displayed in the "Activity completion" section on each activity settings page and also in the Default course completion settings: Meet the styling (checkboxes/radio buttons, strings ) from the prototype| That is: Grading should be moved to the end of the form Completion tracking should be converted to radio buttons. The dependent options (based on the value of different options), like " Student must receive a passing grade to complete this activity" must be hidden instead of disabled. Review the completion criteria settings of each activity type included in Moodle LMS. For the MVP, at least, Assignment, Book, Chat, File, Folder, Forum, IMS Content package, Page, URL, Quiz and Wiki must be reviewed. They can be done here or in separate issues (recommended option to make this easier). The same will happen with the rest of the activities if we have time to review them too. Review the error message displayed when Completion tracking is set to Automatic and no rule is set (currently "When you select automatic completion, you must also enable at least one requirement (below)." is displayed below the selector but it needs to be changed as described in the prototype). !assignmentcompletionconditions_current.png|thumbnail! --> !assignmentcompletionconditions_prototype.png|thumbnail! !quizcompletionconditions_current.png|thumbnail! --> !quizcompletionconditions_prototype.png|thumbnail!
5.summary: Remove duplicated IDs for the "Save changes" buttons
description: While reviewing , jpataleta raised the following accessibility issue: color:c1c7d0_Duplicate IDs for the "Save changes" buttons. Specifically, these are the following IDs that are duplicated:_color color:c1c7d0_fitem_id_submitbutton_color color:c1c7d0_id_submitbutton_color color:c1c7d0_id_error_submitbutton_color While the resolution for this matter is scheduled for , it has been postponed to upcoming releases. To address this accessibility concern in the interim and prevent the occurrence of duplicated IDs for action buttons, we have proactively instituted this solution.
6.summary: Homogenize the course completion conditions
description: Reuse the code between default completion settings and activity forms (to avoid duplicating efforts and missing features, as happened with the grading forum when was implemented). This is how completion settings look on the activity page: !activitycompletionsettings.png|thumbnail! And this is what it looks like from the course completion settings: !coursedefaultcompletionsettings.png|thumbnail!
7.summary: Add support to default site settings to course/defaultcompletion.php
description: Currently, the page course/defaultcompletion.php only supports courses (the id parameter with the course identifier is mandatory). However, it must be adapted to support the site course too (when no id parameter is sent). It implies: Alter \course_completion_defaults table to support null for the course field). This approach is followed by lti_tool_settings: codeFIELD NAME="course" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false" COMMENT="Primary key of course (null for system-wide settings)"/> code Modify course/defaultcompletion.php to remove course as a required parameter and adapt code to support it (capabilities ), to guarantee data will be stored properly in the \course_completion_defaults table with course=null when the course is empty. The site courses wont include Expect completed on dates.
8.summary: Use tertiary navigation selector in Course completion settings
description: The Course completion settings page element for tertiary navigation must be modernised using the new output component recently improved, as the prototype| shows: !tertiarynavigation.png|thumbnail!
9.summary: Consider the default site completion settings during activity creation
description: The following tasks must be done too: When creating a new activity, use course default completion if exists. Otherwise, use site default completion if exists ($course = $SITE). Otherwise default completion should be COMPLETION_TRACKING_NONE instead of COMPLETION_TRACKING_MANUAL Restoring and importing courses will stay the same as the course default is backed up and restored. We are getting rid of "Default completion tracking" setting (in "Advanced features"). Moodle sites using 4.3 onwards could set site default completion up or not, but the system will always use the same logic to set default completion values. A new page called "_Default completion settings"_ should be added to Site administration > Courses > Default settings. This is a new page that contains the new default completion criteria settings for site level !sitelinktodefaultactivitycompletion.png|thumbnail!
10.summary: Order activities by display name in Default activity completion
description: Default completion settings page orders activities alphabetically by internal name, but it should order them by display name. Steps to reproduce: Create a course Navigate to Course > More > Course completion > Default activity completion Confirm the activities are alphabetically ordered (e.g. External Tool, Text and media)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Default site completion criteria settings for Moodle 4.3
description: This epic contains all the related issues for implementing the default site completion criteria settings. All of the issues belong to the following groups: Ux designs for the completion criteria settings. Clean up the technical debts, to make them easier to maintain. Implement the default site completion criteria settings. . Issue dependency tree Homogenize the course completion conditions Improve the completion conditions form Redesign the Default activity completion page Add site admin link to "Default activity completion" site page Consider the default site completion settings in course creation Use tertiary navigation selector in Course completion settings addHelpButton() function doesnt allow to pass parameters to get_string Order activities by display name in Default activity completion Remove duplicated IDs for the "Save changes" buttons . MVP designs Prototype|
### Response:
1.summary: addHelpButton() function doesnt allow to pass parameters to get_string
description: addHelpButton() function doesnt allow to pass variables to get_string so tooltip help strings cant use variables to better help the user. Discovered while working on , addHelpButton() doesnt accept variables, so we cant add to "Set reminder in Timeline" the correct string proposed by jverdaguer and the PX team. Once we have this improvement, the help tooltip for "Set reminder in Timeline" should be changed to "This allows you to set a reminder for students to work on this activity. It will appear on the Timeline block in their Dashboard as "Activity type requires action".
2.summary: Create a new Courses > Default settings section in Site administration
description: Create a new Courses > Default settings section in the Site administration and move Course default settings and Course custom fields to the new settings section. !sitelinktodefaultactivitycompletion.png|thumbnail!
3.summary: Redesign the Default activity completion page
description: Redesign the "Default activity completion" page (course/defaultcompletion.php), following the prototype| (except for the "Save changes" button that will be reviewed in ): Update the description text. Display all the completion activities forms on the same page, following the prototype. Remove the checkboxes and bulk activity type edition for the course/defaultcompletion.php page. !coursedefaultcompletionsettings_coursepage.png|thumbnail! Out of scope The way the completion forms are displayed, replacing select with radio buttons will be done in . The sticky footer for the Save changes and all the activity completion forms will be merged in . It will also add automatically the Expand/Collapse all button to the right side of the page following the prototype.
4.summary: Improve the completion conditions form
description: The UX team has redesigned the "Default activity completion" page to display the completion conditions in a different way, hiding some settings (instead of hiding them), to guide the user and display only the conditions that apply based on the current values they select. This issue will review the current activity completion forms displayed in the "Activity completion" section on each activity settings page and also in the Default course completion settings: Meet the styling (checkboxes/radio buttons, strings ) from the prototype| That is: Grading should be moved to the end of the form Completion tracking should be converted to radio buttons. The dependent options (based on the value of different options), like " Student must receive a passing grade to complete this activity" must be hidden instead of disabled. Review the completion criteria settings of each activity type included in Moodle LMS. For the MVP, at least, Assignment, Book, Chat, File, Folder, Forum, IMS Content package, Page, URL, Quiz and Wiki must be reviewed. They can be done here or in separate issues (recommended option to make this easier). The same will happen with the rest of the activities if we have time to review them too. Review the error message displayed when Completion tracking is set to Automatic and no rule is set (currently "When you select automatic completion, you must also enable at least one requirement (below)." is displayed below the selector but it needs to be changed as described in the prototype). !assignmentcompletionconditions_current.png|thumbnail! --> !assignmentcompletionconditions_prototype.png|thumbnail! !quizcompletionconditions_current.png|thumbnail! --> !quizcompletionconditions_prototype.png|thumbnail!
5.summary: Remove duplicated IDs for the "Save changes" buttons
description: While reviewing , jpataleta raised the following accessibility issue: color:c1c7d0_Duplicate IDs for the "Save changes" buttons. Specifically, these are the following IDs that are duplicated:_color color:c1c7d0_fitem_id_submitbutton_color color:c1c7d0_id_submitbutton_color color:c1c7d0_id_error_submitbutton_color While the resolution for this matter is scheduled for , it has been postponed to upcoming releases. To address this accessibility concern in the interim and prevent the occurrence of duplicated IDs for action buttons, we have proactively instituted this solution.
6.summary: Homogenize the course completion conditions
description: Reuse the code between default completion settings and activity forms (to avoid duplicating efforts and missing features, as happened with the grading forum when was implemented). This is how completion settings look on the activity page: !activitycompletionsettings.png|thumbnail! And this is what it looks like from the course completion settings: !coursedefaultcompletionsettings.png|thumbnail!
7.summary: Add support to default site settings to course/defaultcompletion.php
description: Currently, the page course/defaultcompletion.php only supports courses (the id parameter with the course identifier is mandatory). However, it must be adapted to support the site course too (when no id parameter is sent). It implies: Alter \course_completion_defaults table to support null for the course field). This approach is followed by lti_tool_settings: codeFIELD NAME="course" TYPE="int" LENGTH="10" NOTNULL="false" SEQUENCE="false" COMMENT="Primary key of course (null for system-wide settings)"/> code Modify course/defaultcompletion.php to remove course as a required parameter and adapt code to support it (capabilities ), to guarantee data will be stored properly in the \course_completion_defaults table with course=null when the course is empty. The site courses wont include Expect completed on dates.
8.summary: Use tertiary navigation selector in Course completion settings
description: The Course completion settings page element for tertiary navigation must be modernised using the new output component recently improved, as the prototype| shows: !tertiarynavigation.png|thumbnail!
9.summary: Consider the default site completion settings during activity creation
description: The following tasks must be done too: When creating a new activity, use course default completion if exists. Otherwise, use site default completion if exists ($course = $SITE). Otherwise default completion should be COMPLETION_TRACKING_NONE instead of COMPLETION_TRACKING_MANUAL Restoring and importing courses will stay the same as the course default is backed up and restored. We are getting rid of "Default completion tracking" setting (in "Advanced features"). Moodle sites using 4.3 onwards could set site default completion up or not, but the system will always use the same logic to set default completion values. A new page called "_Default completion settings"_ should be added to Site administration > Courses > Default settings. This is a new page that contains the new default completion criteria settings for site level !sitelinktodefaultactivitycompletion.png|thumbnail!
10.summary: Order activities by display name in Default activity completion
description: Default completion settings page orders activities alphabetically by internal name, but it should order them by display name. Steps to reproduce: Create a course Navigate to Course > More > Course completion > Default activity completion Confirm the activities are alphabetically ordered (e.g. External Tool, Text and media)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Accessibility Issues - Stage 2
description: There are a number of issues that have reported accessibility problems in Moodle. In order for them to be worked on in an organised way, Im establishing this Epic issue so I can link such issue together in one place.
| Unsolvable | 1.summary: Simple changes to main course page to improve accessibility
description: We can not navigate through the course page easily. H3 element are currently the way to understand that we are in a new section - if a content contain an it may be confused as a new section. If we add the region aria role, then we could use screenreader shortcut to navigate between section. Original report: "The main course page could use a few simple changes that would help identify each topic as a region and label them with the proper label. The changes can be made without changing the page structure or visual appearance."
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Accessibility Issues - Stage 2
description: There are a number of issues that have reported accessibility problems in Moodle. In order for them to be worked on in an organised way, Im establishing this Epic issue so I can link such issue together in one place.
### Response:
1.summary: Simple changes to main course page to improve accessibility
description: We can not navigate through the course page easily. H3 element are currently the way to understand that we are in a new section - if a content contain an it may be confused as a new section. If we add the region aria role, then we could use screenreader shortcut to navigate between section. Original report: "The main course page could use a few simple changes that would help identify each topic as a region and label them with the proper label. The changes can be made without changing the page structure or visual appearance."
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: MUA Project: To make Atto Editor more accessible
description: THIS IS AN MUA PROJECT PROPOSAL THAT WILL BE OR HAS BEEN SUBMITTED FOR POSSIBLE MUA FUNDING. ANY EXISTING TRACKER ITEMS THAT THIS MIGHT DUPLICATE SHOULD BE LINKED TO BELOW. Overview At the University of Montreal, we use Atto Editor a lot. With a new law coming into force in 2022 to make all website accessible, we need to make improvements in Atto Editor. I am proposing 6 improvements on the feature. The web accessibility consultant made some recommendations and suggestions, and our user cases are based on them. . Summary Project size: large Audience: university Target users: teachers, students . Goals To make Atto Editor accessible to screen readers. . User Stories _User stories should be specific to each requirement and provide a clear view of what you want the improvement/new feature to accomplish._ As a teacher, I should be able to.... The editor text box is not labeled. It should be tagged with the wording of the question. To do this, the DIV with the ARIA "textbox" role must receive an "aria-labelledby" attribute having as value the identifier of the text of the question. After reading the question, you land on a series of buttons without being warned of the presence of a text editor. Only JAWS mentions that there is a toolbar based on the "toolbar" role of the button group. But that does not constitute an explicit mention of the presence of the publisher. Additionally, users of screenreaders may need assistance getting started with this interactive component. So I suggest placing a little offscreen text that precedes the text editor: "You are going to meet a text editor. If you need help navigating this component, activate the following button: ". The help button, also displayed off-screen, would command the opening of an accessible dialog box, as in the following example Example on the image: !Screen Shot 2020-09-22 at 3.56.26 PM.png!!Screen Shot 2020-09-22 at 3.21.25 PM.png! 2. The first button on the toolbar lets you show or hide the advanced buttons, much like an accordion. However, the reduced or extended state of the bar is not announced. The information should be transmitted by giving the button an "aria-expanded" attribute. As a student, I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, in order to know that there is extendable toolbar. Visual: !Screen Shot 2020-09-25 at 4.22.08 PM.png! . 3. The "Screenreader Helper" button provides information on the current formatting of the selected text. However, to access it on the keyboard or by touch gesture, you have to deploy the advanced toolbar and then go to the penultimate button in a long list. Ideally, the option would be accessible in the basic toolbar, in the first buttons. As a student, I want to find/hear the screenreader helper button on the main toolbar, in order to avoid navigating in the buttons. . Visual: !Screen Shot 2020-09-25 at 4.23.25 PM.png! . 4. Some buttons have a selected or unselected state (eg: Bold, Italic, Superscript ). This state is conveyed visually, but it should also be communicated to screenreaders. To do this, we can add the information in the buttons existing "title" attribute, after the name of the button. Sample code: . Visual: . !Screen Shot 2020-09-25 at 4.24.18 PM.png! . 5. The "Paragraph Style", "Background Color" and "Font Color" buttons open a kind of submenu advertised as a dialog box by screenreaders. This dialog displays a list of styles, but you cannot enter them in VoiceOver and TalkBack: playback continues on the other buttons on the toolbar. In addition, there is no button provided to exit it. You stay trapped inside, unless you hit Escape while in JAWS or NVDA. To make things more functional, it might be better to treat these buttons as menus, that unfold a submenu, instead of making them dialogs. The presence of the submenu would be indicated by the aria-has popup attribute, and the buttons collapsed or expanded state with the aria-expanded attribute. . !Screen Shot 2020-09-25 at 4.25.06 PM.png! 6. Some features like "Insert character", "Emoticon" and "Screenreader helper" open dysfunctional dialogs with screenreaders: a) NVDA reads the title of the dialog box. However, if the dialog does not contain a form field, NVDA says "empty" and the text or the "Close" button cannot be read. JAWS can read the title of the dialog and the "Close" button, but when attempting to browse the contents, the focus moves to the bottom of the dialog, unless there is a form field. b) In JAWS as in NDVA, it is possible to exit the dialogue with Escape. However, the focus may end up elsewhere on the page, when it should get trapped in the dialogue. This same behavior also occurs in TalkBack. c) In VoiceOver and TalkBack, dialog navigation results in frequent loss of focus and it is often necessary to use one-finger selection to restore it. d) I noticed that the "dialog" role was given to each dialog box, but the block encompassing the contents of the dialog did not have a "document" role. Maybe we should start there to solve the problems. In addition, the dialog script should prevent the user from exiting the modal box, unless specifically commanding exit with Escape or the "Close" button. Finally, the close button should logically be read at the end and not at the beginning of the dialog box. An example of an accessible dialog can be found at: Error messages that appear in some dialog boxes are not fully accessible. Among other things, it happens that several fields are in error, but the error message mentions only one. There should be an error message at the start of the dialog box, on which the focus is shifted. This message must include all the fields to be corrected in the form of a list. The explanations of the errors must be included in the of each of these fields. For an example of accessible validation, see the link provided The insertion of pictures and tables is variably supported in the four screen readers. People who use a screenreader should therefore refrain from using these editor features. . !Screen Shot 2020-09-25 at 4.25.54 PM.png! . . Links to existing tracker issues, forum discussions, contrib plugins ... . Requirements ... Include mockups, screenshots from similar products, links to demo sites ... . Further reading ...
| Unsolvable | 1.summary: User story: As an assistive technology user I want to be warned of the presence of a text editor So that I know I can input text and I can make sense of the editors buttons
description: As an assistive technology user I want to be warned of the presence of a text editor So that I know I can input text and I can make sense of the editors buttons
2.summary: User story: As assistive technology user I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, So that I know that there is extendable toolbar
description: As assistive technology user I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, So that I know that there is extendable toolbar
3.summary: User story: As a user, I want to find/hear the screenreader helper button on the main toolbar, in order to avoid navigating in the buttons.
description: As a user I want to find/hear the screenreader helper button on the main toolbar in order to avoid navigating in the buttons
4.summary: User story: As an assistive technology user I want to find/hear the state of editor toolbar buttons So that I know if pressing a button applies a style or removes it
description: As an assistive technology user I want to find/hear the state of editor toolbar buttons So that I know if pressing a button applies a style or removes it
5.summary: User story: As an assistive technology user I want to easily navigate between the elements of a submenu So that I can use all the features the toolbar offers
description: As an assistive technology user I want to easily navigate between the Atto buttons and their submenus So that I can use all the features the toolbar offers
6.summary: User story: As an assistive technology user I want to easily navigate within the Atto editor s dialog interfaces So that I can accomplish my task in the dialog and continue editing my content within the editor
description: As an assistive technology user I want to hear the title of the dialog that is opened So that I know what dialog is opened
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: MUA Project: To make Atto Editor more accessible
description: THIS IS AN MUA PROJECT PROPOSAL THAT WILL BE OR HAS BEEN SUBMITTED FOR POSSIBLE MUA FUNDING. ANY EXISTING TRACKER ITEMS THAT THIS MIGHT DUPLICATE SHOULD BE LINKED TO BELOW. Overview At the University of Montreal, we use Atto Editor a lot. With a new law coming into force in 2022 to make all website accessible, we need to make improvements in Atto Editor. I am proposing 6 improvements on the feature. The web accessibility consultant made some recommendations and suggestions, and our user cases are based on them. . Summary Project size: large Audience: university Target users: teachers, students . Goals To make Atto Editor accessible to screen readers. . User Stories _User stories should be specific to each requirement and provide a clear view of what you want the improvement/new feature to accomplish._ As a teacher, I should be able to.... The editor text box is not labeled. It should be tagged with the wording of the question. To do this, the DIV with the ARIA "textbox" role must receive an "aria-labelledby" attribute having as value the identifier of the text of the question. After reading the question, you land on a series of buttons without being warned of the presence of a text editor. Only JAWS mentions that there is a toolbar based on the "toolbar" role of the button group. But that does not constitute an explicit mention of the presence of the publisher. Additionally, users of screenreaders may need assistance getting started with this interactive component. So I suggest placing a little offscreen text that precedes the text editor: "You are going to meet a text editor. If you need help navigating this component, activate the following button: ". The help button, also displayed off-screen, would command the opening of an accessible dialog box, as in the following example Example on the image: !Screen Shot 2020-09-22 at 3.56.26 PM.png!!Screen Shot 2020-09-22 at 3.21.25 PM.png! 2. The first button on the toolbar lets you show or hide the advanced buttons, much like an accordion. However, the reduced or extended state of the bar is not announced. The information should be transmitted by giving the button an "aria-expanded" attribute. As a student, I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, in order to know that there is extendable toolbar. Visual: !Screen Shot 2020-09-25 at 4.22.08 PM.png! . 3. The "Screenreader Helper" button provides information on the current formatting of the selected text. However, to access it on the keyboard or by touch gesture, you have to deploy the advanced toolbar and then go to the penultimate button in a long list. Ideally, the option would be accessible in the basic toolbar, in the first buttons. As a student, I want to find/hear the screenreader helper button on the main toolbar, in order to avoid navigating in the buttons. . Visual: !Screen Shot 2020-09-25 at 4.23.25 PM.png! . 4. Some buttons have a selected or unselected state (eg: Bold, Italic, Superscript ). This state is conveyed visually, but it should also be communicated to screenreaders. To do this, we can add the information in the buttons existing "title" attribute, after the name of the button. Sample code: . Visual: . !Screen Shot 2020-09-25 at 4.24.18 PM.png! . 5. The "Paragraph Style", "Background Color" and "Font Color" buttons open a kind of submenu advertised as a dialog box by screenreaders. This dialog displays a list of styles, but you cannot enter them in VoiceOver and TalkBack: playback continues on the other buttons on the toolbar. In addition, there is no button provided to exit it. You stay trapped inside, unless you hit Escape while in JAWS or NVDA. To make things more functional, it might be better to treat these buttons as menus, that unfold a submenu, instead of making them dialogs. The presence of the submenu would be indicated by the aria-has popup attribute, and the buttons collapsed or expanded state with the aria-expanded attribute. . !Screen Shot 2020-09-25 at 4.25.06 PM.png! 6. Some features like "Insert character", "Emoticon" and "Screenreader helper" open dysfunctional dialogs with screenreaders: a) NVDA reads the title of the dialog box. However, if the dialog does not contain a form field, NVDA says "empty" and the text or the "Close" button cannot be read. JAWS can read the title of the dialog and the "Close" button, but when attempting to browse the contents, the focus moves to the bottom of the dialog, unless there is a form field. b) In JAWS as in NDVA, it is possible to exit the dialogue with Escape. However, the focus may end up elsewhere on the page, when it should get trapped in the dialogue. This same behavior also occurs in TalkBack. c) In VoiceOver and TalkBack, dialog navigation results in frequent loss of focus and it is often necessary to use one-finger selection to restore it. d) I noticed that the "dialog" role was given to each dialog box, but the block encompassing the contents of the dialog did not have a "document" role. Maybe we should start there to solve the problems. In addition, the dialog script should prevent the user from exiting the modal box, unless specifically commanding exit with Escape or the "Close" button. Finally, the close button should logically be read at the end and not at the beginning of the dialog box. An example of an accessible dialog can be found at: Error messages that appear in some dialog boxes are not fully accessible. Among other things, it happens that several fields are in error, but the error message mentions only one. There should be an error message at the start of the dialog box, on which the focus is shifted. This message must include all the fields to be corrected in the form of a list. The explanations of the errors must be included in the of each of these fields. For an example of accessible validation, see the link provided The insertion of pictures and tables is variably supported in the four screen readers. People who use a screenreader should therefore refrain from using these editor features. . !Screen Shot 2020-09-25 at 4.25.54 PM.png! . . Links to existing tracker issues, forum discussions, contrib plugins ... . Requirements ... Include mockups, screenshots from similar products, links to demo sites ... . Further reading ...
### Response:
1.summary: User story: As an assistive technology user I want to be warned of the presence of a text editor So that I know I can input text and I can make sense of the editors buttons
description: As an assistive technology user I want to be warned of the presence of a text editor So that I know I can input text and I can make sense of the editors buttons
2.summary: User story: As assistive technology user I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, So that I know that there is extendable toolbar
description: As assistive technology user I want to hear by the help of my screen reader, that there is extension of the toolbar, when the Show/hide advanced buttons button is read, So that I know that there is extendable toolbar
3.summary: User story: As a user, I want to find/hear the screenreader helper button on the main toolbar, in order to avoid navigating in the buttons.
description: As a user I want to find/hear the screenreader helper button on the main toolbar in order to avoid navigating in the buttons
4.summary: User story: As an assistive technology user I want to find/hear the state of editor toolbar buttons So that I know if pressing a button applies a style or removes it
description: As an assistive technology user I want to find/hear the state of editor toolbar buttons So that I know if pressing a button applies a style or removes it
5.summary: User story: As an assistive technology user I want to easily navigate between the elements of a submenu So that I can use all the features the toolbar offers
description: As an assistive technology user I want to easily navigate between the Atto buttons and their submenus So that I can use all the features the toolbar offers
6.summary: User story: As an assistive technology user I want to easily navigate within the Atto editor s dialog interfaces So that I can accomplish my task in the dialog and continue editing my content within the editor
description: As an assistive technology user I want to hear the title of the dialog that is opened So that I know what dialog is opened
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Fully review Clean theme in master to list remaining serious issues
description: We need to a) search tracker for all known regressions relating to Clean theme b) run through a full site with data looking for other issues and produce a list here of blockers that would stop Clean becoming the default theme in 2.6.
| Unsolvable | 1.summary: Bootstrap base: import visual fixes from learnmoodle
description: Port all the theme/rendering/css fixes from learnmoodle repository into core Bootstrap.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Fully review Clean theme in master to list remaining serious issues
description: We need to a) search tracker for all known regressions relating to Clean theme b) run through a full site with data looking for other issues and produce a list here of blockers that would stop Clean becoming the default theme in 2.6.
### Response:
1.summary: Bootstrap base: import visual fixes from learnmoodle
description: Port all the theme/rendering/css fixes from learnmoodle repository into core Bootstrap.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Resource upload
description: See
| Solvable | 1.summary: Decide which fields to make available when uploading resources
description: Many fields have been defined for resource metadata during the research phase: This was based on the work of Phil Barker and I: (see also the linked spreadsheets) Some fields like language or resource type should be linked to a taxonomy: ---- While until now resources are only links to external resources, we should be smarter about what metadata we collect and store about uploaded resources, among other things, this is to power search/filtering/discovery. Importantly, all fields are optional. ---- These fields have actually already been added to the back-end and client API: code:java "name": "content", "type": "name": "String" , "name": "educationalUse" , "name": "inLanguage" , "name": "isAccesibleForFree", "type": "name": "Boolean" , "name": "learningResourceType", "type": "name": "String" , "name": "license", "type": "name": "String" , "name": "primaryLanguage", "type": "name": "String" , "name": "publicAccess", "type": "name": "Boolean" , "name": "sameAs", "type": "name": "String" , "name": "timeRequired", "type": "name": "Int" , "name": "typicalAgeRange", "type": "name": "String" code
2.summary: Create endpoints to allow resource-upload to collections
description: This should build on the previous work with image uploads, and store files in the instances cloud storage of choice. We should save a checksum of uploaded resources (and federate that metadata, incl storing it in the mothership search index, so we can surface when the same resource is posted in different collections, even on different instances)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Resource upload
description: See
### Response:
1.summary: Decide which fields to make available when uploading resources
description: Many fields have been defined for resource metadata during the research phase: This was based on the work of Phil Barker and I: (see also the linked spreadsheets) Some fields like language or resource type should be linked to a taxonomy: ---- While until now resources are only links to external resources, we should be smarter about what metadata we collect and store about uploaded resources, among other things, this is to power search/filtering/discovery. Importantly, all fields are optional. ---- These fields have actually already been added to the back-end and client API: code:java "name": "content", "type": "name": "String" , "name": "educationalUse" , "name": "inLanguage" , "name": "isAccesibleForFree", "type": "name": "Boolean" , "name": "learningResourceType", "type": "name": "String" , "name": "license", "type": "name": "String" , "name": "primaryLanguage", "type": "name": "String" , "name": "publicAccess", "type": "name": "Boolean" , "name": "sameAs", "type": "name": "String" , "name": "timeRequired", "type": "name": "Int" , "name": "typicalAgeRange", "type": "name": "String" code
2.summary: Create endpoints to allow resource-upload to collections
description: This should build on the previous work with image uploads, and store files in the instances cloud storage of choice. We should save a checksum of uploaded resources (and federate that metadata, incl storing it in the mothership search index, so we can surface when the same resource is posted in different collections, even on different instances)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Refactoring old code, databases, and functionality
description: Refactoring old code, databases, and functionality
| Unsolvable | 1.summary: Refactor DB/Ecto schema
description: 1. broadly flatten the database rather than have this aspects thing, an initial schema is at 1a. it has an addressing table to be used for inbox/outbox and timelines (addressing_type would be to cc etc) 1b. activities table which just points back to objects table 1c. context_local_id to do away with non-virtual collections, used for: - collection object indicates the parent community - resource object indicates the parent collection - thread object indicates the parent community - comment object indicates the parent thread (or other activity) 1d. in this approach the objects table is the central data store and everything else is mostly foreign keys and counts to make querying more straightforward. 1e. of course nothing stops us from duplicating the content in dedicated fields in the mn_ tables to make things even easier 2. go back to plain ecto models 3. remove fields and tables were not using but had to be in many tables where they werent used because of the activitypub libraries 4. put activitypub into the new objects json table, and use foreign keys in the MN tables to refer directly to data in objects table
2.summary: Refactor some of MN backend
description: Rewrite some MN modules and functions as required to make happen, while preserving existing features (and avoid breaking changes to the GraphQL API) and planning for future features in the roadmap.
3.summary: Refactor frontend queries/mutations based on any changes to MN GraphQL API
description: In case leads to any API changes.
4.summary: Refactor how federation module(s) interact with MN backend modules
description: How will incoming activities in the AP objects table be transformed and copied into MN tables, so that they are available to client API queries? We will have to parse meaning out of the AP object and put it into a table. Same the other way around, any object created/updated, or activities like like/follow/flag will need to trigger the creation of AP objects/activities which need to be persisted in the objects table and federated. Fetched objects are currently persisted in the JSON object table, persisting it in the current DB was causing issues. We will need to translate them over to the new MN tables. If/when we have persistence, could we spawn processes to fetch and store in the background? Eventually all AP stuff should be stored as JSON so yes, so well also store outgoing activities in the objects table Lets add a public boolean just like we have for local so that we can make it easy to filter only for public stuff and avoid some mistakes leading to leaks.
5.summary: Define how MN receives, stores, and displays non-MN Activities (eg. Announce) and Objects (eg. Video/Event)
description: This is one for the whole team to discuss, as it has as much to do with UX as implementation.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Refactoring old code, databases, and functionality
description: Refactoring old code, databases, and functionality
### Response:
1.summary: Refactor DB/Ecto schema
description: 1. broadly flatten the database rather than have this aspects thing, an initial schema is at 1a. it has an addressing table to be used for inbox/outbox and timelines (addressing_type would be to cc etc) 1b. activities table which just points back to objects table 1c. context_local_id to do away with non-virtual collections, used for: - collection object indicates the parent community - resource object indicates the parent collection - thread object indicates the parent community - comment object indicates the parent thread (or other activity) 1d. in this approach the objects table is the central data store and everything else is mostly foreign keys and counts to make querying more straightforward. 1e. of course nothing stops us from duplicating the content in dedicated fields in the mn_ tables to make things even easier 2. go back to plain ecto models 3. remove fields and tables were not using but had to be in many tables where they werent used because of the activitypub libraries 4. put activitypub into the new objects json table, and use foreign keys in the MN tables to refer directly to data in objects table
2.summary: Refactor some of MN backend
description: Rewrite some MN modules and functions as required to make happen, while preserving existing features (and avoid breaking changes to the GraphQL API) and planning for future features in the roadmap.
3.summary: Refactor frontend queries/mutations based on any changes to MN GraphQL API
description: In case leads to any API changes.
4.summary: Refactor how federation module(s) interact with MN backend modules
description: How will incoming activities in the AP objects table be transformed and copied into MN tables, so that they are available to client API queries? We will have to parse meaning out of the AP object and put it into a table. Same the other way around, any object created/updated, or activities like like/follow/flag will need to trigger the creation of AP objects/activities which need to be persisted in the objects table and federated. Fetched objects are currently persisted in the JSON object table, persisting it in the current DB was causing issues. We will need to translate them over to the new MN tables. If/when we have persistence, could we spawn processes to fetch and store in the background? Eventually all AP stuff should be stored as JSON so yes, so well also store outgoing activities in the objects table Lets add a public boolean just like we have for local so that we can make it easy to filter only for public stuff and avoid some mistakes leading to leaks.
5.summary: Define how MN receives, stores, and displays non-MN Activities (eg. Announce) and Objects (eg. Video/Event)
description: This is one for the whole team to discuss, as it has as much to do with UX as implementation.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.8 upgrade
description: Moodle 3.8 is scheduled for release on Monday 18 November 2019.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.8
description:
2.summary: Upgrade learn.moodle.org to 3.8
description:
3.summary: Upgrade lang.moodle.org to 3.6.7
description:
4.summary: Upgrade school.moodledemo.net to 3.8
description:
5.summary: Upgrade sandbox.moodledemo.net to 3.8
description:
6.summary: Upgrade archive.moodle.net to 3.8
description:
7.summary: Upgrade stats.moodle.org to 3.8
description:
8.summary: Upgrade dev.moodle.org to 3.6.7
description:
9.summary: Upgrade download.moodle.org to latest 3.5.x
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.8 upgrade
description: Moodle 3.8 is scheduled for release on Monday 18 November 2019.
### Response:
1.summary: Upgrade moodle.org to 3.8
description:
2.summary: Upgrade learn.moodle.org to 3.8
description:
3.summary: Upgrade lang.moodle.org to 3.6.7
description:
4.summary: Upgrade school.moodledemo.net to 3.8
description:
5.summary: Upgrade sandbox.moodledemo.net to 3.8
description:
6.summary: Upgrade archive.moodle.net to 3.8
description:
7.summary: Upgrade stats.moodle.org to 3.8
description:
8.summary: Upgrade dev.moodle.org to 3.6.7
description:
9.summary: Upgrade download.moodle.org to latest 3.5.x
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Moodle 4.0 onboarding
description: This epic covers the issues we will work on to improve Moodles onboarding experience for new user and freshly installed sites. Prototypes Teacher / admin onboarding| Student onboarding|
| Solvable | 1.summary: Improve and simplify design of user tours
description: As part of Moodle 4.0 we are working on a new onboarding experience. This includes some changes to how the user tour modals look and work. The work done to update the user tour modal as part of this issue should be captured in the component library. Specification to follow . Moodle 4.0 user tours redesign . Structure AFAIK, current user tours use the modal bootstrap component which is great for dialogues boxes but offers too many UI elements for simple and elegant user tours. I suggest using the modal component as the base to create our own user tour box component. This is what, IMO, we should and should not change when creating a new component user tour box when comparing it to the bootstrap modal component. . Width The new user tours have a width of 400px instead of the current 500px existing ones. This smaller size just seems more friendly to users and allows us to display images with a better proportion ratio. However, I m not sure if this should be a rule since user tours are also displayed in the middle of the screen on different occasions. Maybe we could set a rule for its size, or it should be customisable? Now it looks like this: !width-500-px.png|width=500! It could look like this: !width-400-px.png|width=400! . Borders For a cleaner look, we should drop the borders that separate the title, content and buttons. How it looks now: !drop-borders.png|width=500! How it could look then: !no-borders.png|width=500! . Close button (x) We should drop the x button as well, making the process more straightforward and simulating a more natural dialogue process where the user reads the message and answers it by clicking on the button. How it looks now: !drop-close-button.png|width=500! How it could look then: !no-close-button.png|width=500! . Arrows !arrows-no-change.png|width=500! No changes in either the way it behaves or looks. (Just mentioning this because in the Figma prototypes these are not illustrated due to time constraints.) . Buttons alignment Not a mandatory thing, but aligning buttons to the left is a pattern that was heavily used in Moodle 4 overall redesign. It makes it more readable (even more when the borders that separate text and buttons are gone). Now it looks like this: !button-alignment-right.png|width=500! It would look like this: !button-alignment-left.png|width=500! . Flow . Single-step user tour Right now it seems that the only button that s always displayed is the user tours, regarding their complexity, is the End tour one. In the new design, tours with a single step will have their own customisable agreement button - that functionality is covered by , so does not need to be handled as part of this issue. . Multi-step user tour . Previous button Users rarely want to navigate back in a user tour, so we should remove the Previous button. So this: !previous-button.png|width=500! Would look like this: !no-previous-button.png|width=500! . Next button If possible, we should inform users of how many steps are ahead in some user tours. This gives them more control over it and less probability of skipping it. We could display this steps indicator in the agreement button itself; however, if this approach makes the development more expensive, we could find another way to display it. Note: The step count is being implemented as part of , so in this issue we just need to move that information into the "Next" button and adjust it to match the below prototype. It currently looks like this: !next-button.png|width=500! It could look like this: !next-button-alt.png|width=500! . End tour button As mentioned above, this should not be the button that is displayed by default on single-step tours. This button should only appear when there is more than one step in the user tour and it should allow the user to abort the user tour completely. Currently, it looks like this: !end-tour-button.png|width=500! It could look like this: !skip-button.png|width=500! . Result Putting all previous changes together should make the user tours look like this: Single-step: !result-one-step.png|width=400! Multi-step: !result-multi-step.png|width=400!
2.summary: User Tour: Include ATTO text editor
description: The user tour in 3.4 is a great addition, but I am unable to add links in the content box to our support site. The text box is just text with no formatting or hyperlinks. Can ATTO be used for the content box?
3.summary: Implement customisable confirmation button for single step user tours
description: . Single-step user tour Right now it seems that the only button that s always displayed is the user tours, regarding their complexity, is the End tour one, which acts more like what we commonly find in other products user tours as Skip . In the new design, tours with a single step should not display this "skip" button that dismisses the tour, but instead will show some kind of agreement button. The button text should also be customizable by each user tour, to make user tours sound less robotic. This is how it looks now: !single-step-tour.png|thumbnail! How it could look: !customisable-single-confirmation-button.png|thumbnail!
4.summary: Remove current user tours
description: Theres no point in explaining the activity information to users. I tested the new (Moodle 4) layout and never saw users getting confused with the activity information. Its plenty self-explanatory as it is. I understand that the goal when adding these user tours was to highlight the changes in Moodle 3.11 to migrating 3.10 users. However, I dont think its worth disturbing (and even confusing) users who didnt use Moodle before with information that only makes sense for users migrating between different versions. !Screenshot 2021-10-11 at 14.13.49.png|width=655,height=243! EDIT: We also have old dashboard, messaging, and old boost user tours in there. I see no reason to retain these. Lets remove all old user tours. !Screen Shot 2021-10-12 at 1.24.57 pm.png|width=658,height=79,thumbnail!
5.summary: Add new user tours
description: Page: Dashboard Target: Block panel toggle Roles: Student / Teacher / Admin (All roles) Title: "Expand to explore!" Message: "Each page may contain different functionalities in the side panel" Confirmation button: "Got it!" Image: tour_dashboard_1.png Example: !dashboard_example.png|width=600! Page: My courses Target: Menu icon Roles: Teacher / Admin / Whichever user has access to this menu Title: "Courses and categories" Message: "Expand this menu to go to the course management page, where you can duplicate, delete courses and much more" Confirmation button: "I understand" Image: tour_mycourses_1.png Example: !mycourses_example.png|width=600! Page: Course page (1 of 3) - Admin Target: "Edit mode" toggle Roles: Teacher / Admin / Users with permission to turn on edit mode Title: "Activate editing mode first" Message: "Add new resources to this course or edit the existing ones" Confirmation button: "Next (1/3)" Image: tour_course_admin_1.png Example: !course_admin_1_example.png|width=600! Page: Course page (2 of 3) - Admin Target: Course index container Roles: Teacher / Admin Title: "Course index" Message: "Drag and drop the activities to easily re-order the course content" Confirmation button: "Next (2/3)" Image: tour_course_admin_2.png Example: !course_admin_2_example.png|width=600! Page: Course page (3 of 3) - Admin Target: Announcements forum Roles: Teacher / Admin Title: "Something to say?" Message: "Use this forum to keep in touch with everyone enrolled on this course" Confirmation button: "Cool, thanks!" Image: tour_course_admin_3.png Example: !course_admin_3_example.png|width=600! color:de350bNote: This third step was added last minute since its mandatory for us to include an "Announcements forums" for each course page when they are created. Neither this step, its image or text was properly tested at this point.color Page: Course page - Student Target: Course index container Roles: Student Title: "Don t get lost!" Message: "Use the course index to quickly browse through the activities and to keep your progress under control" Confirmation button: "Cool, thanks!" Image: tour_course_student_1.png Example: !couse_student_example.png|width=600!
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Moodle 4.0 onboarding
description: This epic covers the issues we will work on to improve Moodles onboarding experience for new user and freshly installed sites. Prototypes Teacher / admin onboarding| Student onboarding|
### Response:
1.summary: Improve and simplify design of user tours
description: As part of Moodle 4.0 we are working on a new onboarding experience. This includes some changes to how the user tour modals look and work. The work done to update the user tour modal as part of this issue should be captured in the component library. Specification to follow . Moodle 4.0 user tours redesign . Structure AFAIK, current user tours use the modal bootstrap component which is great for dialogues boxes but offers too many UI elements for simple and elegant user tours. I suggest using the modal component as the base to create our own user tour box component. This is what, IMO, we should and should not change when creating a new component user tour box when comparing it to the bootstrap modal component. . Width The new user tours have a width of 400px instead of the current 500px existing ones. This smaller size just seems more friendly to users and allows us to display images with a better proportion ratio. However, I m not sure if this should be a rule since user tours are also displayed in the middle of the screen on different occasions. Maybe we could set a rule for its size, or it should be customisable? Now it looks like this: !width-500-px.png|width=500! It could look like this: !width-400-px.png|width=400! . Borders For a cleaner look, we should drop the borders that separate the title, content and buttons. How it looks now: !drop-borders.png|width=500! How it could look then: !no-borders.png|width=500! . Close button (x) We should drop the x button as well, making the process more straightforward and simulating a more natural dialogue process where the user reads the message and answers it by clicking on the button. How it looks now: !drop-close-button.png|width=500! How it could look then: !no-close-button.png|width=500! . Arrows !arrows-no-change.png|width=500! No changes in either the way it behaves or looks. (Just mentioning this because in the Figma prototypes these are not illustrated due to time constraints.) . Buttons alignment Not a mandatory thing, but aligning buttons to the left is a pattern that was heavily used in Moodle 4 overall redesign. It makes it more readable (even more when the borders that separate text and buttons are gone). Now it looks like this: !button-alignment-right.png|width=500! It would look like this: !button-alignment-left.png|width=500! . Flow . Single-step user tour Right now it seems that the only button that s always displayed is the user tours, regarding their complexity, is the End tour one. In the new design, tours with a single step will have their own customisable agreement button - that functionality is covered by , so does not need to be handled as part of this issue. . Multi-step user tour . Previous button Users rarely want to navigate back in a user tour, so we should remove the Previous button. So this: !previous-button.png|width=500! Would look like this: !no-previous-button.png|width=500! . Next button If possible, we should inform users of how many steps are ahead in some user tours. This gives them more control over it and less probability of skipping it. We could display this steps indicator in the agreement button itself; however, if this approach makes the development more expensive, we could find another way to display it. Note: The step count is being implemented as part of , so in this issue we just need to move that information into the "Next" button and adjust it to match the below prototype. It currently looks like this: !next-button.png|width=500! It could look like this: !next-button-alt.png|width=500! . End tour button As mentioned above, this should not be the button that is displayed by default on single-step tours. This button should only appear when there is more than one step in the user tour and it should allow the user to abort the user tour completely. Currently, it looks like this: !end-tour-button.png|width=500! It could look like this: !skip-button.png|width=500! . Result Putting all previous changes together should make the user tours look like this: Single-step: !result-one-step.png|width=400! Multi-step: !result-multi-step.png|width=400!
2.summary: User Tour: Include ATTO text editor
description: The user tour in 3.4 is a great addition, but I am unable to add links in the content box to our support site. The text box is just text with no formatting or hyperlinks. Can ATTO be used for the content box?
3.summary: Implement customisable confirmation button for single step user tours
description: . Single-step user tour Right now it seems that the only button that s always displayed is the user tours, regarding their complexity, is the End tour one, which acts more like what we commonly find in other products user tours as Skip . In the new design, tours with a single step should not display this "skip" button that dismisses the tour, but instead will show some kind of agreement button. The button text should also be customizable by each user tour, to make user tours sound less robotic. This is how it looks now: !single-step-tour.png|thumbnail! How it could look: !customisable-single-confirmation-button.png|thumbnail!
4.summary: Remove current user tours
description: Theres no point in explaining the activity information to users. I tested the new (Moodle 4) layout and never saw users getting confused with the activity information. Its plenty self-explanatory as it is. I understand that the goal when adding these user tours was to highlight the changes in Moodle 3.11 to migrating 3.10 users. However, I dont think its worth disturbing (and even confusing) users who didnt use Moodle before with information that only makes sense for users migrating between different versions. !Screenshot 2021-10-11 at 14.13.49.png|width=655,height=243! EDIT: We also have old dashboard, messaging, and old boost user tours in there. I see no reason to retain these. Lets remove all old user tours. !Screen Shot 2021-10-12 at 1.24.57 pm.png|width=658,height=79,thumbnail!
5.summary: Add new user tours
description: Page: Dashboard Target: Block panel toggle Roles: Student / Teacher / Admin (All roles) Title: "Expand to explore!" Message: "Each page may contain different functionalities in the side panel" Confirmation button: "Got it!" Image: tour_dashboard_1.png Example: !dashboard_example.png|width=600! Page: My courses Target: Menu icon Roles: Teacher / Admin / Whichever user has access to this menu Title: "Courses and categories" Message: "Expand this menu to go to the course management page, where you can duplicate, delete courses and much more" Confirmation button: "I understand" Image: tour_mycourses_1.png Example: !mycourses_example.png|width=600! Page: Course page (1 of 3) - Admin Target: "Edit mode" toggle Roles: Teacher / Admin / Users with permission to turn on edit mode Title: "Activate editing mode first" Message: "Add new resources to this course or edit the existing ones" Confirmation button: "Next (1/3)" Image: tour_course_admin_1.png Example: !course_admin_1_example.png|width=600! Page: Course page (2 of 3) - Admin Target: Course index container Roles: Teacher / Admin Title: "Course index" Message: "Drag and drop the activities to easily re-order the course content" Confirmation button: "Next (2/3)" Image: tour_course_admin_2.png Example: !course_admin_2_example.png|width=600! Page: Course page (3 of 3) - Admin Target: Announcements forum Roles: Teacher / Admin Title: "Something to say?" Message: "Use this forum to keep in touch with everyone enrolled on this course" Confirmation button: "Cool, thanks!" Image: tour_course_admin_3.png Example: !course_admin_3_example.png|width=600! color:de350bNote: This third step was added last minute since its mandatory for us to include an "Announcements forums" for each course page when they are created. Neither this step, its image or text was properly tested at this point.color Page: Course page - Student Target: Course index container Roles: Student Title: "Don t get lost!" Message: "Use the course index to quickly browse through the activities and to keep your progress under control" Confirmation button: "Cool, thanks!" Image: tour_course_student_1.png Example: !couse_student_example.png|width=600!
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.0
description: There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Many have a deadline of 3.0. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
| Unsolvable | 1.summary: Remove get_incomplete_criteria()
description: Deprecated in
2.summary: Remove enrol_plugin::instance_deleteable()
description: Follow on from
3.summary: Remove strings deprecated in 2.8
description: Remove strings from language files under the heading "Deprecated in Moodle 2.8" and the respective lines in deprecated.txt files See also
4.summary: Make $plugin->component required for all plugins
description: To help the diagnosis and auto-detection (in Moodle core - - and in the Plugins directory), it would help to make the $plugin->component required at some point. Moodle 3.0 looks like a reasonable candidate. The syntax has been supported and recommended since Moodle 2.0 (, 3e858ea737739197809013636d0ed942131ffb3e) so its been there long enough to give plugin maintainers time to include it (and recent plugin submissions all have it).
5.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php in 3.0
description: It looks like we have not done it for a while. lib/deprecatedlib.php contains lots of functions that were deprecated in 2.8, 2.7, 2.6, 2.5 and even 2.4 They should be all substituted with throwing exception as described in
6.summary: Remove deprecated grade.php from mod/lti
description: LTIs grade.php was deprecated in . If its agreeable, lets remove the deprecated file.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Epic: Collect together deprecated and planned code changes for Moodle 3.0
description: There are a number of parts of the Moodle codebase that have been marked as deprecated as a warning to developers not to use these functions as they will be removed in future. Many have a deadline of 3.0. Each of these deprecated functions, especially those in Moodle core code, should have an MDL issue associated with it. In order to time the removal of these deprecated functions issues and not lose sight of them, this issue will be used to collect them together.
### Response:
1.summary: Remove get_incomplete_criteria()
description: Deprecated in
2.summary: Remove enrol_plugin::instance_deleteable()
description: Follow on from
3.summary: Remove strings deprecated in 2.8
description: Remove strings from language files under the heading "Deprecated in Moodle 2.8" and the respective lines in deprecated.txt files See also
4.summary: Make $plugin->component required for all plugins
description: To help the diagnosis and auto-detection (in Moodle core - - and in the Plugins directory), it would help to make the $plugin->component required at some point. Moodle 3.0 looks like a reasonable candidate. The syntax has been supported and recommended since Moodle 2.0 (, 3e858ea737739197809013636d0ed942131ffb3e) so its been there long enough to give plugin maintainers time to include it (and recent plugin submissions all have it).
5.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php in 3.0
description: It looks like we have not done it for a while. lib/deprecatedlib.php contains lots of functions that were deprecated in 2.8, 2.7, 2.6, 2.5 and even 2.4 They should be all substituted with throwing exception as described in
6.summary: Remove deprecated grade.php from mod/lti
description: LTIs grade.php was deprecated in . If its agreeable, lets remove the deprecated file.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Implement an analytics engine in Moodle
description: Project page: This epic is used to collect issues related to this project.
| Unsolvable | 1.summary: Convert current tool_inspire plugin to core API + plugin
description: This issue is about moving to core
2.summary: Manage access to models management page through a new capability
description: This would allow site admins to grant a new capability to researchers without having to give them site:config capability.
3.summary: Allow models to override machine learning predictions with hardcoded rules
description: At the moment all predictions pass through the machine learning backend, there are some models that dont need to rely predictions on a machine learning supervised learning and they can hardcode predictions based on the indicators and generate insights. Some specific things about these models: No need for training Evaluation of the algorithm will always be 100 so not sure if there is a point allowing evaluation of these models.
4.summary: Limit tool_models and report_insights access by a new capability for researchers
description: Researchers are very interested in analytics stuff, they are not usually Moodle site admins nor site managers, instead of controlling tool_models and report_insights access with moodle/site:config we could use a new capability (by default only for admins / managers) for it so sites interested in giving access to researchers could create a role with that capability at system context. An extension of this would be to add a research role to moodle default roles. There are some actions that site admins may still want to control, running models evaluation from the browser may be a heavy task, so we may have to create another capability for that and let site admins choose what they allow researchers to do.
5.summary: Move project inspire python plugin to moodlehq account
description: The python ml backend uses to run evaluation, training and prediction processes. We should: Move to moodlehq github account Fix Tag a new version for Moodle 3.4.x branch Create a moodlehq account in and upload the latest build Add a point to so we create a new tag for each supported Moodle major version
6.summary: Make predict_php 7.x requirement clearer
description: The PHP predictions processor requires PHP 7.x to work because it is what php-ml library requires. We need to make this requirement clearer. We can not do it at plugin level because people can just use the python predictions processor or any other plugin they write, but we could show a warning message in the admin settings page if the server php version is lower than 7.0 and the PHP predictions processor is selected (it is the default value)
7.summary: Add support for social breadth level 2
description: I added a // TODO Add support for other levels than 1. in classes/local/indicator/activity_social_breadth.php because I didnt have time to code other social breadth levels. Level 2 should be pretty easy to add (just check any_write). From level 3 it starts depending on the activity, most of the stuff required to code from level 3 is available in the parent class community_of_inquiry_activity but we may require to add extra stuff to calculate them all.
8.summary: Replace get_activity_type indicators method for an automated solution
description: We could not automate it when indicators were part of tool_inspire, but we can do it now that they are in core as indicator classes namespace include the activity type.
9.summary: Move activities indicators under each activity directory
description: All indicators are in analytics/classes/local/indicator they should be move to the activity directory along with the indicator name. e.g. mod/assign/classes/analytics/indicator/
10.summary: Skip mlbackend_php tests if PHP < 7.0
description: mlbackend_php requires PHP 7.0, we should skip its tests if the PHP CLI version is lower than PHP 7.0
11.summary: Remove built-in models once tool_models is deleted.
description: Moodle built-in models are installed along with tool_models to separate analytics API and the prediction models that come with moodle, Im not 100 convinced this is a good idea but it sounds better to me than to mix analytics base classes with specific-models targets. If the tool is removed the 2 cron tasks that run training and predictions will not be used any more, but people can still use the API function that these tasks execute to run training and prediction. Conceptually this is what makes more sense to me and people removing tool_models does not make much sense to me either. Open to discussion, but as pointed out by ankit_frenz if we set built-in models targets in tool_models namespace we should uninstall them if the tool is uninstalled.
12.summary: Convert student enrolments analyser get samples methods to enrol API functions
description: We should avoid having direct DB queries to other subsystems db tables. We should instead use enrol API methods.
13.summary: Fix CiBoT complaints
description: There shouldnt be anything really worrying, there are missing php doc blocks and stuff like that
14.summary: Review unit test coverage
description: There are unit tests for the model and for training, prediction and evaluation processes, but there are some critical areas that are not covered by unit test and they should.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Implement an analytics engine in Moodle
description: Project page: This epic is used to collect issues related to this project.
### Response:
1.summary: Convert current tool_inspire plugin to core API + plugin
description: This issue is about moving to core
2.summary: Manage access to models management page through a new capability
description: This would allow site admins to grant a new capability to researchers without having to give them site:config capability.
3.summary: Allow models to override machine learning predictions with hardcoded rules
description: At the moment all predictions pass through the machine learning backend, there are some models that dont need to rely predictions on a machine learning supervised learning and they can hardcode predictions based on the indicators and generate insights. Some specific things about these models: No need for training Evaluation of the algorithm will always be 100 so not sure if there is a point allowing evaluation of these models.
4.summary: Limit tool_models and report_insights access by a new capability for researchers
description: Researchers are very interested in analytics stuff, they are not usually Moodle site admins nor site managers, instead of controlling tool_models and report_insights access with moodle/site:config we could use a new capability (by default only for admins / managers) for it so sites interested in giving access to researchers could create a role with that capability at system context. An extension of this would be to add a research role to moodle default roles. There are some actions that site admins may still want to control, running models evaluation from the browser may be a heavy task, so we may have to create another capability for that and let site admins choose what they allow researchers to do.
5.summary: Move project inspire python plugin to moodlehq account
description: The python ml backend uses to run evaluation, training and prediction processes. We should: Move to moodlehq github account Fix Tag a new version for Moodle 3.4.x branch Create a moodlehq account in and upload the latest build Add a point to so we create a new tag for each supported Moodle major version
6.summary: Make predict_php 7.x requirement clearer
description: The PHP predictions processor requires PHP 7.x to work because it is what php-ml library requires. We need to make this requirement clearer. We can not do it at plugin level because people can just use the python predictions processor or any other plugin they write, but we could show a warning message in the admin settings page if the server php version is lower than 7.0 and the PHP predictions processor is selected (it is the default value)
7.summary: Add support for social breadth level 2
description: I added a // TODO Add support for other levels than 1. in classes/local/indicator/activity_social_breadth.php because I didnt have time to code other social breadth levels. Level 2 should be pretty easy to add (just check any_write). From level 3 it starts depending on the activity, most of the stuff required to code from level 3 is available in the parent class community_of_inquiry_activity but we may require to add extra stuff to calculate them all.
8.summary: Replace get_activity_type indicators method for an automated solution
description: We could not automate it when indicators were part of tool_inspire, but we can do it now that they are in core as indicator classes namespace include the activity type.
9.summary: Move activities indicators under each activity directory
description: All indicators are in analytics/classes/local/indicator they should be move to the activity directory along with the indicator name. e.g. mod/assign/classes/analytics/indicator/
10.summary: Skip mlbackend_php tests if PHP < 7.0
description: mlbackend_php requires PHP 7.0, we should skip its tests if the PHP CLI version is lower than PHP 7.0
11.summary: Remove built-in models once tool_models is deleted.
description: Moodle built-in models are installed along with tool_models to separate analytics API and the prediction models that come with moodle, Im not 100 convinced this is a good idea but it sounds better to me than to mix analytics base classes with specific-models targets. If the tool is removed the 2 cron tasks that run training and predictions will not be used any more, but people can still use the API function that these tasks execute to run training and prediction. Conceptually this is what makes more sense to me and people removing tool_models does not make much sense to me either. Open to discussion, but as pointed out by ankit_frenz if we set built-in models targets in tool_models namespace we should uninstall them if the tool is uninstalled.
12.summary: Convert student enrolments analyser get samples methods to enrol API functions
description: We should avoid having direct DB queries to other subsystems db tables. We should instead use enrol API methods.
13.summary: Fix CiBoT complaints
description: There shouldnt be anything really worrying, there are missing php doc blocks and stuff like that
14.summary: Review unit test coverage
description: There are unit tests for the model and for training, prediction and evaluation processes, but there are some critical areas that are not covered by unit test and they should.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.7 upgrade
description: Moodle 3.7 is scheduled for release on Monday 13 May 2019.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.7
description:
2.summary: Upgrade learn.moodle.net to 3.7
description:
3.summary: Upgrade lang.moodle.org to 3.6.4
description:
4.summary: Upgrade school.demo.moodle.net to 3.7
description:
5.summary: Upgrade demo.moodle.net to 3.7
description:
6.summary: Upgrade download.moodle.org to 3.7
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.7 upgrade
description: Moodle 3.7 is scheduled for release on Monday 13 May 2019.
### Response:
1.summary: Upgrade moodle.org to 3.7
description:
2.summary: Upgrade learn.moodle.net to 3.7
description:
3.summary: Upgrade lang.moodle.org to 3.6.4
description:
4.summary: Upgrade school.demo.moodle.net to 3.7
description:
5.summary: Upgrade demo.moodle.net to 3.7
description:
6.summary: Upgrade download.moodle.org to 3.7
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle sites 3.0 upgrade
description: Moodle 3.0 scheduled release: Monday 9 November 2015
| Unsolvable | 1.summary: Upgrade moodle.org to 3.0
description:
2.summary: Upgrade learn.moodle.net to 3.0
description:
3.summary: Upgrade lang.moodle.org to 3.0
description:
4.summary: Upgrade school.demo.moodle.net to 3.0
description:
5.summary: Upgrade demo.moodle.net to 3.0
description:
6.summary: Upgrade dev.moodle.org to 3.0
description:
7.summary: Upgrade moodle.net to 3.0
description:
8.summary: Upgrade research.moodle.net to 3.0
description:
9.summary: Upgrade moodlemoot.org sites to 3.0
description:
10.summary: Upgrade download.moodle.org to 3.0
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle sites 3.0 upgrade
description: Moodle 3.0 scheduled release: Monday 9 November 2015
### Response:
1.summary: Upgrade moodle.org to 3.0
description:
2.summary: Upgrade learn.moodle.net to 3.0
description:
3.summary: Upgrade lang.moodle.org to 3.0
description:
4.summary: Upgrade school.demo.moodle.net to 3.0
description:
5.summary: Upgrade demo.moodle.net to 3.0
description:
6.summary: Upgrade dev.moodle.org to 3.0
description:
7.summary: Upgrade moodle.net to 3.0
description:
8.summary: Upgrade research.moodle.net to 3.0
description:
9.summary: Upgrade moodlemoot.org sites to 3.0
description:
10.summary: Upgrade download.moodle.org to 3.0
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Moodle Mobile 3.5.0
description: Collection of Moodle Mobile 3.5 required issues
| Unsolvable | 1.summary: Replace ionic icons with Moodle font icons
description: We need to replace the Ionic font icons with Moodle font icons
2.summary: Mobile app update to Ionic 3
description: Epic listing all the issues related to the apps update to Ionic 3
3.summary: Make "Post to forum" button sticky
description: Make "Post to forum" button sticky. it will help student post their replies or answers quickly.
4.summary: Support for Site Add-ons on local_mobile
description: We need to support the new site add-ons for 3.1 onwards
5.summary: Include new 1024 icon for iOS
description: As mentioned here:
6.summary: Disable "Offline", "Download courses" and "Download course"
description: In we are introducing a few settings to allow admins to disable the "Offline use", "Download course" and "Download all courses" options. The overall idea is to not show those options if those settings are selected. Please note that the admin can disable the "Download all courses" but not "Download course" so individual courses can be downloaded, and vice-versa.
7.summary: Support custom app Privacy Policy
description: In we are creating a new setting inside the "Mobile settings" to enable admins to point to an specific Privacy Policy for the app. We should use that policy if available, if not, fallback to the "Site policy" and if there isnt fallback to Moodle generic one (the one used right now)
8.summary: Download course option is confusing for already downloaded courses
description: According to displaying "Download course" when a course has been already downloaded its confusing for students. Since we know that the course was already downloaded we should display an alternative text
9.summary: Support new Moodle 3.5 course cards in the app
description: Support new Moodle 3.5 course cards in the app
10.summary: Scale properly Vimeo videos in the app
description: This is a follow-up of , we need to improve how videos are embedded supporting bootstrap responsive classes like responsive-video, embed-responsive, embed-responsive-16by9 etc.. Most of the problems are related to the changes we made to serve always Vimeo videos via an iframe in the Moodle site to support private videos.
11.summary: Release local_mobile for Moodle 3.5
description: We need a 3.5 version for sites upgrading
12.summary: Inform student what will happen with their choices
description: We need to support on the mobile app the following functionality
13.summary: Improve some styles and UX problems
description: Core tabs are usually hidden on small screens. To avoid that Sliding tabs should be implemented. ------------ and other add buttons to FAB. Improve course section selector: The course section selector is hard to see/understand. We should add typeGroups in tsconfig: -Main Menu: Notifications tab isnt shown in 3.1 sites (site home is).- RTE issues: Bullets/nums not seen. Resize not working right in Android (when I close the keyboard the RTE keeps being small, when the keyboard is open I cant see the RTE buttons). I tested it on wiki. Brush icon should be improved. When the RTE is empty, writing on it sometimes place the text outside of , so the text styles are different. When going back a strange effect happens. In login we have this "Display label and select in different lines". Also, the box is quite narrow when using a list of fixed sites. In CoreLocalNotificationsProvider.showNotificationPopover were just displaying a Toast with the message. This should be improved to display a notification similar to what we did in the previous app. In iOS 11, there was a padding at top in course contents. Credentials view: cannot navigate through fields in iOS using the virtual keyboard. Check scroll effects on iOS. Click to add a new site and enter the proto 3.3 URL. In the credentials screen, part of the box ends up being behind the header bar. iOS8: The courses in dashboard werent seen.
14.summary: Release Moodle Mobile 3.5.0
description: Tasks to be done every time we are going to release a new version:
15.summary: Display message for classic app when connecting to old Moodle sites
description: We should display a message redirecting the user to download Moodle Classic when connecting to old Moodle sites. We should display the same message for sites already stored in the app and avoid the user to use them (we can remove the token or something like that).
16.summary: Display message for new app when connecting to Moodle sites >= 3.1 (in the classic app)
description: Display message for new app when connecting to Moodle sites >= 3.1 (in the classic app)
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Moodle Mobile 3.5.0
description: Collection of Moodle Mobile 3.5 required issues
### Response:
1.summary: Replace ionic icons with Moodle font icons
description: We need to replace the Ionic font icons with Moodle font icons
2.summary: Mobile app update to Ionic 3
description: Epic listing all the issues related to the apps update to Ionic 3
3.summary: Make "Post to forum" button sticky
description: Make "Post to forum" button sticky. it will help student post their replies or answers quickly.
4.summary: Support for Site Add-ons on local_mobile
description: We need to support the new site add-ons for 3.1 onwards
5.summary: Include new 1024 icon for iOS
description: As mentioned here:
6.summary: Disable "Offline", "Download courses" and "Download course"
description: In we are introducing a few settings to allow admins to disable the "Offline use", "Download course" and "Download all courses" options. The overall idea is to not show those options if those settings are selected. Please note that the admin can disable the "Download all courses" but not "Download course" so individual courses can be downloaded, and vice-versa.
7.summary: Support custom app Privacy Policy
description: In we are creating a new setting inside the "Mobile settings" to enable admins to point to an specific Privacy Policy for the app. We should use that policy if available, if not, fallback to the "Site policy" and if there isnt fallback to Moodle generic one (the one used right now)
8.summary: Download course option is confusing for already downloaded courses
description: According to displaying "Download course" when a course has been already downloaded its confusing for students. Since we know that the course was already downloaded we should display an alternative text
9.summary: Support new Moodle 3.5 course cards in the app
description: Support new Moodle 3.5 course cards in the app
10.summary: Scale properly Vimeo videos in the app
description: This is a follow-up of , we need to improve how videos are embedded supporting bootstrap responsive classes like responsive-video, embed-responsive, embed-responsive-16by9 etc.. Most of the problems are related to the changes we made to serve always Vimeo videos via an iframe in the Moodle site to support private videos.
11.summary: Release local_mobile for Moodle 3.5
description: We need a 3.5 version for sites upgrading
12.summary: Inform student what will happen with their choices
description: We need to support on the mobile app the following functionality
13.summary: Improve some styles and UX problems
description: Core tabs are usually hidden on small screens. To avoid that Sliding tabs should be implemented. ------------ and other add buttons to FAB. Improve course section selector: The course section selector is hard to see/understand. We should add typeGroups in tsconfig: -Main Menu: Notifications tab isnt shown in 3.1 sites (site home is).- RTE issues: Bullets/nums not seen. Resize not working right in Android (when I close the keyboard the RTE keeps being small, when the keyboard is open I cant see the RTE buttons). I tested it on wiki. Brush icon should be improved. When the RTE is empty, writing on it sometimes place the text outside of , so the text styles are different. When going back a strange effect happens. In login we have this "Display label and select in different lines". Also, the box is quite narrow when using a list of fixed sites. In CoreLocalNotificationsProvider.showNotificationPopover were just displaying a Toast with the message. This should be improved to display a notification similar to what we did in the previous app. In iOS 11, there was a padding at top in course contents. Credentials view: cannot navigate through fields in iOS using the virtual keyboard. Check scroll effects on iOS. Click to add a new site and enter the proto 3.3 URL. In the credentials screen, part of the box ends up being behind the header bar. iOS8: The courses in dashboard werent seen.
14.summary: Release Moodle Mobile 3.5.0
description: Tasks to be done every time we are going to release a new version:
15.summary: Display message for classic app when connecting to old Moodle sites
description: We should display a message redirecting the user to download Moodle Classic when connecting to old Moodle sites. We should display the same message for sites already stored in the app and avoid the user to use them (we can remove the token or something like that).
16.summary: Display message for new app when connecting to Moodle sites >= 3.1 (in the classic app)
description: Display message for new app when connecting to Moodle sites >= 3.1 (in the classic app)
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Moodle community sites 3.6.2 upgrade
description: Moodle 3.6.2 is scheduled for release on Monday 14 January 2019.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.6.2
description:
2.summary: Upgrade learn.moodle.net to 3.6.2
description:
3.summary: Upgrade lang.moodle.org to 3.6.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.6.2
description:
5.summary: Upgrade demo.moodle.net to 3.6.2
description:
6.summary: Upgrade moodle.net to 3.6.2
description:
7.summary: Upgrade download.moodle.org to 3.6.2
description:
8.summary: Upgrade dev.moodle.org to 3.6.2
description:
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Moodle community sites 3.6.2 upgrade
description: Moodle 3.6.2 is scheduled for release on Monday 14 January 2019.
### Response:
1.summary: Upgrade moodle.org to 3.6.2
description:
2.summary: Upgrade learn.moodle.net to 3.6.2
description:
3.summary: Upgrade lang.moodle.org to 3.6.2
description:
4.summary: Upgrade school.demo.moodle.net to 3.6.2
description:
5.summary: Upgrade demo.moodle.net to 3.6.2
description:
6.summary: Upgrade moodle.net to 3.6.2
description:
7.summary: Upgrade download.moodle.org to 3.6.2
description:
8.summary: Upgrade dev.moodle.org to 3.6.2
description:
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Do educators want to use MoodleNet on their mobile devices?
description: Testers can access MoodleNet on a mobile device. The interface is smooth and responsive.
| Unsolvable | 1.summary: Automatically paste the clipboard URL
description: When creating a new resource, it would be very desirable to paste automatically the content of the clipboard if it is an URL so the user only has to click once to fetch metadata.
2.summary: Improve mobile web view
description: Improve and iterate the first release of the mobile web view.
3.summary: Test and adapt the MoodleNet UI for smaller screen sizes
description: (eg. mobile, tablet)
4.summary: Test MoodleNet on mobile
description: Use our devices and Browserstack account.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Do educators want to use MoodleNet on their mobile devices?
description: Testers can access MoodleNet on a mobile device. The interface is smooth and responsive.
### Response:
1.summary: Automatically paste the clipboard URL
description: When creating a new resource, it would be very desirable to paste automatically the content of the clipboard if it is an URL so the user only has to click once to fetch metadata.
2.summary: Improve mobile web view
description: Improve and iterate the first release of the mobile web view.
3.summary: Test and adapt the MoodleNet UI for smaller screen sizes
description: (eg. mobile, tablet)
4.summary: Test MoodleNet on mobile
description: Use our devices and Browserstack account.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Better Office Integrations Project - Moodle 3.3
description: Project page:
| Unsolvable | 1.summary: OAuth 2 authentication upgrades for Moodle.
description: 1. Improve the moodle oauth 2 library so it is compatible with several prominant OAuth APIs (Google, Microsoft, Facebook is a nice start). Some specific problems are use of multi-part form encoding for token requests and duplicating Authentication headers on every request. 2. Provide a central administration page for configuring OAuth services in a generic way (including support for service discovery with OpenID Connect) 3. Allow system wide configuration of an OAuth service account which retrieves a "refresh token" for an OAuth API - allowing the system to retrieve access tokens and use the service account as part of an API. 4. Allow incremental authorization by remembering the approved scopes and requesting re-authentication when the un un-authorized scope is requested. 5. Implement a new auth plugin that displayes the installed OAuth services in a list on the login page and will login and update the user details via OAuth.
2.summary: Update googledocs repository to use \core\oaut\client
description: Use a single setting which is which OAuth 2 issuer to use for authentication. This is merged with the googledocs repo - I think this makes sense (no point having 2). The googledocs repo used an older version of the google client libraries that is now difficult to upgrade because of composer. I replaced it with straight rest calls using the updated OAuth client.
3.summary: Implement core office365 repository that uses \core\oaut\client
description: The existing skydrive repository and third party office 365 repositories can be used as a reference.
4.summary: Update googledocs repository to support references
description: The google docs repository currently only supports internal files - to support references it should get the "sharing" link to the file from the API and store that.
5.summary: Update new office365 repository to support external files and references
description: Get a sharing link to the file and store that as the source.
6.summary: Add a new feature for repositories to generate an "edit" link to an external file / resource.
description: If a file has an "edit" link and the current moodle user can edit the file - show an Edit link in the UI wherever the file is listed.
7.summary: Add upload support to googledocs and office365 repositories
description: Allow uploading files direct to the repository.
8.summary: Add optional feature to repositories to make a copy of an external file / reference owned by Moodle
description: This creates a new file that is owned by the system account. Implement this for google docs and office365.
9.summary: Use new repository feature to transfer file from student as part of assignment workflow.
description: In the feedback files assignment plugin - when a student cannot edit their submission any longer, transfer the owner ship of the file to the system account and let teachers edit it. (If the repository supports this feature).
10.summary: Add admin settings to googledrive and office365 repositories to control the default type of file, and the available types
description: E.g. FILE_INTERNAL, FILE_EXTERNAL, FILE_REFERENCE
11.summary: Do something with the skydrive repo.
description: Do we keep it? Move the code from the new o365 repo into it?
12.summary: Auto subscribe google calendars to the moodle calendar RSS.
description: Not sure where this code should go yet.
13.summary: Auto subscribe the Outlook calendar to the moodle calendar.
description: Not sure where this code goes yet.
14.summary: Add upgrade step to googledrive to create a google service from the stored credentials
description: Existing working setups should keep working.
15.summary: Allow connecting a Moodle account with (many) OAuth accounts
description: When logging in via OAuth we can search for a moodle account connected to the current OAuth account and login as that user. Provide a "Connected Logins" page for users to connect/disconnect any of their OAuth logins.
16.summary: Final clean up of googledocs set of tasks and send to integration
description: This is an issue to collect together the full set of issues to improve the google docs repo + add authentication providers on the login page. There will be a separate issue for the office365/skydrive repo.
17.summary: Implement Better office integrations project
description: This is a separate issue to review / integrate the set of changes for the skydrive repo + final improvements.
18.summary: Add a new type of file converter to core - which uses Google drive apis to convert files online.
description: Since we now have a nice OAuth api to google, and a new plugin type for document conversions - lets ship a google file converter as an alternative to unoconv (which people have struggled to setup).
19.summary: Add a new param to the file serving script to get the offline version of a controlled link
description: The new param will be offline=true and will download or export and download the file from the repository and return it.
20.summary: OAuth 2 - Confirm emails before auto-linking or creating new accounts.
description: E.g. I have a Moodle account with the email set to damyon.wiese I use google login to login to the matching gmail account and I have access to Moodle (without manually connecting the accounts in my preferences). The DANGER - can I make up an account at one of the OAuth providers and login with that account before verifying that I am the owner of the email address? This would allow me to login to Moodle as ANYONE...
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Better Office Integrations Project - Moodle 3.3
description: Project page:
### Response:
1.summary: OAuth 2 authentication upgrades for Moodle.
description: 1. Improve the moodle oauth 2 library so it is compatible with several prominant OAuth APIs (Google, Microsoft, Facebook is a nice start). Some specific problems are use of multi-part form encoding for token requests and duplicating Authentication headers on every request. 2. Provide a central administration page for configuring OAuth services in a generic way (including support for service discovery with OpenID Connect) 3. Allow system wide configuration of an OAuth service account which retrieves a "refresh token" for an OAuth API - allowing the system to retrieve access tokens and use the service account as part of an API. 4. Allow incremental authorization by remembering the approved scopes and requesting re-authentication when the un un-authorized scope is requested. 5. Implement a new auth plugin that displayes the installed OAuth services in a list on the login page and will login and update the user details via OAuth.
2.summary: Update googledocs repository to use \core\oaut\client
description: Use a single setting which is which OAuth 2 issuer to use for authentication. This is merged with the googledocs repo - I think this makes sense (no point having 2). The googledocs repo used an older version of the google client libraries that is now difficult to upgrade because of composer. I replaced it with straight rest calls using the updated OAuth client.
3.summary: Implement core office365 repository that uses \core\oaut\client
description: The existing skydrive repository and third party office 365 repositories can be used as a reference.
4.summary: Update googledocs repository to support references
description: The google docs repository currently only supports internal files - to support references it should get the "sharing" link to the file from the API and store that.
5.summary: Update new office365 repository to support external files and references
description: Get a sharing link to the file and store that as the source.
6.summary: Add a new feature for repositories to generate an "edit" link to an external file / resource.
description: If a file has an "edit" link and the current moodle user can edit the file - show an Edit link in the UI wherever the file is listed.
7.summary: Add upload support to googledocs and office365 repositories
description: Allow uploading files direct to the repository.
8.summary: Add optional feature to repositories to make a copy of an external file / reference owned by Moodle
description: This creates a new file that is owned by the system account. Implement this for google docs and office365.
9.summary: Use new repository feature to transfer file from student as part of assignment workflow.
description: In the feedback files assignment plugin - when a student cannot edit their submission any longer, transfer the owner ship of the file to the system account and let teachers edit it. (If the repository supports this feature).
10.summary: Add admin settings to googledrive and office365 repositories to control the default type of file, and the available types
description: E.g. FILE_INTERNAL, FILE_EXTERNAL, FILE_REFERENCE
11.summary: Do something with the skydrive repo.
description: Do we keep it? Move the code from the new o365 repo into it?
12.summary: Auto subscribe google calendars to the moodle calendar RSS.
description: Not sure where this code should go yet.
13.summary: Auto subscribe the Outlook calendar to the moodle calendar.
description: Not sure where this code goes yet.
14.summary: Add upgrade step to googledrive to create a google service from the stored credentials
description: Existing working setups should keep working.
15.summary: Allow connecting a Moodle account with (many) OAuth accounts
description: When logging in via OAuth we can search for a moodle account connected to the current OAuth account and login as that user. Provide a "Connected Logins" page for users to connect/disconnect any of their OAuth logins.
16.summary: Final clean up of googledocs set of tasks and send to integration
description: This is an issue to collect together the full set of issues to improve the google docs repo + add authentication providers on the login page. There will be a separate issue for the office365/skydrive repo.
17.summary: Implement Better office integrations project
description: This is a separate issue to review / integrate the set of changes for the skydrive repo + final improvements.
18.summary: Add a new type of file converter to core - which uses Google drive apis to convert files online.
description: Since we now have a nice OAuth api to google, and a new plugin type for document conversions - lets ship a google file converter as an alternative to unoconv (which people have struggled to setup).
19.summary: Add a new param to the file serving script to get the offline version of a controlled link
description: The new param will be offline=true and will download or export and download the file from the repository and return it.
20.summary: OAuth 2 - Confirm emails before auto-linking or creating new accounts.
description: E.g. I have a Moodle account with the email set to damyon.wiese I use google login to login to the matching gmail account and I have access to Moodle (without manually connecting the accounts in my preferences). The DANGER - can I make up an account at one of the OAuth providers and login with that account before verifying that I am the owner of the email address? This would allow me to login to Moodle as ANYONE...
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle Community Sites
summary: Registration improvements
description:
| Solvable | 1.summary: Review of Moodle.net registration/stats etc
description: In dougiamas wrote: quote do a code review on the entire path from registration, email subscription on sendy linkchecking, and stats generation to make sure all the code logic is understandable and looks ok. quote
2.summary: Registration page should state if site is registered
description: Currently the registration page looks almost identical whether your site is registered or not. You have to be very observant and scroll to the bottom of the page to check whether the button says Register with moodle.org or Update registration on Moodle.org. Also, if you have registered, there is no indication of when you did so, and no prompt to update your registration. It would be good if the registration page could be made more user-friendly, perhaps with a message at the top of the page, for example Please register your site with Moodle.org OR Thanks for registering your site with Moodle.org (just after doing so) OR This site was previously registered with Moodle.org on ..... Please help improve our statistics by updating your registration. (with an update registration button)
3.summary: Improve messages displayed in the registration process
description: Registering your site should be appear inviting and straightforward. This issue follows up improvements made in .
4.summary: Improve the site registration scheduled task
description: A scheduled task exists in lib/classes/task/registration_cron_task.php. The code that actually does the work is in /admin/registration/lib.php cron(). Its output if run on an unregistered site doesnt mention not being registered and probably should. quote Execute scheduled task: Site registration ... started 07:25:20. Current memory use 24.1MB. ... used 4 dbqueries ... used 0.060204029083252 seconds Scheduled task complete: Site registration quote The scheduled task, having run, is now set to run again tomorrow. Within the task there is code that silently does nothing if the task has been run within the last seven days. Imposing a hard limit on how often registration is updated seems fine but it would be nice if the scheduled task didnt pretend like it was updating the registration every day. Also, can the registration page determine if the scheduled task is enabled and output something to the UI? We dont need to tell users to manually update their registration if it will happen automatically. Also, if Moodle is "phoning home" we want to be very explicit about that.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle Community Sites
summary: Registration improvements
description:
### Response:
1.summary: Review of Moodle.net registration/stats etc
description: In dougiamas wrote: quote do a code review on the entire path from registration, email subscription on sendy linkchecking, and stats generation to make sure all the code logic is understandable and looks ok. quote
2.summary: Registration page should state if site is registered
description: Currently the registration page looks almost identical whether your site is registered or not. You have to be very observant and scroll to the bottom of the page to check whether the button says Register with moodle.org or Update registration on Moodle.org. Also, if you have registered, there is no indication of when you did so, and no prompt to update your registration. It would be good if the registration page could be made more user-friendly, perhaps with a message at the top of the page, for example Please register your site with Moodle.org OR Thanks for registering your site with Moodle.org (just after doing so) OR This site was previously registered with Moodle.org on ..... Please help improve our statistics by updating your registration. (with an update registration button)
3.summary: Improve messages displayed in the registration process
description: Registering your site should be appear inviting and straightforward. This issue follows up improvements made in .
4.summary: Improve the site registration scheduled task
description: A scheduled task exists in lib/classes/task/registration_cron_task.php. The code that actually does the work is in /admin/registration/lib.php cron(). Its output if run on an unregistered site doesnt mention not being registered and probably should. quote Execute scheduled task: Site registration ... started 07:25:20. Current memory use 24.1MB. ... used 4 dbqueries ... used 0.060204029083252 seconds Scheduled task complete: Site registration quote The scheduled task, having run, is now set to run again tomorrow. Within the task there is code that silently does nothing if the task has been run within the last seven days. Imposing a hard limit on how often registration is updated seems fine but it would be nice if the scheduled task didnt pretend like it was updating the registration every day. Also, can the registration page determine if the scheduled task is enabled and output something to the UI? We dont need to tell users to manually update their registration if it will happen automatically. Also, if Moodle is "phoning home" we want to be very explicit about that.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: A collection of user stories to work on after weve launched MoodleNet.
description: A collection of user stories to work on after weve launched MoodleNet.
| Unsolvable | 1.summary: Refer users to other Moodle services
description: We need to scope out how users are referred to other Moodle services, including those provided by Moodle Partners:
2.summary: Add an already-created resource to another collection
description: See discussion at
3.summary: Research models for payment/support
description: MoodleNet needs to find a way to be sustainable. Theres many options for this, including allowing users to directly support its development. Heres a couple of starting points for research: Discord: Aether: (interestingly, Discord upgraded its Nitro offering( to included free content (i.e. games) - and also increased the price from $4.99 to $9.99 per month)
4.summary: Look into APIs for OER & commons repositories
description: x Look into Creative Commons API x Contact OER Commons about API licensing( (and potentially also sharing Moodle content to their platform as a "Featured Content Provider")
5.summary: Start planning post-beta roadmap
description: Its time to start thinking beyond shipping a federated social network, and think about features that the community will want in 2020.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: A collection of user stories to work on after weve launched MoodleNet.
description: A collection of user stories to work on after weve launched MoodleNet.
### Response:
1.summary: Refer users to other Moodle services
description: We need to scope out how users are referred to other Moodle services, including those provided by Moodle Partners:
2.summary: Add an already-created resource to another collection
description: See discussion at
3.summary: Research models for payment/support
description: MoodleNet needs to find a way to be sustainable. Theres many options for this, including allowing users to directly support its development. Heres a couple of starting points for research: Discord: Aether: (interestingly, Discord upgraded its Nitro offering( to included free content (i.e. games) - and also increased the price from $4.99 to $9.99 per month)
4.summary: Look into APIs for OER & commons repositories
description: x Look into Creative Commons API x Contact OER Commons about API licensing( (and potentially also sharing Moodle content to their platform as a "Featured Content Provider")
5.summary: Start planning post-beta roadmap
description: Its time to start thinking beyond shipping a federated social network, and think about features that the community will want in 2020.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Add workshop module support on Mobile app
description: Add workshop support on the Mobile app using the WS created on
| Unsolvable | 1.summary: Support main info of workshop activity
description: Support the main page of workshop activity. This issue includes: Availability. Links to activity sections. In this case, phases. Basic prefetch.
2.summary: Support setup phase on Workshop activity
description: Support first phase of the activity. Provide information about the different phases and its actions. Add instructions of the setup phase
3.summary: Support submission phase on Workshop
description: Support submission phase on workshop activity. As an student add form and actions to add and edit submissions. As a teacher add a way to review all students submissions and delete them. Add offline and sync functions.
4.summary: Support assessment phase on Workshop
description: Add support for assessment phase on workshop. Add a way to review all submissions that the user has to assess. Add proper actions on the review page and provide the assessment form. Add offline and sync actions.
5.summary: Support grading evaluation phase on Workshop
description: Add support for grading evaluation phase. Add a review page for the submission and the given assessments Add a form to provide final grade and feedback information. Add offline and sync actions.
6.summary: Support closing phase on Workshop
description: Add all related information and actions to close a workshop. Review all workshop as one.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Add workshop module support on Mobile app
description: Add workshop support on the Mobile app using the WS created on
### Response:
1.summary: Support main info of workshop activity
description: Support the main page of workshop activity. This issue includes: Availability. Links to activity sections. In this case, phases. Basic prefetch.
2.summary: Support setup phase on Workshop activity
description: Support first phase of the activity. Provide information about the different phases and its actions. Add instructions of the setup phase
3.summary: Support submission phase on Workshop
description: Support submission phase on workshop activity. As an student add form and actions to add and edit submissions. As a teacher add a way to review all students submissions and delete them. Add offline and sync functions.
4.summary: Support assessment phase on Workshop
description: Add support for assessment phase on workshop. Add a way to review all submissions that the user has to assess. Add proper actions on the review page and provide the assessment form. Add offline and sync actions.
5.summary: Support grading evaluation phase on Workshop
description: Add support for grading evaluation phase. Add a review page for the submission and the given assessments Add a form to provide final grade and feedback information. Add offline and sync actions.
6.summary: Support closing phase on Workshop
description: Add all related information and actions to close a workshop. Review all workshop as one.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Review third party libraries for new versions (3.3)
description: There are a number of third-party libraries distributed with Moodle. Before the major release, the available versions of these libraries should be reviewed. Check the list at which should be up to date with lib/thirdpartylibs.xml and other thirdpartylibs.xml files distributed around Moodle. Add any newly incorporated libraries into the list Check the available versions of each library If there is a significant new version and updating is recommended, the new version should be integrated by creating a sub-task to this issue and processing it through integration independently. If there is a readme_moodle.txt file with the plugin, this describes the customisations made for Moodle. Check when doing your review. Libraries review here:
| Unsolvable | 1.summary: User Tours: paragraph text in user tour steps inherit all style attributes from CSS selector
description: When building or importing a User Tour in Moodle 3.2 (.../admin/tool/...) steps connected with CSS selectors inherit all the style attributes of the CSS selector. E.g.: a step in add=assign tour imported from Moodle.net connected with any of the headers in this page will format all text in the step box as a header; any step connected to a CSS selector with font color: white will be unreadable as the text is displayed in white against a white background. Ive tested this in both a custom theme and in Clean, with the same results. An example of this issue can be replicated using the downloadable json-file from Moodle.net:
2.summary: Upgrade PHPMailer to 5.2.23
description: In we fixed the recently reported security issues in phpmailer by validating before sending to phpmailer. This issue is to upgrade the library, following that mitigation of the security issue
3.summary: Upgrade Google API library to 2.1.1 for Moodle 3.3 release (do last)
description: Before starting work on the google drive repository, we should make sure we are using the latest version.
4.summary: Upgrade Video.JS to 5.18.4
description: Upgrade Video.JS to 5.18.4 also youtube extension
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Review third party libraries for new versions (3.3)
description: There are a number of third-party libraries distributed with Moodle. Before the major release, the available versions of these libraries should be reviewed. Check the list at which should be up to date with lib/thirdpartylibs.xml and other thirdpartylibs.xml files distributed around Moodle. Add any newly incorporated libraries into the list Check the available versions of each library If there is a significant new version and updating is recommended, the new version should be integrated by creating a sub-task to this issue and processing it through integration independently. If there is a readme_moodle.txt file with the plugin, this describes the customisations made for Moodle. Check when doing your review. Libraries review here:
### Response:
1.summary: User Tours: paragraph text in user tour steps inherit all style attributes from CSS selector
description: When building or importing a User Tour in Moodle 3.2 (.../admin/tool/...) steps connected with CSS selectors inherit all the style attributes of the CSS selector. E.g.: a step in add=assign tour imported from Moodle.net connected with any of the headers in this page will format all text in the step box as a header; any step connected to a CSS selector with font color: white will be unreadable as the text is displayed in white against a white background. Ive tested this in both a custom theme and in Clean, with the same results. An example of this issue can be replicated using the downloadable json-file from Moodle.net:
2.summary: Upgrade PHPMailer to 5.2.23
description: In we fixed the recently reported security issues in phpmailer by validating before sending to phpmailer. This issue is to upgrade the library, following that mitigation of the security issue
3.summary: Upgrade Google API library to 2.1.1 for Moodle 3.3 release (do last)
description: Before starting work on the google drive repository, we should make sure we are using the latest version.
4.summary: Upgrade Video.JS to 5.18.4
description: Upgrade Video.JS to 5.18.4 also youtube extension
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: MoodleNet
summary: Documentation for MoodleNet 3.0.0
description: User Documentation for MoodleNet 3.0.0
| Solvable | 1.summary: Create or link to a documentation page for tracker
description: Update documentation to inform people how to report bugs, request features.
2.summary: architecture and dev guidelines docs
description: create documentation for: overview of backend and frontend architecture for each system logical layer dev patterns dev guidelines
3.summary: Image upload advice
description: _When I upload a picture I have no idea which size or aspect/ratio you prefer. I neither have the option to arrange my uploaded image for optimal presentation._
4.summary: Add Visual Roadmap
description: Some users are reporting no access to the roadmap in our tracker. We should add a visual one to our documentation.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: MoodleNet
summary: Documentation for MoodleNet 3.0.0
description: User Documentation for MoodleNet 3.0.0
### Response:
1.summary: Create or link to a documentation page for tracker
description: Update documentation to inform people how to report bugs, request features.
2.summary: architecture and dev guidelines docs
description: create documentation for: overview of backend and frontend architecture for each system logical layer dev patterns dev guidelines
3.summary: Image upload advice
description: _When I upload a picture I have no idea which size or aspect/ratio you prefer. I neither have the option to arrange my uploaded image for optimal presentation._
4.summary: Add Visual Roadmap
description: Some users are reporting no access to the roadmap in our tracker. We should add a visual one to our documentation.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: An AI assistant for Moodle
description: An AI assistant could bring multiple benefits for Moodle users. We want users to interact with Moodle through user friendly interfaces. An AI assistant could be a new user interface that would grant quick access to the most popular user stories different stakeholders have in Moodle. We want Moodle to actively nudge users about different aspects of their interest. We currently use the notifications system in Moodle to display insights from the analytics API. An assistant could better channel these insights to the user. An AI assistant could monitor the user session and actively help or encourage the user when necessary. There are some examples of this in this proof of concept: An AI assistant should understand users input in natural language (NLU) and could respond to them, forwarding them to external documentation pages or asking further questions about their intent. There is a proof-of-concept of Moodle connecting to a NLU backend in The responsibility of the NLU backend in this POC is to identify the user intent and/or to reply to user questions. As an open source learning platform whatever solution we design should be highly customisable and extendable so we should abstract parts of the AI assistant API so we allow users to use different NLU backends and we allow moodle components (including 3rd party plugins) to hook into the assistant. Some sources of information about how an AI assistants (or chatbots) can help users in an LMS: (I havent been able to locate the list of intents yet) The first thing we should do is to identify how an AI assistant adds extra value for Moodle users. All ideas are welcomed.
| Solvable | 1.summary: Training data format
description: We want the AI assistant in Moodle to communicate with natural language understanding (NLU) backends so they can identify what the user wants to do; well, what is the most likely thing they want to do given that input. We need training data for each intent and we need to define the format of this training data file so that: The format is human-readable so it can be easily translated to different languages by translators (we will need to check with Moodle translators that the suggested format is ok for them) The format is easily convertible to the format NLU backends expect. We dont want to tie all Moodle users in the world to 1 NLU solution so we need a new nlu plugin type. I havent found any standard format for training data. is the closest thing Ive found so far. It is not likely that we will find a format that works across all the NLU backends if there is no standard format so the least we should do is to ensure that the format we use can be easily converted to the format used by the most popular NLU backends (e.g. Dialogflow, Luis, Rasa, Snips, Lex, Watson...). The nlu API in moodle can then allow plugins to reformat the training data in the format expected by that specific NLU backend.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: An AI assistant for Moodle
description: An AI assistant could bring multiple benefits for Moodle users. We want users to interact with Moodle through user friendly interfaces. An AI assistant could be a new user interface that would grant quick access to the most popular user stories different stakeholders have in Moodle. We want Moodle to actively nudge users about different aspects of their interest. We currently use the notifications system in Moodle to display insights from the analytics API. An assistant could better channel these insights to the user. An AI assistant could monitor the user session and actively help or encourage the user when necessary. There are some examples of this in this proof of concept: An AI assistant should understand users input in natural language (NLU) and could respond to them, forwarding them to external documentation pages or asking further questions about their intent. There is a proof-of-concept of Moodle connecting to a NLU backend in The responsibility of the NLU backend in this POC is to identify the user intent and/or to reply to user questions. As an open source learning platform whatever solution we design should be highly customisable and extendable so we should abstract parts of the AI assistant API so we allow users to use different NLU backends and we allow moodle components (including 3rd party plugins) to hook into the assistant. Some sources of information about how an AI assistants (or chatbots) can help users in an LMS: (I havent been able to locate the list of intents yet) The first thing we should do is to identify how an AI assistant adds extra value for Moodle users. All ideas are welcomed.
### Response:
1.summary: Training data format
description: We want the AI assistant in Moodle to communicate with natural language understanding (NLU) backends so they can identify what the user wants to do; well, what is the most likely thing they want to do given that input. We need training data for each intent and we need to define the format of this training data file so that: The format is human-readable so it can be easily translated to different languages by translators (we will need to check with Moodle translators that the suggested format is ok for them) The format is easily convertible to the format NLU backends expect. We dont want to tie all Moodle users in the world to 1 NLU solution so we need a new nlu plugin type. I havent found any standard format for training data. is the closest thing Ive found so far. It is not likely that we will find a format that works across all the NLU backends if there is no standard format so the least we should do is to ensure that the format we use can be easily converted to the format used by the most popular NLU backends (e.g. Dialogflow, Luis, Rasa, Snips, Lex, Watson...). The nlu API in moodle can then allow plugins to reformat the training data in the format expected by that specific NLU backend.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Implement the JS Framework specification
description: All the tasks required to spec, prototype, discuss, agree and implement
| Unsolvable | 1.summary: Update prototype grunt support to support transpiling from ES6 modules
description: Following on from , we want to see if it is worth writing our new modules in ES6 and converting them to AMD as a build step. This would let us remove the dependency on requirejs eventually without having to re-factor all our javascript modules.
2.summary: Update prototype grunt support for requirejs
description: Create a fork of that supports grunt for minification. We want grunt to create minified versions of js modules in /js/amd/ folders and move them to /js/build folders, then serve all files from the build area. Ideally we will have minified, + source maps and originals in the build area. Also we want to auto-generate a default file for each component containing all modules from the component (Using r.js).
3.summary: Summarise the discussion
description: Write up a clear summary of the discussion on in the specification document
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Implement the JS Framework specification
description: All the tasks required to spec, prototype, discuss, agree and implement
### Response:
1.summary: Update prototype grunt support to support transpiling from ES6 modules
description: Following on from , we want to see if it is worth writing our new modules in ES6 and converting them to AMD as a build step. This would let us remove the dependency on requirejs eventually without having to re-factor all our javascript modules.
2.summary: Update prototype grunt support for requirejs
description: Create a fork of that supports grunt for minification. We want grunt to create minified versions of js modules in /js/amd/ folders and move them to /js/build folders, then serve all files from the build area. Ideally we will have minified, + source maps and originals in the build area. Also we want to auto-generate a default file for each component containing all modules from the component (Using r.js).
3.summary: Summarise the discussion
description: Write up a clear summary of the discussion on in the specification document
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Changes to forms discussed a the Form simplification working group at MootIEUK15
description: This epic will contain a number of suggested improvements to forms to simplify them for first-time users. Ideas from the working group are recorded in the following doc. This will need to be transferred to a Dev Docs spec.
| Unsolvable | 1.summary: maximise/minimise button to hide the lateral blocks/dock
description: It will be nice to have a maximise/minimise button to hide all blocks on page to get more viewable area. leblangi is using similar concept on his site see here (at the left of lang menu)|
2.summary: Trigger form submit using CTRL+Enter
description: A lot of Web forms (like the ones here in Tracker) allow you to submit a form, even when the submit button is not focussed, by pressing CTRL+Enter. When you are editing a text input field, pressing Enter will normally submit a form, whereas when you are editing some fields, like text areas or the HTML Editor, pressing Enter generates a new line. So the CTRL+Enter hotkey allows easier form submission from anywhere in the form. I havent thought through all the consequences of this (potential conflicts, for example). Im not sure what the equivalent Mac combination is (Command+Enter perhaps).
3.summary: Quiz password should not be an advanced setting by default
description: At the moment, the "Extra restrictions on attempts" is empty by default, which is not good.
4.summary: Improve the overall feedback section of the quiz form
description: At the moment, when you create a new quiz, there are 5 overall feedback boxes, and when you edit an existing quiz, you get either (current number of feedback 1.5) or 5 boxes, whichever is more. (E.g. if the quiz had 5 feedbacks, then you get 7 boxes on the edit form. If it had 10, you get 15 boxes.) This is not ideal. It takes up a lot of space on the form. Our experience of the question type forms (e.g. answers and hints) is that once the quiz is created, the best thing is to have a number of form fields that matches the number of repeat items that actually exist, since adding more is a rare action, and so it is not a problem to click the "Space for 3 more ..." in that case. (We probably always need to show one box, to avoid errors.) For new quizzes, we should pick a sensible number of boxes. The only data I have ready access to is the OU, and the data there shows: || number of feedbacks || number of quizzes || | 0 | 6088 | | 1 | 112 | | 2 | 17 | | 3 | 302 | | 4 | 335 | | 5 | 135 | | 6 | 6 | | 8 | 96 | From that, it looks like starting the form with 5 boxes would be right. (Before seeing the data, my guess was 2 empty boxes for a new quiz.)
5.summary: Course format change should use AJAX
description: In course settings, when a user changes the course format the page reloads and dislocates the user from the settings they were working on. An improvement to return the user course format section after reloading is suggested in , but this still includes a page reload. Using AJAX to display course format options as they change would be preferable.
6.summary: Simplifications of the Course creation/editing form
description: The course editing form contains a number of options that are prominent, but not essential. The working group suggests the following simplifications. . Form section names General Essential or Name Description Course details Guest access Access . First section changes Move Course category Course details Move Course start date Course details Move Visible Appearance Move Course start date Access Move Course ID number Course details Add a set of save buttons at the end of the first section.
7.summary: Improve saving options when adding a course
description: When creating a new course, on saving the course creation/editing form, the user is automatically directed to the enrolment page. This is not always desirable. Instead, when a user is about to save new course, they should be presented with three options: Save and return (to category management) Save and add users (default) Save and go to course Cancel The behaviour when editing an existing course should remain the same (returning the user to the course page after saving).
8.summary: Allow admins to control which course settings are available to users
description: Admins should be able to enable, lock or hide all/most course settings. This should be done from Course settings page in Moodle Site administration.
9.summary: Automatically copy full course name to short name as it is being added
description: When creating a new course, in many cases, the course short name and full name are the same. While this is not true in most cases, assisting the user to fill in this form will simplify the (often repetitive) process of creating courses. If the short name field is empty or if it is already identical to the full name, changes to the full name should be mirrored in the short name. When the short name field contains content that is different to the full name, it should be left alone.
10.summary: Add Undo button to Enrol users dialogue box
description: When a user enrols people in course, there is a dialogue box with an Enrol button next to each persons name. If a user accidentally clicks this button and enrols the wrong person, there is no quick way how to correct that. An improvement would be to add an Undo button next to newly enrolled person.
11.summary: There should be a button for user unenrollment instead of icon
description: In user enrollment page there should be a button for user unenrollment instead of icon. Currently it is an icon and is non-obvious. It should also be on seperate collumn, so it os divided from enrollment information
12.summary: Simplifications to Enrolled users page
description: The following changes are suggested for simplifying Enrolled users page. Move the "Proceed to course content" button to top and make the highlighted default button. Currently this button is only shown after a new course is created, but it should be shown all the time. Perhaps the label on the button could become "Return to course content" if changing enrolments under normal circumstances (ie not immediately after course creation). Collapse filter section and allow it to be expanded. The Filter button should not be a highlighted default button. The button to Proceed to course content is the logical next step, so should be highlighted. An Actions column should be created to the right of the enrolled users table. The delete and edit buttons should be moved to this column. Tooltips should be added to these buttons. The Roles column is unnecessarily wide. Column widths should be dynamic to allow narrow columns to expand. The date of enrolment is wrong when manual enrolments are used. It shows midnight of at the beginning of the date of enrolment instead of the correct enrolment time.
13.summary: Add link to non-AJAX enrolment page for bulk actions
description: The Enrolled users page relies on an AJAX dialogue to add new users. This is suitable for small classes where users are added individually. When JavaScript is disabled, the page reverts to the former Enrolled users page that uses side-by-side multi-select inputs to add and remove users from the list of enrolled users. This page is slightly more suitable for bulk actions. A link should be made form the new Enrolled users page to the old for admins/teachers who wish to add enrolments faster.
14.summary: Simplifcations to new user / edit profile form
description: There are a number of simplifications that can be made to the New user / Edit profile form. . Sections Make a new section called Location Make a new section called Actions . Moving Move Name fields to the top, above the user name Move authentication method and other actions (suspend and password) to the Actions section Move country, city and timezone to Location section Reduce the size of the description
15.summary: Allow admins to hide uncessary elements on New user / Edit profile form
description: A number of fields on the New user / Edit profile form are not relevant in many cases. Admins should have the potential to hide these options to simplify this form. country city timezone ID number institution department
16.summary: Quiz question bank pop-up: Add to quiz button should be disabled until a question is selected
description: Would be a small usability win.
17.summary: Move user profile email control field to their user preferences.
description: On each users profile, there is an option to change their preference for exposing their email address. There is an argument that this is a preference, rather than a profile field, and should instead appear in the users preferences.
18.summary: Keep the state of form sections between views of the same form
description: Currently users are presented with a minimal view of forms by containing and hiding optional settings in closed sections until the user expands a section. For a novice user this is appropriate as it avoids overwhelming the user. For more experienced users, however, it means that, to access optional settings, they have to expand each section that contains the settings they want. It is possible to expand all sections, but that creates a very long page. It would be helpful if the form remembered the state of expanded sections and restored this when the user returned to the form later. Its arguable whether this should persist between sessions.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Changes to forms discussed a the Form simplification working group at MootIEUK15
description: This epic will contain a number of suggested improvements to forms to simplify them for first-time users. Ideas from the working group are recorded in the following doc. This will need to be transferred to a Dev Docs spec.
### Response:
1.summary: maximise/minimise button to hide the lateral blocks/dock
description: It will be nice to have a maximise/minimise button to hide all blocks on page to get more viewable area. leblangi is using similar concept on his site see here (at the left of lang menu)|
2.summary: Trigger form submit using CTRL+Enter
description: A lot of Web forms (like the ones here in Tracker) allow you to submit a form, even when the submit button is not focussed, by pressing CTRL+Enter. When you are editing a text input field, pressing Enter will normally submit a form, whereas when you are editing some fields, like text areas or the HTML Editor, pressing Enter generates a new line. So the CTRL+Enter hotkey allows easier form submission from anywhere in the form. I havent thought through all the consequences of this (potential conflicts, for example). Im not sure what the equivalent Mac combination is (Command+Enter perhaps).
3.summary: Quiz password should not be an advanced setting by default
description: At the moment, the "Extra restrictions on attempts" is empty by default, which is not good.
4.summary: Improve the overall feedback section of the quiz form
description: At the moment, when you create a new quiz, there are 5 overall feedback boxes, and when you edit an existing quiz, you get either (current number of feedback 1.5) or 5 boxes, whichever is more. (E.g. if the quiz had 5 feedbacks, then you get 7 boxes on the edit form. If it had 10, you get 15 boxes.) This is not ideal. It takes up a lot of space on the form. Our experience of the question type forms (e.g. answers and hints) is that once the quiz is created, the best thing is to have a number of form fields that matches the number of repeat items that actually exist, since adding more is a rare action, and so it is not a problem to click the "Space for 3 more ..." in that case. (We probably always need to show one box, to avoid errors.) For new quizzes, we should pick a sensible number of boxes. The only data I have ready access to is the OU, and the data there shows: || number of feedbacks || number of quizzes || | 0 | 6088 | | 1 | 112 | | 2 | 17 | | 3 | 302 | | 4 | 335 | | 5 | 135 | | 6 | 6 | | 8 | 96 | From that, it looks like starting the form with 5 boxes would be right. (Before seeing the data, my guess was 2 empty boxes for a new quiz.)
5.summary: Course format change should use AJAX
description: In course settings, when a user changes the course format the page reloads and dislocates the user from the settings they were working on. An improvement to return the user course format section after reloading is suggested in , but this still includes a page reload. Using AJAX to display course format options as they change would be preferable.
6.summary: Simplifications of the Course creation/editing form
description: The course editing form contains a number of options that are prominent, but not essential. The working group suggests the following simplifications. . Form section names General Essential or Name Description Course details Guest access Access . First section changes Move Course category Course details Move Course start date Course details Move Visible Appearance Move Course start date Access Move Course ID number Course details Add a set of save buttons at the end of the first section.
7.summary: Improve saving options when adding a course
description: When creating a new course, on saving the course creation/editing form, the user is automatically directed to the enrolment page. This is not always desirable. Instead, when a user is about to save new course, they should be presented with three options: Save and return (to category management) Save and add users (default) Save and go to course Cancel The behaviour when editing an existing course should remain the same (returning the user to the course page after saving).
8.summary: Allow admins to control which course settings are available to users
description: Admins should be able to enable, lock or hide all/most course settings. This should be done from Course settings page in Moodle Site administration.
9.summary: Automatically copy full course name to short name as it is being added
description: When creating a new course, in many cases, the course short name and full name are the same. While this is not true in most cases, assisting the user to fill in this form will simplify the (often repetitive) process of creating courses. If the short name field is empty or if it is already identical to the full name, changes to the full name should be mirrored in the short name. When the short name field contains content that is different to the full name, it should be left alone.
10.summary: Add Undo button to Enrol users dialogue box
description: When a user enrols people in course, there is a dialogue box with an Enrol button next to each persons name. If a user accidentally clicks this button and enrols the wrong person, there is no quick way how to correct that. An improvement would be to add an Undo button next to newly enrolled person.
11.summary: There should be a button for user unenrollment instead of icon
description: In user enrollment page there should be a button for user unenrollment instead of icon. Currently it is an icon and is non-obvious. It should also be on seperate collumn, so it os divided from enrollment information
12.summary: Simplifications to Enrolled users page
description: The following changes are suggested for simplifying Enrolled users page. Move the "Proceed to course content" button to top and make the highlighted default button. Currently this button is only shown after a new course is created, but it should be shown all the time. Perhaps the label on the button could become "Return to course content" if changing enrolments under normal circumstances (ie not immediately after course creation). Collapse filter section and allow it to be expanded. The Filter button should not be a highlighted default button. The button to Proceed to course content is the logical next step, so should be highlighted. An Actions column should be created to the right of the enrolled users table. The delete and edit buttons should be moved to this column. Tooltips should be added to these buttons. The Roles column is unnecessarily wide. Column widths should be dynamic to allow narrow columns to expand. The date of enrolment is wrong when manual enrolments are used. It shows midnight of at the beginning of the date of enrolment instead of the correct enrolment time.
13.summary: Add link to non-AJAX enrolment page for bulk actions
description: The Enrolled users page relies on an AJAX dialogue to add new users. This is suitable for small classes where users are added individually. When JavaScript is disabled, the page reverts to the former Enrolled users page that uses side-by-side multi-select inputs to add and remove users from the list of enrolled users. This page is slightly more suitable for bulk actions. A link should be made form the new Enrolled users page to the old for admins/teachers who wish to add enrolments faster.
14.summary: Simplifcations to new user / edit profile form
description: There are a number of simplifications that can be made to the New user / Edit profile form. . Sections Make a new section called Location Make a new section called Actions . Moving Move Name fields to the top, above the user name Move authentication method and other actions (suspend and password) to the Actions section Move country, city and timezone to Location section Reduce the size of the description
15.summary: Allow admins to hide uncessary elements on New user / Edit profile form
description: A number of fields on the New user / Edit profile form are not relevant in many cases. Admins should have the potential to hide these options to simplify this form. country city timezone ID number institution department
16.summary: Quiz question bank pop-up: Add to quiz button should be disabled until a question is selected
description: Would be a small usability win.
17.summary: Move user profile email control field to their user preferences.
description: On each users profile, there is an option to change their preference for exposing their email address. There is an argument that this is a preference, rather than a profile field, and should instead appear in the users preferences.
18.summary: Keep the state of form sections between views of the same form
description: Currently users are presented with a minimal view of forms by containing and hiding optional settings in closed sections until the user expands a section. For a novice user this is appropriate as it avoids overwhelming the user. For more experienced users, however, it means that, to access optional settings, they have to expand each section that contains the settings they want. It is possible to expand all sections, but that creates a very long page. It would be helpful if the form remembered the state of expanded sections and restored this when the user returned to the form later. Its arguable whether this should persist between sessions.
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle
summary: Review third party libraries for new versions (3.1)
description: There are a number of third-party libraries distributed with Moodle. Before the major release, the available versions of these libraries should be reviewed. Check the list at which should be up to date with lib/thirdpartylibs.xml and other thirdpartylibs.xml files distributed around Moodle. Add any newly incorporated libraries into the list Check the available versions of each library If there is a significant new version and updating is recommended, the new version should be integrated by creating a sub-task to this issue and processing it through integration independently. If there is a readme_moodle.txt file with the plugin, this describes the customisations made for Moodle. Check when doing your review. Libraries review here: ||Library||Path||Current version||Last version||URL||MDL|| |AdoDB|/lib/adodb/|5.20.1|5.20.3| |less.php|/lib/lessphp/|1.7.0.9|1.7.0.10| |Google APIs Client Library|/lib/google/|1.1.5|1.1.7| |Minify|/lib/minify/|2.2.1|2.3.0| |Pear_Crypt_CHAP|/lib/pear/Crypt/CHAP.php|1.1|1.5.0 (stable) was released on 2010-09-19| | |Pear_HTML_Common|/lib/pear/HTML/Common.php|1.7|1.2.5 (stable) was released on 2009-04-03| | |Pear.php|/lib/pear/PEAR.php|1.4.5|1.10.1| |PHPMailer|/lib/phpmailer/|5.2.13|5.2.14| |Typo3|/lib/typo3/|4.7.19|7.6.4| |YUI|/lib/yuilib/|3.17.2|3.18.1| no, see below | |YUI Gallery|/lib/yuilib/gallery/|gallery-2013.10.02-20-26|gallery-2014.06.12-21-45| no, see below | |jQuery|/lib/jquery/|1.11.3|1.12.1| | |jQuery Migrate|/lib/jquery/|1.2.1|1.4.0| | |HTML2Text|/lib/html2text.php|3.0.0|4.0.0| |Markdown original+extra|/lib/markdown/|1.5.0|1.6.0| |ReCAPTCHA|/lib/recaptchalib.php|1.1|1.11| | | |XHProf|/lib/xhprof/|0.9.2|0.9.4 from 2013-09-30| | |RequireJS|/lib/requirejs/|2.1.20|2.1.22| | |Mustache|/lib/mustache/|2.9.0|2.10.0| | |Mustache.js|/lib/amd/src/mustache.js|2.1.3|2.2.1| | |CAS|/auth/cas/CAS/|1.3.3|1.3.4|
| Unsolvable | 1.summary: Update MathJax to version 2.6
description: This is effectively a repeat of , this time, upgrading from MathJax 2.5 to the recently released MathJax 2.6. This has bug fixes and new features, including better accessibility.
2.summary: Investigate which libraries need upgrading for 3.1
description: Investigate which libraries need upgrading for 3.1 ||Library||Path||Current version||Last version||URL||MDL|| |AdoDB|/lib/adodb/|5.20.1|5.20.3| | |less.php|/lib/lessphp/|1.7.0.9|1.7.0.10| | |Google APIs Client Library|/lib/google/|1.1.5|1.1.7| | |Minify|/lib/minify/|2.2.1|2.3.0| | |Pear_Crypt_CHAP|/lib/pear/Crypt/CHAP.php|1.1|1.5.0 (stable) was released on 2010-09-19| | |Pear_HTML_Common|/lib/pear/HTML/Common.php|1.7|1.2.5 (stable) was released on 2009-04-03| | |Pear.php|/lib/pear/PEAR.php|1.4.5|1.10.1| | |Typo3|/lib/typo3/|4.7.19|7.6.4| | |YUI|/lib/yuilib/|3.17.2|3.18.1| | |YUI Gallery|/lib/yuilib/gallery/|gallery-2013.10.02-20-26|gallery-2014.06.12-21-45| | |jQuery|/lib/jquery/|1.11.3|1.12.1| | |jQuery Migrate|/lib/jquery/|1.2.1|1.4.0| | |HTML2Text|/lib/html2text.php|3.0.0|4.0.0| | |Markdown original+extra|/lib/markdown/|1.5.0|1.6.0| | |ReCAPTCHA|/lib/recaptchalib.php|1.1|1.11| | |XHProf|/lib/xhprof/|0.9.2|0.9.4 from 2013-09-30| | |RequireJS|/lib/requirejs/|2.1.20|2.1.22| | |Mustache|/lib/mustache/|2.9.0|2.10.0| | |Mustache.js|/lib/amd/src/mustache.js|2.1.3|2.2.1| | |CAS|/auth/cas/CAS/|1.3.3|1.3.4| |
3.summary: Upgrade PEAR to 1.10.0
description: See See also comment
4.summary: Upgrade ADODB to 5.20.3
description: When we were upgrading to 5.20.1 in we have found a couple of problems, ADOdb team was kind enough to fix and make a new hotfix 5.20.2, as far as I can see from a new problem with mssql was discovered and they may release 5.20.3 soon
5.summary: Upgrade HTML2Text to 4.0.1 for Moodle 3.1 release
description: Upgrade html2text to 4.0.1
6.summary: Upgrade JQuery to 1.12.1 for Moodle 3.1 release
description: jQuery /lib/jquery/ 1.11.3 -> 1.12.1
7.summary: Upgrade RequireJS to 2.1.22 for Moodle 3.1 release
description: RequireJS /lib/requirejs/ 2.1.20 -> 2.1.22
8.summary: Upgrade Mustache to 2.10.0 for Moodle 3.1 release
description: Mustache /lib/mustache/ 2.9.0 -> 2.10.0
9.summary: Upgrade Mustache.js to 2.2.1 for Moodle 3.1 release
description: Mustache.js /lib/amd/src/mustache.js 2.1.3 -> 2.2.1
10.summary: Upgrade MathJax to 2.6 for Moodle 3.1 release
description: There are 2 admin settings that need to be updated if they havent been modified. filter_mathjaxloader | filter_mathjaxloader | and obviously this needs to be tested properly.
11.summary: Upgrade PHPMailer to 5.2.14 for Moodle 3.1
description: 5.2.14 was released on Nov 1, 2015
12.summary: Upgrade Horde to 5.2.12 for Moodle 3.1 release
description:
13.summary: Upgrade s3 repository to v0.5.1
description: We are using a random commit version atm - it would be nice to upgrade to a release version.
14.summary: Upgrade Google API library to 1.1.7 for Moodle 3.1 release
description: Google APIs Client Library /lib/google/ 1.1.5 1.1.7
15.summary: Upgrade less.php to 1.7.0.10 for Moodle 3.1 release
description: less.php /lib/lessphp/ 1.7.0.9 1.7.0.10
16.summary: Upgrade minify to 2.3.0 for Moodle 3.1 release
description: Minify /lib/minify/ 2.2.1 2.3.0
17.summary: Upgrade markdown library to 1.6.0 for Moodle 3.1 release
description: Markdown original+extra /lib/markdown/ 1.5.0 1.6.0
18.summary: Upgrade jQuery Migrate to 1.4.0 for Moodle 3.1 release
description: jQuery Migrate /lib/jquery/ 1.2.1 -> 1.4.0
19.summary: Update CAS library to 1.3.4 for Moodle 3.1 release
description: CAS /auth/cas/CAS/ 1.3.3 1.3.4
20.summary: Upgrade typo3 to 7.6.4 for Moodle 3.1 release
description: Typo3 /lib/typo3/ 4.7.19 7.6.4
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle
summary: Review third party libraries for new versions (3.1)
description: There are a number of third-party libraries distributed with Moodle. Before the major release, the available versions of these libraries should be reviewed. Check the list at which should be up to date with lib/thirdpartylibs.xml and other thirdpartylibs.xml files distributed around Moodle. Add any newly incorporated libraries into the list Check the available versions of each library If there is a significant new version and updating is recommended, the new version should be integrated by creating a sub-task to this issue and processing it through integration independently. If there is a readme_moodle.txt file with the plugin, this describes the customisations made for Moodle. Check when doing your review. Libraries review here: ||Library||Path||Current version||Last version||URL||MDL|| |AdoDB|/lib/adodb/|5.20.1|5.20.3| |less.php|/lib/lessphp/|1.7.0.9|1.7.0.10| |Google APIs Client Library|/lib/google/|1.1.5|1.1.7| |Minify|/lib/minify/|2.2.1|2.3.0| |Pear_Crypt_CHAP|/lib/pear/Crypt/CHAP.php|1.1|1.5.0 (stable) was released on 2010-09-19| | |Pear_HTML_Common|/lib/pear/HTML/Common.php|1.7|1.2.5 (stable) was released on 2009-04-03| | |Pear.php|/lib/pear/PEAR.php|1.4.5|1.10.1| |PHPMailer|/lib/phpmailer/|5.2.13|5.2.14| |Typo3|/lib/typo3/|4.7.19|7.6.4| |YUI|/lib/yuilib/|3.17.2|3.18.1| no, see below | |YUI Gallery|/lib/yuilib/gallery/|gallery-2013.10.02-20-26|gallery-2014.06.12-21-45| no, see below | |jQuery|/lib/jquery/|1.11.3|1.12.1| | |jQuery Migrate|/lib/jquery/|1.2.1|1.4.0| | |HTML2Text|/lib/html2text.php|3.0.0|4.0.0| |Markdown original+extra|/lib/markdown/|1.5.0|1.6.0| |ReCAPTCHA|/lib/recaptchalib.php|1.1|1.11| | | |XHProf|/lib/xhprof/|0.9.2|0.9.4 from 2013-09-30| | |RequireJS|/lib/requirejs/|2.1.20|2.1.22| | |Mustache|/lib/mustache/|2.9.0|2.10.0| | |Mustache.js|/lib/amd/src/mustache.js|2.1.3|2.2.1| | |CAS|/auth/cas/CAS/|1.3.3|1.3.4|
### Response:
1.summary: Update MathJax to version 2.6
description: This is effectively a repeat of , this time, upgrading from MathJax 2.5 to the recently released MathJax 2.6. This has bug fixes and new features, including better accessibility.
2.summary: Investigate which libraries need upgrading for 3.1
description: Investigate which libraries need upgrading for 3.1 ||Library||Path||Current version||Last version||URL||MDL|| |AdoDB|/lib/adodb/|5.20.1|5.20.3| | |less.php|/lib/lessphp/|1.7.0.9|1.7.0.10| | |Google APIs Client Library|/lib/google/|1.1.5|1.1.7| | |Minify|/lib/minify/|2.2.1|2.3.0| | |Pear_Crypt_CHAP|/lib/pear/Crypt/CHAP.php|1.1|1.5.0 (stable) was released on 2010-09-19| | |Pear_HTML_Common|/lib/pear/HTML/Common.php|1.7|1.2.5 (stable) was released on 2009-04-03| | |Pear.php|/lib/pear/PEAR.php|1.4.5|1.10.1| | |Typo3|/lib/typo3/|4.7.19|7.6.4| | |YUI|/lib/yuilib/|3.17.2|3.18.1| | |YUI Gallery|/lib/yuilib/gallery/|gallery-2013.10.02-20-26|gallery-2014.06.12-21-45| | |jQuery|/lib/jquery/|1.11.3|1.12.1| | |jQuery Migrate|/lib/jquery/|1.2.1|1.4.0| | |HTML2Text|/lib/html2text.php|3.0.0|4.0.0| | |Markdown original+extra|/lib/markdown/|1.5.0|1.6.0| | |ReCAPTCHA|/lib/recaptchalib.php|1.1|1.11| | |XHProf|/lib/xhprof/|0.9.2|0.9.4 from 2013-09-30| | |RequireJS|/lib/requirejs/|2.1.20|2.1.22| | |Mustache|/lib/mustache/|2.9.0|2.10.0| | |Mustache.js|/lib/amd/src/mustache.js|2.1.3|2.2.1| | |CAS|/auth/cas/CAS/|1.3.3|1.3.4| |
3.summary: Upgrade PEAR to 1.10.0
description: See See also comment
4.summary: Upgrade ADODB to 5.20.3
description: When we were upgrading to 5.20.1 in we have found a couple of problems, ADOdb team was kind enough to fix and make a new hotfix 5.20.2, as far as I can see from a new problem with mssql was discovered and they may release 5.20.3 soon
5.summary: Upgrade HTML2Text to 4.0.1 for Moodle 3.1 release
description: Upgrade html2text to 4.0.1
6.summary: Upgrade JQuery to 1.12.1 for Moodle 3.1 release
description: jQuery /lib/jquery/ 1.11.3 -> 1.12.1
7.summary: Upgrade RequireJS to 2.1.22 for Moodle 3.1 release
description: RequireJS /lib/requirejs/ 2.1.20 -> 2.1.22
8.summary: Upgrade Mustache to 2.10.0 for Moodle 3.1 release
description: Mustache /lib/mustache/ 2.9.0 -> 2.10.0
9.summary: Upgrade Mustache.js to 2.2.1 for Moodle 3.1 release
description: Mustache.js /lib/amd/src/mustache.js 2.1.3 -> 2.2.1
10.summary: Upgrade MathJax to 2.6 for Moodle 3.1 release
description: There are 2 admin settings that need to be updated if they havent been modified. filter_mathjaxloader | filter_mathjaxloader | and obviously this needs to be tested properly.
11.summary: Upgrade PHPMailer to 5.2.14 for Moodle 3.1
description: 5.2.14 was released on Nov 1, 2015
12.summary: Upgrade Horde to 5.2.12 for Moodle 3.1 release
description:
13.summary: Upgrade s3 repository to v0.5.1
description: We are using a random commit version atm - it would be nice to upgrade to a release version.
14.summary: Upgrade Google API library to 1.1.7 for Moodle 3.1 release
description: Google APIs Client Library /lib/google/ 1.1.5 1.1.7
15.summary: Upgrade less.php to 1.7.0.10 for Moodle 3.1 release
description: less.php /lib/lessphp/ 1.7.0.9 1.7.0.10
16.summary: Upgrade minify to 2.3.0 for Moodle 3.1 release
description: Minify /lib/minify/ 2.2.1 2.3.0
17.summary: Upgrade markdown library to 1.6.0 for Moodle 3.1 release
description: Markdown original+extra /lib/markdown/ 1.5.0 1.6.0
18.summary: Upgrade jQuery Migrate to 1.4.0 for Moodle 3.1 release
description: jQuery Migrate /lib/jquery/ 1.2.1 -> 1.4.0
19.summary: Update CAS library to 1.3.4 for Moodle 3.1 release
description: CAS /auth/cas/CAS/ 1.3.3 1.3.4
20.summary: Upgrade typo3 to 7.6.4 for Moodle 3.1 release
description: Typo3 /lib/typo3/ 4.7.19 7.6.4
|
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic. | project: Moodle app
summary: Add support for desktop apps
description: Some of the Cordova APIs must be replaced to use native HTML5 and Chromium webkit functions, see the current lib/mm.emulator.js
| Unsolvable | 1.summary: Pull notifications in desktop app to simulate push notifications
description: Push notifications arent supported in desktop apps. Well have to implement a polling service to check if there are new notifications and show them as if they were push notifications.
2.summary: Allow recording audio/video and taking pictures in desktop apps
description: I found this library that could be used: We can also implement it ourselves using navigator.mediaDevices.getUserMedia and MediaRecorder. This will require creating our own templates for this.
3.summary: Support main features of MoodleMobile in desktop app
description: Support the main features of the app in a desktop app: download and open files, SSO, upload files, etc.
4.summary: Package the Electron app to be published in Windows Store
description:
5.summary: Package the Electron app to be published in MacOS Store
description: The same we did for Windows but for MacOS
6.summary: Package the Electron app to be published in Ubuntu Store
description: Use snapcraft to publish a classic snap in the Ubuntu Store
7.summary: Build the desktop app for Linux 32 bits
description: We should check if it is possible to build easily a 32bits version of the desktop app for Linux3.
| Below is an instruction that describes a task, paired with an input that provides an epic with this format:
"project": "Name of the project"
"summary": "Summary of the epic user story"
"description": "Description of the epic user story". Write a response that appropriately completes the request.### Instruction:
Break this epic user story into smaller tasks to help the developers understand the epic better, you can divide this epic into as much as you want depending on the complexity of the epic.
### Input:
project: Moodle app
summary: Add support for desktop apps
description: Some of the Cordova APIs must be replaced to use native HTML5 and Chromium webkit functions, see the current lib/mm.emulator.js
### Response:
1.summary: Pull notifications in desktop app to simulate push notifications
description: Push notifications arent supported in desktop apps. Well have to implement a polling service to check if there are new notifications and show them as if they were push notifications.
2.summary: Allow recording audio/video and taking pictures in desktop apps
description: I found this library that could be used: We can also implement it ourselves using navigator.mediaDevices.getUserMedia and MediaRecorder. This will require creating our own templates for this.
3.summary: Support main features of MoodleMobile in desktop app
description: Support the main features of the app in a desktop app: download and open files, SSO, upload files, etc.
4.summary: Package the Electron app to be published in Windows Store
description:
5.summary: Package the Electron app to be published in MacOS Store
description: The same we did for Windows but for MacOS
6.summary: Package the Electron app to be published in Ubuntu Store
description: Use snapcraft to publish a classic snap in the Ubuntu Store
7.summary: Build the desktop app for Linux 32 bits
description: We should check if it is possible to build easily a 32bits version of the desktop app for Linux3.
|