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.7.1/3.6.5 upgrade
description: Moodle 3.7.1 is scheduled for release on Monday 8 July 2019.
| Unsolvable | 1.summary: Upgrade moodle.net to 3.6.5
description:
2.summary: Upgrade dev.moodle.org to 3.6.5
description:
3.summary: Upgrade moodle.org to 3.7.1
description:
4.summary: Upgrade learn.moodle.net to 3.7.1
description:
5.summary: Upgrade school.demo.moodle.net to 3.7.1
description:
6.summary: Upgrade demo.moodle.ne... | 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:
Brea... |
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: Forum improvements for 3.8
description: Forum improvements for 3.8
| Unsolvable | 1.summary: Allow user to edit forum posts
description: allow user to edit forum posts from moodle mobile.
2.summary: Forum - posts without replies sometimes the time elapsed is shown
description: Using the App (Android mobile device as well as iPhone as well as Moodle Desktop (Mac)), posts without replies (0 replies) o... | 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:
Brea... |
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: MoodleNet 3.0.0
description: MoodleNet 3.0 advances version 2.x.x to include an Extensibility Environment for Developer Contributions and Add-Ons. This provides a structured and documented way to allow internal and external developers to develop non-core features for MoodleNet. This will all... | Unsolvable | 1.summary: Profile Page improvements
description: bru.mas finalize current impl as static page in storybook ettore.bevilacqua then implement Ctrl and apply to webapp route
2.summary: Admin page
description: An Admin page needs to be set up.
3.summary: deploy a staging server
description: Would be great to have kind of ... | 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:
Brea... |
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: MUA new model setup (Discovery)
description: Goal: propose a new setup for MUA /HQ/ community interaction MUA ideas - board of trustees / steering group including volunteers elected and recognised (how) top universities and contributors - Regular Community Teams/ MUA liaison mee... | Unsolvable | 1.summary: Initial draft with MUA
description: Aurelie to review work so far in MUA Improvement Planning document by MUA. and organise next meeting to review inputs.
2.summary: MUA committee / Aurelie interviews to build proposal
description: Aurelie will book time with all who can on the committee during November, and... | 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:
Brea... |
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 theme epic
description: Collection of issues raised during 4.0 dev that have been deferred till 4.1+
| Unsolvable | 1.summary: Move form submit buttons to the left
description: The form submit buttons should be aligned left to match the UX designs in figma
2.summary: Allow users to resize and crop images
description: To give users more control over images like the profile picture and images used in content users should be able to re... | 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:
Brea... |
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 accessibility of the filepicker
description: A new LMS accessibility study from University of Illinois was published recently, unfortunately they had Moodle 2.3 only, but has some useful things to say: The main issue they had was unfortunately with our filepicker, which is complex. Ive ... | Unsolvable | 1.summary: Explore ideas for reducing the size of the file picker.
description: The filepicker takes up alot of vertical space. When it is used in a form in pushed elements below it off the bottom of the page. Because it is large, it also implies (visually) that it is important which may not be the case (e.g. coursefil... | 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:
Brea... |
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.6
description: In 3.6 we can remove functionality that was deprecated in 3.2 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 the... | Unsolvable | 1.summary: Properly deprecate print_textarea()
description: This issue remains here so we can eventually deprecate this function when all usages are removed. Until then keep moving it to the next deprecation epic Deprecated function print_textarea() does not display debugging message. Also there are still usages in cor... | 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:
Brea... |
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.0
description: In 4.0 we can remove functionality that was deprecated in 3.8 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 the... | Unsolvable | 1.summary: Phase 2 of deprecation of functions in lib/deprecatedlib.php initially deprecated in 3.8
description: As per all functions in lib/deprecatedlib.php that were deprecated in 3.8 should be replaced with exceptions in 4.0 This includes all functions in lib/deprecatedlib.php that say since 3.8 If any functions fr... | 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:
Brea... |
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: Web service API Roadmap
description: .How to add a web service function into core if you want to suggest or implement a web service function, read the Moodledocs| .Integration priority the ones required for the official Mobile app (generally very few) the ones for which a git patch has been sub... | Unsolvable | 1.summary: mod_resource_get_resources_by_courses
description: Retrieve a list of resources from several courses
2.summary: New Web Service mod_page_view_page
description: Trigger the module view event and update completion status. This function will be used by the Mobile app in order to allow logging and trigger events... | 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:
Brea... |
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 Create an Event Monitor tool
description: Create a report that lets users subscribe to various events happening in Moodle.
| Unsolvable | 1.summary: Event monitor: Finalise the basic file and database structure
description: Commit the basic file structure with the following:- Directory structure xmldb files permissions (db/access.php)
2.summary: Event monitor: Create a rule manager class with unit tests
description: Create a class report_monitor\rule_man... | 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:
Brea... |
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: Initial release of user-specific page
description: Initial release of user-specific page
| Unsolvable | 1.summary: Give user control of whats shown in My feed
description: As reported on Changemap| a user has suggested more control of the My feed timeline on the home page. At the moment, this is just a feed of everything on the instance, but eventually it should be a feed of updates around: Communities the user is part o... | 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:
Brea... |
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.3 upgrade
description: Moodle 3.6.3 was released on Monday 11 March 2019.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.6.3
description:
2.summary: Upgrade learn.moodle.net to 3.6.3
description:
3.summary: Upgrade lang.moodle.org to 3.6.3
description:
4.summary: Upgrade school.demo.moodle.net to 3.6.3
description:
5.summary: Upgrade demo.moodle.net to 3.6.3
description:
6.summary: Upgrade moodle.n... | 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:
Brea... |
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: Gradebook push from HQ in 2014
description: These are a list of some of the important Grade issues that we are looking at in 2.8.
| Unsolvable | 1.summary: Grade Scales - Currently, only integers can be specified as letter grade boundaries when creating a grade scale. Provide the ability to specify a real number.
description: When creating a grading scale, the letter grade boundary is chosen from a drop-down list box and only an integer can be chosen. For examp... | 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:
Brea... |
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 on MoodleNet servers should be able to interact across instances
description: Users on MoodleNet servers should be able to interact across instances
| Unsolvable | 1.summary: UX for following remote community/collection via search
description: .
2.summary: Set up another MoodleNet instance for initial testing
description: Mayel to ask DevOps to set up.
| 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:
Brea... |
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: Performance tool for finding performance regressions
description: We already have moodle-performance-comparison| for finding performance regression, then why a new tool? With current tool, we have hit some bottleneck issues and they were discussed in iTeam meeting| As per proposal| this tool wi... | Unsolvable | 1.summary: Data generator for performance tool
description: Data generator is a very important aspect of performance tool, as it create a target site against which the performance metrics will be generated. Target site should not be changed, if data needs to be compared over the period. Current data generator for perfo... | 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:
Brea... |
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: Learn Moodle MOOC Jan 2017
description:
| Unsolvable | 1.summary: Create a sign-up enrolment plugin for Learn Moodle
description: Needs to cater for user-friendly enrolment to the upcoming MOOC for both new and returning users including mobile app users. In the Sept 2013 MOOC we used the standard self-enrolment plugin, however it proved a problem for people to click a link... | 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:
Brea... |
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: Analytics 3.8 improvements
description: List of improvements / relevant bug fixes for Moodle 3.8
| Unsolvable | 1.summary: Analytics models may be restricted to category or course contexts
description: is scheduled for 3.7, it will allow people to create as many prediction models as they want, reusing the same target. A new "Restrict model to the following contexts" option would allow people to set up separate predictive models ... | 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:
Brea... |
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 Assignment 2.2
description: Remove mod_assignment (NOT mod_assign) from the platform. This activity has been disabled by default since version 2.2 (2012) and has been long replaced by mod_assign. It It s important to remove things like this to reduce technical debt and the ongoing suppor... | Unsolvable | 1.summary: Remove Assignment 2.2 (mod_assignment) from core
description: The Assignment 2.2 activity module has been disabled by default since 2012 but was kept to enable pre-2.2 backups to be restored and have the assignments auto-converted to new assignments. Lets remove it from Moodle 4.2 and add it to the git repos... | 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:
Brea... |
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: Downloads reboot
description: Download sites to have green colour-scheme and a better design covering all the downloads we have including mobile in nice clear pages.
| Solvable | 1.summary: Plugins redesign
description:
2.summary: Downloads site makeover
description: From Martins notes: bq. Re-make Download site as a simple web page and update it with new theme.
3.summary: Switch download.moodle.org from CVS to git
description: With CVS being abandoned completely in January 2013, its time to s... | 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:
Brea... |
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: Events 2
description: Major overhaul of the current event system. Specification doc:
| Unsolvable | 1.summary: Pre and post performance profiling
description: Decide and implement performance tests, to measure the impact of the changes.
2.summary: Check coverage of unit tests for new events API
description: Write unit tests for anything that was not covered in previous issues. Create new event handler management clas... | 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:
Brea... |
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: Create a Moodle overview video that cleanly shows anyone what Moodle actually does
description: We really need one clean, professionally-designed overview video that really explains how the Moodle software works. I imagine a slick quality entertaining video not more than 5 minut... | Unsolvable | 1.summary: Develop storyboard for Moodle software overview video
description: Final Storyboard (subject to modifications during production): (SHOTS run under the text that follows them.) SHOT: intro titles SHOT: animated or talking head or both Moodle is a course management system. Moodle runs on a web server, and by c... | 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:
Brea... |
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 Theme and Navigation changes for Moodle 3.2
description: This epic collects together the issues related to the new theme and navigation changes for Moodle 3.2. For more information see the specification: The prototype site for this theme is and the login is admin / test.
| Unsolvable | 1.summary: Add some info to the performance footer when theme designer mode is on
description: Ive almost started investigating performance issues a few times because ive been tripped up by being in theme designer mode and using the more theme and wondered why things are going so slow. (The reason which I am well aware... | 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:
Brea... |
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 issues to be fixed from the findings of the accessibility audit
description: This epic contains the list of accessibility issues raised during the Moodle accessibility audit.
| Unsolvable | 1.summary: Improve UI accessibility on small viewports
description: From the audit results: . Issue Some user interfaces are not usable when text is zoomed to 200 or the UI is zoomed to 400 . Impact on users Screen reader users can call up a list of headings. Empty headings can cause confusion. . Guidelines affected Re... | 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:
Brea... |
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.10 upgrade
description: Moodle 3.10 is scheduled for release on Monday 9 November 2020.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.10
description:
2.summary: Upgrade learn.moodle.org to 3.10
description:
3.summary: Upgrade school.moodledemo.net to 3.10
description:
4.summary: Upgrade sandbox.moodledemo.net to 3.10
description:
5.summary: Upgrade archive.moodle.net to 3.10
description:
6.summary: Upgrade stat... | 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:
Brea... |
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.9)
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 ... | Unsolvable | 1.summary: Upgrade VideoJS to 7.7.6, 2.6.1, 2.2.1 and 5.4.2
description: VideoJS (/media/player/videojs/amd/src/video-lazy.js) 7.6.5 --> 7.7.6: VideoJS (/media/player/videojs/amd/src/video-lazy.js) 7.6.5 --> 7.7.6: VideoJS support files (/media/player/videojs/videojs/) 7.6.5 --> 7.7.6: The Flash tech for video.js (/med... | 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:
Brea... |
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/OER set-up
description: We need an attractive and inviting page, with URL say (to be confirmed) listing Moodle courses and content to download The page should have: A list of latest OER added to the site A welcome / intro sentence or paragraph A search Links to elsewh... | Solvable | 1.summary: Create wireframe for Moodle.net/oer
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:
Brea... |
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 and Question bank in Moodle 4.2
description: Further improvements to Quiz and question bank in Moodle 4.2 Docs (TBA)
| Unsolvable | 1.summary: Create configurable question bank view
description: TBA
2.summary: Create configurable question bank view for qbank_history
description: TBA
| 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:
Brea... |
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: MoodleMoot Australia 2015 issues
description: This is the collection of tracker issues related to MootAu15.
| Unsolvable | 1.summary: Design appropriate background/theme for AU MoodleMoot site
description: Currently the Au and US MoodleMoot sites are using relatively generic background images. Before the sites are used in earnest, adding a more appropriate background for each would give the sites a greater identity. There are no specific t... | 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:
Brea... |
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 parallel development support
description: After Moodle 3.9 release, its being planned to start working in parallel with 2 lines of development, each one leading to different major releases. This implies changing some assumptions, about versions, branches, the names of bot... | Unsolvable | 1.summary: Update composer.json with the new moodlehq/behat-extension tag for 4.0dev (and exceptionally, 3.10dev)
description: Special notes (for this issue only): Note: This must be done for as many dev branches still not having their corresponding tags. Normally its only master, but under parallel development periods... | 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:
Brea... |
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: Merge Participants and Enrolled Users page follow-up
description: These are a list of issues related to the merging of the two pages in .
| Unsolvable | 1.summary: Add ability to download the Participants table
description: There is a Moodle 2.3 plugin by Kirill Astashov: that does the trick but is restricted to PostgreSQL. It is a useful feature for user mgmt that has been left aside..
2.summary: Allow multiple same type filters on Participants page
description: It wo... | 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:
Brea... |
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 (4.3 release)
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. Run the new task to get the libraries that need to be updated (it... | Unsolvable | 1.summary: Upgrade phpxmlrpc to 4.10.1
description: phpxmlrpc phpxmlrpc 4.8.1 --> 4.10.1
2.summary: Upgrade XHProf to 2.3.9
description: XHProf (/lib/xhprof/) 2.3.5 --> 2.3.9 :
3.summary: Upgrade Tiny to 6.6.2
description: Tiny lib/editor/tiny/ 6.3.2 --> 6.6.0 Changelog:
4.summary: Upgrade ogv.js to 1.8.9
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:
Brea... |
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 upgrade to 2.7
description: Following the release of Moodle 2.7, all Moodle community sites need to be upgraded. Target completion date: Monday 19th May.
| Unsolvable | 1.summary: Reinstall School demo site
description: The School demo has been observed to have a number of database issues over the last couple of years, and most recently when attempting to upgrade to 2.6.2 as part of It is therefore planned to reinstall the site
2.summary: Upgrade moodle.org to 2.7
description: Moodle.... | 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:
Brea... |
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.2
description: In 3.2 we can remove functionality that was deprecated in 2.9 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 the... | Unsolvable | 1.summary: Allow only to upload files to draft area in core_files_upload
description: There is currently a debugging message there saying that upload files to the user private area is deprecated.
2.summary: Remove deprecated course/category.php
description: was deprecated in Moodle 2.5, and is due for removal. Unfortun... | 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:
Brea... |
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: Bulk editing of activities completion rules in a course
description: This is part of MUA project MUA-26, to help make the dashboard better mockups more discussion and screenshots on UX-20
| Unsolvable | 1.summary: Create form for bulk editing completion on existing activities
description: Part of the epic this is the form that displays completion rules that are similar between selected activities, allows to modify them and tries to apply to all of them. Updating some activities may result in errors (for example, compl... | 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:
Brea... |
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: Translation site improvements part 2
description: Translation site reboot follow-up issues.
| Unsolvable | 1.summary: Display stats on translation site front page
description: As suggested by Martin in : quoteCould we make some basic stats a lot more prominent there? We have translation as a major menu item in our sitebar so it would be nice when anyone clicks on it that they see something on this page about how many langua... | 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:
Brea... |
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.9.2 upgrade
description:
| Unsolvable | 1.summary: Upgrade moodle.org to 2.9.2
description:
2.summary: Upgrade learn.moodle.net to 2.9.2
description:
3.summary: Upgrade lang.moodle.org to 2.9.2
description:
4.summary: Upgrade school.demo.moodle.net to 2.9.2
description:
5.summary: Upgrade demo.moodle.net to 2.9.2
description:
6.summary: Upgrade dev.mood... | 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:
Brea... |
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: Improvement to the quiz reports, especially the statistics
description: This is a set of changes requested by the OU. Jamie Pratt is implementing them.
| Unsolvable | 1.summary: Unit tests for quiz statistics report
description: We want to be able to unit test the quiz reports. This will involve populating the unit test db with test data. Using the data generator we want to be able : Create test instances of each sort of question type. Create a quiz from a set of questions. Supply a... | 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:
Brea... |
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 LMS / MoodleNet integration project - Phase 2
description: This epic follows on from the progress of , to expand the functionality available for teachers sharing content from Moodle LMS to MoodleNet, beyond the MVP scope of that original epic. The key persona in this phase of the project... | Unsolvable | 1.summary: Allow teachers to share courses to MoodleNet (all activities)
description: This issue resolves the following user story: As a teacher, I can share the contents of a whole course as a Moodle backup file to MoodleNet, so others can import and use the course I have written. . Requirements A new capability, _moo... | 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:
Brea... |
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: User should be able to configure settings on a separate page
description: User should be able to configure settings on a separate page.
| Solvable | 1.summary: Move language selector to settings page
description: Create a separate settings page, instead of a modal.
2.summary: Link to Code of Conduct from user drop-down menu
description: As we are removing the current home page text when we launch Beta v0.1 we need somewhere for the Code of Conduct to live: Note tha... | 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:
Brea... |
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: Integrate a customizable report builder into core
description: This Epic is intended to support the Learning Analytics roadmap, specifically Implement UI for creating and editing learning analytics models. However, there are other benefits for the Moodle community, as described below. A general... | Unsolvable | 1.summary: Custom Reports should use Moodle API whenever possible
description: Use only Moodle API: the forms-based function of Configurable Reports should use the Moodle API to retrieve data whenever possible, not direct database access. E.g. for grades, use grade_get_course_grade($user->id, $courseid) When there is n... | 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:
Brea... |
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: Merge Participants and Enrolled Users
description: Let us merge them! Two user lists with almost identical content, in different locations. || Item || Type || Link to ||Enrolment page || Participants (brief) || Participants (detailed) || || Profile picture | Data/Picture | Profile | (/) | (/) |... | Unsolvable | 1.summary: Discuss user stories / requirements
description: ||User Story||Acceptance Criteria|| |As a teacher I want to be able to if a users can access the course or not.| - If the current user has moodle/course:enrolreview capability, show a column with the enrolment status for each student. - The enrolment status sh... | 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:
Brea... |
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: Group messaging follow-ups
description: These are follow-ups to group messaging.
| Unsolvable | 1.summary: Add emojis to messaging
description: Add emoji support to messaging as is common in most standard messaging services.
2.summary: Show plain text in Messages summary pane
description: From discussion with michaelh: quoteI think the reason is that you wouldnt want things like showing massive text within the su... | 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:
Brea... |
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: Make Moodle OBv2.1 implementation compliant and get certification
description: Support to OBv2.1 was added in for Moodle 3.9. However, it was one of the first implementation of this specification and there were no certification process for that. Since then, some early adopters have been working... | Unsolvable | 1.summary: Add new "IMS OBv2.1" OAuth 2 service
description: While testing OBv2.1 with several backpack providers, such as Badgr or CampusLabs, we realised our current OBv2.1 implementation in Moodle is ignoring the content in manifest file /.well-known/badgeconnect.json. Tests with IMS Digital credential service worke... | 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:
Brea... |
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: Add links and a drop down to navigate between activities
description: When did they go? I dont know. Adding back the next/previous links was rated as a high priority issue for 3.4. This epic collects the user stories and tasks required to complete this work. See --
| Unsolvable | 1.summary: User Stories for next/previous links on activities.
description: ||User Story||Acceptance Criteria|| |As a user, I should be able to step through activities in the course without returning to the course page in order to stay focused on completing activities| Each activity should have a next/previous link in ... | 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:
Brea... |
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: Additional Theme and Navigation changes for Theme "Boost"
description: This is an epic to collect "optional" (not blocking) issues related to the new "Theme Boost" for Moodle 3.2.
| Unsolvable | 1.summary: Convert all the nav block and settings links into contextual lists on each page.
description: Some background to this. Blocks in general are seen by practically all web designers Ive ever met as "old school" and something we should get rid of, or at least deprecate. Many sites hide those blocks in Moodle, in... | 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:
Brea... |
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 4.0 Migration
description: This epic covers the work to convert from the original BS4 Alpha 3 integration to BS4.0.
| Unsolvable | 1.summary: Update bootstrap 4 to final release
description: The new release plan for bootstrap 4 is to go up to alpha 6, then switch to more stable betas. Alpha 5 just came out.
2.summary: Implement course images for the myoverview block
description: The myoverview block is being redesigned based on UX studies and the ... | 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:
Brea... |
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 feedback module for the Mobile app
description: - Move some view.php/continue.php code to functions - Add required web services - Implement the check_updates callback Spec: (wip)
| Unsolvable | 1.summary: New Web Service mod_feedback_get_feedbacks_by_courses
description: Retrieve a list of feedbacks from several courses
2.summary: New Web Service mod_feedback_view_feedback
description: To mark view completed and optionally launch the mod viewed event
3.summary: New Web Service mod_feedback_get_feedback_access... | 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:
Brea... |
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 the bootstrapbase theme and remove from core
description: Boost is the new default. Time to start deprecation of clean and bootstrapbase.
| Unsolvable | 1.summary: Move all templates from boost to core and (where relevant) core to bootstrapbase
description: All core templates should now belong to boost rather than bootstrapbase. We need to: move all existing core templates which are overridden by boost into the bootstrapbase theme move all templates from boost to core
... | 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:
Brea... |
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 organisations want to run their own MoodleNet instance?
description: Users can choose a MoodleNet instance to join and sign in with their social account. Organisations can set up their own instance and enter an API key to access the functionality of Moodle HQ s API-as-a-service (e.g. fede... | Unsolvable | 1.summary: Spec out admin dashboard for federated instances
description: We should use this issue to talk about longer-term admin features. The MVP admin dashboard issue is ----- Older info: Ive been talking to Gavin have doing some value proposition work. In particular, system admins deploying a MoodleNet instance wan... | 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:
Brea... |
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.8)
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 ... | Unsolvable | 1.summary: Upgrade Horde library to 5.2.22
description: creating this issue long in advance before 3.5 libraries upgrade start. We have previously closed several rounds of Horde upgrade because there were "no changes upstream". However says that this repo is deprecated and separate repos should be used. We will need to... | 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:
Brea... |
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: Stop repeating db queries
description: We all know that moodle sends lots of db reads to the db server but while working on (trying to reduce the number of db reads) Ive realized that in some cases this goes too far, for example a mod_assign grading page sends 433 db reads and it is not i... | Unsolvable | 1.summary: Improve filter_data performance on large sites
description: As a follow-on to which removed global text caching, we need to examine the database filter and probably add MUC caching there to improve performance. The database filter is what puts links in texts to database entries. There is quite a lot of proce... | 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:
Brea... |
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: Follow up: Secondary & Tertiary Navigation improvements 4.0
description: Once lands remove the old navigation UI elements and address found issues which should be added to this epic.
| Unsolvable | 1.summary: Implement tertiary navigation for plugin set 1 of 4
description: Given the completion of we will have the functionality for modules to define their own navigation outside of the primary & secondary navigation structures. Given the designs on figma| we need to go through each module and either implement the n... | 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:
Brea... |
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: Issues related to analytics models editing for 3.7
description: The base issue is although extra work is needed to fully support the creation and the deletion of analytics models, including import and export features. You need to log in to see the list of issues that are part of this epic.
| Unsolvable | 1.summary: Add behat tests for analytics models editing options
description: We need behat tests for the built-in models, it is not very quick to setup the environment to test models like students at risk of dropping out because we need finished courses and current courses, we need a significant amount of students acti... | 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:
Brea... |
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: A list of theme issues related to the Moodle 4.0 UX changes
description: To enforce visual consistency across the 4.0 UX this epic lists changes related to the themes only. Please add issues here where styling changes from the UX projects that might affect other UI components
| Unsolvable | 1.summary: Add new course management buttons to my courses
description: Given discussions presented by the UX team it has been raised that a quick UX win could be to add the following buttons to the incoming my courses page: "New course" & "Manage courses" this would allow users from having to navigation into the link ... | 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:
Brea... |
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 accessibility issues
description: This epic contains the collection of accessibility issues related to the atto editor.
| Unsolvable | 1.summary: Atto dosent add "img-responsive" class tag when i use drag and drop
description: i can see code:java class="img-responsive" code when i upload image it using the image button of atto toolbar BUT i cant see code:java class="img-responsive" code tag when i upload image it using drag and drop . i want to use dr... | 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:
Brea... |
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: Calendar Improvements - followup
description: Calendar Improvements - followup to
| Unsolvable | 1.summary: Improve the calendar monthly view for better support for visual impairment
description: Take a look at the colours used for the month view of the calendar and make sure they are appropriate for visually impaired users.
2.summary: Add support for drag/drop of lesson activity action events
description: Allow t... | 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:
Brea... |
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: Download course content
description: This epic covers deliverable elements of the MUA "Download all" 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... | Solvable | 1.summary: Add ZipStream library to core
description: Look to add the ZipStream library to core: Without using composer Will need a new wrapper in core\zipstream to extend ZipStream\ZipStream and definition in lib/classes/component.php Wrapper should have a Moodle abstraction to get an instance with a default configura... | 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:
Brea... |
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: Participant page filters project
description: Collection of issues for the Participant page filters project
| Unsolvable | 1.summary: Add global and/or/not (jointype)
description: We need to add the global and/or/not to the UI to match the prototype
2.summary: Create filter classes
description: Rather than passing in arbitrary strings, arrays, ints, and other values into tablelib to describe filter values, it would be beneficial to describ... | 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:
Brea... |
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: UX / UI analytics improvements for 3.8
description: List of UX / UI improvements to analytics for Moodle 3.8.
| Unsolvable | 1.summary: Analytics models should be sorted by name and not last modified
description: Since the model lists are ordered by time modified every time you change something in a model it climbs on top of the page, a better UX, in my opinion, would be just to leave it order by ID, instead of enabled, timemodified
2.summar... | 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:
Brea... |
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: Dev site reboot
description: Dev site to have a dark blue colour scheme. - front page
| Solvable | 1.summary: Create a separate skin for the dev docs
description: The dev docs should have a dark blue colour scheme, whereas the user docs should be purple.
2.summary: Upgrade dev.moodle.org and add sites bar and new theme
description: Dark blue colour scheme, moodleclean theme. Upgrade checklist:
| 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:
Brea... |
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: Define high-level technical architecture
description: See issues included in this epic.
| Solvable | 1.summary: Specify criteria for technology/protocol/standards choices
description: WIP
2.summary: Create diagrams to represent each option
description: WIP
| 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:
Brea... |
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: Assessment Analytics Working group priority issues
description: These issues are generated from the work of the Assessment Analytics working group| that took place at MootAu15| The issues relate mainly to assignment feedback and how that can be made more relevant and useful.
| Unsolvable | 1.summary: Feedback Response Rating - Allow students to indicate whether feedback was helpful
description: As a means of encouraging students to reflect on feedback given to them and to offer teachers/markers an indication of the value the student places on the provided feedback, controls that allow students to rate fe... | 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:
Brea... |
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: Replacement for the course and category management pages
description: This issue has been created to look at a possible replacement for the course and category management pages within Moodle. The management system we currently have is getting pretty antiquated and could really do with a make ov... | Unsolvable | 1.summary: Add functionality to duplicate a course within the selected category
description: Thanks Hartmut for the suggestion! Please see this comment:
2.summary: Write Behat tests for this new UI
description: This is two parts really: Write behat tests for this. Remove behat tests for the old interfaces.
3.summary: R... | 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:
Brea... |
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 Dock JS to use Shifter, and be more performant
description: Update the Dock JS to use Shifter, and improve performance aspects.
| Unsolvable | 1.summary: Convert the dock to a YUI module.
description: This is an easy one.... ;) Convert the dock into a YUI module that gets built by shifter.
2.summary: Change naming pattern for dock-loader to use submodule naming pattern
description: As discussed in , this should use an appropriate submodule name - e.g. moodle-... | 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:
Brea... |
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 JS Framework
description: Implement a new JS Framework based on the doc and discussion here: Components: RequireJS Grunt JQuery UI (with accessibility wrapper)
| Unsolvable | 1.summary: RequireJS AMD Javascript loader
description: Add the RequireJS + hooks required to load AMD modules.
2.summary: Templates for renderers
description: Docs link: Forum link: Add mustache support for templates. Allow identical calling from php or javascript.
3.summary: Unified Ajax script handler
description: C... | 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:
Brea... |
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.2
description: In Moodle 4.2 we can remove functionality that was deprecated in 3.10 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... | Unsolvable | 1.summary: Final deprecation of plagiarism functions
description: Do the final deprecation of: plagiarism_save_form_elements() plagiarism_get_form_elements_module() plagiarism_plugin::get_form_elements_module() plagiarism_plugin::save_form_elements() The first two files need to be moved into deprecatedlib.php and the 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:
Brea... |
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 existing log reading analysis to use the proposed system.
description: Assuming to system proposed in Logging_2| is implemented we will need to convert any places that read from the log table to use the new system.
| Unsolvable | 1.summary: Replace usages of the log table in admin/handlevirus.php
description: See usages|
2.summary: Replace usages of the log table in backup/util/helper/backup_cron_helper.class.php
description: See usages|
3.summary: Replace usages of the log table in backup/util/structure/backup_nested_element.class.php
descript... | 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:
Brea... |
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: Downloads site migration and upgrade
description: downloads.moodle.org is out of the K8s infrastructure and uses Moodle 3.5 version. Initial review|
| Unsolvable | 1.summary: Moodle 4.1 branches for download.moodle.org
description: Create the Moodle 4.1 branches for download.moodle.org in the repository sites (
2.summary: Download Server migration: plan migration dates and plan communication
description: We discussed that the date could be either week commencing 3rd April or 24th... | 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:
Brea... |
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.1
description: And again, more deprecations in the PHP language that moodle has to work with. PHP 7.1 is expected in December 2016, we should aim to make Moodle 3.2 compatible with it.
| Unsolvable | 1.summary: Add environment check for versions where PHP 7.1 is NOT supported
description: Add env check to 3.0 and 3.1 similar to the one added to previous versions for php7 see
2.summary: enrollib has sloppy casting from array to string that doesnt work in php 7.1
description: Test the LTI provider - fix bugs (Sorry I... | 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:
Brea... |
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: Improvements to the export features
description: The export features of Scheduler have not really been reviewed since the 1.9 version, and the code is in need od refactoring/rewriting. Im collecting here all the current issues and feature requests relating to exports.
| Unsolvable | 1.summary: Add "export/print sign-up list" feature
description: It would be nice to have a feature for each scheduler instance where you could export a list of students who have signed up for that particular scheduler. Theres a need at my school to have a print-out of people whove signed up for a scheduler so that role... | 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:
Brea... |
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 the course UI
description: The Course UI is build on the core course renderers and the course format renderers. Over time UI has degraded because of theme and navigation changes. The course editing looks particularly bad on mobile devices. To improve the Course UI these steps could be t... | Unsolvable | 1.summary: Work on converting the course format renderer to templates
description: Currently Moodles course formats are run heavily though the renderer in course/format This can be better handled as it primarily echos out html_writer items, we can add new functions to better build our renderable objects and parse them ... | 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:
Brea... |
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 mod_feedback to be enabled by default
description: Mod feedback is installed, but not enabled by default. Martin requested it be enabled by default starting from 3.0. Same applies to block_feedback After some discussion, it was decided that it was not safe enough to do so this stage so ... | Unsolvable | 1.summary: Is it possible to export the data collected in Feedback to a .csv file?
description: Is it possible to export the data collected in Feedback to a .csv file?
2.summary: Allow non-alpha characters in the label in feedback
description: In mod/feedback/item/feedback_item_form_class.php, there is one line of 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:
Brea... |
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: Replace existing reports in Core based on Configurable Reports
description: This Epic is related to the proposal to construct a UI for creating and editing learning analytics models: This is a proposal to replace as many Core reports as possible using the forms-based Configurable Reports tool (... | Unsolvable | 1.summary: Replace/enhance Participants report using form-based editable report
description: . Location: Navigation block Course Gear menu / Users tab / Enroled users . Description: This report provides a list of all participants in a course to each of the participants in the course, including: First name (sortable) Su... | 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:
Brea... |
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: Add a behat feature to add all of Moodles blocks in all contexts
description: This is a good idea as can catch many issues. We already have .feature files covering the blocks general management, but not features about specific blocks being added to the different contexts where they can be added... | Unsolvable | 1.summary: Improved Behat tests for the activity_results block
description: The behat tests for the activity_results block can be improved by: Moving the group creation to the background Expanding behat tests to include scales
2.summary: Add Behat tests for the blog_menu block
description: The blog_menu block currently... | 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:
Brea... |
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: Gradebook performance improvements for Moodle 3.1
description: In large courses (500+ students) with a decent amount of gradebook entries, a gradebook regrade caused by adding/moving/modifying a grade item can take a really long time, often several minutes. To test this, extend the testing inst... | Unsolvable | 1.summary: Add a cache definition for grade categories
description: Login into the gradebook with different users, looking at different reports... there are always many repeated queries to grade_categories tables, they are simple database queries to grade_categories without any join with other tables, writes in grade_c... | 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:
Brea... |
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 tag communities, collections, and profiles
description: See
| Solvable | 1.summary: Auto-complete tags
description: If a user starts to type into the tag field on a collection, community, or profile, a drop-down list of similar tags should appear. See attached image for how WordPress does this.
2.summary: Decide on approach to tagging
description: Mapping out resource types: Review Phil Bar... | 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:
Brea... |
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: Change core code so it follows Moodle coding style
description: We should improve our core code, so it complies with the standard we have set in
| Unsolvable | 1.summary: Many comments that dont confirm to Moodle coding style in /backup/moodle2/restore_stepslib.php
description: If you look in /backup/moodle2/restore_stepslib.php you will see many comments that dont confirm to our coding style. See For example around line 150 there is... // manual grade items store category id... | 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:
Brea... |
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.5 upgrade
description: Moodle 3.5 is scheduled for release on Monday 14 May 2018.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.5
description:
2.summary: Upgrade learn.moodle.net to 3.5
description:
3.summary: Upgrade lang.moodle.org to 3.5
description:
4.summary: Upgrade school.demo.moodle.net to 3.5
description:
5.summary: Upgrade demo.moodle.net to 3.5
description:
6.summary: Upgrade moodle.net to 3.5
... | 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:
Brea... |
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: Font Awesome follow ups
description: There are still some visual inconsistencies with font awesome that we should collect here and fix
| Unsolvable | 1.summary: Activity modules icons should use font awesome
description: Currenlty activity modules icons look inconsistent to the other icons on the page. Also we use the file type icon when displaying page resource or folder icon when displaying the folder resource inline and they look out of place
2.summary: Changing ... | 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:
Brea... |
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 stage 2 tasks from spec
description: This is best described on the spec doc - please read it! Specification: Render library specification Forum discussion: Advisory posts in General developers forum and Theme developers forum Please do not discuss the specification here. We would ... | Unsolvable | 1.summary: Meta: Update existing documentation
description: A lot is going to change in respect to output in 2.8 via the Render library specification| All of the theme and output docs and tutorials are going to need to be updated. As pages are found that will need to be updated they will be added as subtasks here so th... | 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:
Brea... |
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: Onboarding for new iTeam member: Paul Holden
description: This issue will track the progress of Pauls onboarding with the Integration Team. The onboarding follows the iTeam onboarding course| Each section in the course represents an issue in this epic and each assignee will orga... | Unsolvable | 1.summary: Welcome, access and generalities
description: Welcome session with Paul, help him get set up for integration.
2.summary: Integration: purposes, principles, standard messages
description:
3.summary: Integration: process and schedules
description:
4.summary: Integration: Backporting issues and other bits. Re... | 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:
Brea... |
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: Add behat tests for message drawer for 3.7
description: has removed the existing behat tests for messaging so they need to be re-written and added back for the new message drawer
| Unsolvable | 1.summary: Add behat test for new message drawer to test admin settings
description: Feature In order to manage the messaging system As an admin I need to be able to enabled/disabled site-wide messaging system Scenarios Enable messaging system
2.summary: Add behat test for new message drawer to manage contacts
descript... | 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:
Brea... |
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: Analytics engine follow-up issues for Moodle 3.4
description: This epic is a continuation of which only included issues that we considered required before sending the analytics API to integration.
| Unsolvable | 1.summary: Create an analytics indicator for "completion enabled".
description: Completion enabled / disabled will have a strong effect on any of the "completion" indicators. The value of this indicator would be 0 when completion is disabled for the course and 1 when it is enabled.
2.summary: Admin page to list all ana... | 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:
Brea... |
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: Create forum grading interface
description: This is an epic to capture all of the relevant changes to support use of a Unified Grading Interface in the Forum. This issue duplicates a number of other issues but serves as a clean place for the purposes of project development.
| Solvable | 1.summary: Add rubric grading modal
description: Add a modal to show the full rubric
2.summary: Add configuration to show grading options in the Forum settings
description: Given I add a new forum And I press "Edit settings" Then I should be able to apply a rubric I believe we need to: define the FEATURE define a gradi... | 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:
Brea... |
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: Unittest and behat failures in particular DB / OS
description: Since there are quite a few reportly lately (2.8 pre-release) about unit or behat test failures in specific environments Im collecting them under one Epic so we dont create duplicates
| Unsolvable | 1.summary: Various behat failures cause by profile items in user menu
description: I guess the user menu is causing this: code (::) failed steps (::) 01. The "(//html/.//a./ = My private files or contains(normalize-space(string(.)), My private files)) or contains(./ My private files) or contains(./ My private files)) o... | 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:
Brea... |
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: Further quiz editing improvements
description: Following on from , these are the changes we hope to get into Moodle 2.9.
| Unsolvable | 1.summary: Add section headings to quiz
description: Allow the teacher to add headings to the quiz to break up the navigation At the moment, in the quiz navigation, all the questions are shown in one big block. That gets pretty unmanagable for big quizzes. We want to provide a way for teacher to add section headings to... | 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:
Brea... |
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: Define database models
description: See issues included in this epic.
| Solvable | 1.summary: Specify model and choose engine for search index (incl. OER)
description: WIP
2.summary: Specify model for app
description: WIP
3.summary: Specify model for repository
description: WIP
| 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:
Brea... |
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 mod_forum to add additional functionality, and improve accessibility and performance
description: Moodlerooms have produced "Advanced Forum" (it originally started at Humboldt State Uni) It extends current Moodle forum code to prove some of the most-requested forum features such a: - Ano... | Unsolvable | 1.summary: Forum: Per-discussion subscription
description: I am finding that my inbox is absolutely flooded with unwanted moodle mails off the forum script. This is very annoying and I know it will similarly annoy my users. In fact it will put them off the system. The problem arises because unlike other discussion boar... | 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:
Brea... |
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: Behat 3.2.x upgrade issues to be fixed
description: Some of the issues have been fixed in Behat and not yet released. This epic is to keep track of all related issues which need attention after behat is upgraded.
| Unsolvable | 1.summary: Behat, support relative dates.
description: Now and then I find relative dates necessary in my behat tests. To start with I worked around this issue by creating custom steps. However, a much better way is to use the translation feature in behat. This way you can simply do things like: code I should see "the ... | 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:
Brea... |
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.3
description: In 3.3 we can remove functionality that was deprecated in 2.9 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 the... | Unsolvable | 1.summary: Final deprecations in core_cache
description: We need to remove the following in core_cache that were deprecated in 2.9: cache/classes/definition.php cache_definition::datasourceaggregate| cache/tests/fixtures/lib.php: cache_config_phpunittest| See
2.summary: Deprecate behat step: I go to "PATH" in the cours... | 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:
Brea... |
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: Use hideIf in core forms
description: There are a number of core forms that could benefit from the use of the new hideIf functionality (). In this ticket I will propose a number of places this could be implemented + attach proposed patches to do this.
| Unsolvable | 1.summary: LTI modedit.php should not display disabled form elements
description: The LTI form can, depending on how its been set up, show a whole bunch of disabled elements. I cant see any reason for displaying these. If they are not editable then dont display them. Particular confusion is caused by the Select 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:
Brea... |
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 accessibility issues
description: This issue serves as the collection of accessibility issues affecting Moodle in general.
| Unsolvable | 1.summary: Adding title attribute to links for accessibility goes against recommendations in WCAG and is rarely useful.
description: Needs confirming in Jaws. Found in testing . A link like this Dan the man appears to screen readers as: link Dan the man The extra information provided by the title is not read out. We sh... | 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:
Brea... |
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: H5P for Moodle 3.9
description: Further development of the H5P integration| Integration of H5P content types with Moodle gradebook and activity completion. Improved integration of H5P content type selection in Moodles activity chooser.
| Unsolvable | 1.summary: Improve admin UI to manage H5P libraries and give information about H5P tools status
description: Improve admin UI for H5P management: Add icons to installed content types list in Site administration > H5P > Manage H5P content types Add a new page to show the admins information about the status of different ... | 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:
Brea... |
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.1 upgrade
description: Moodle 3.3.1 is scheduled for release on Monday 10 July 2017.
| Unsolvable | 1.summary: Upgrade moodle.org to 3.3.1
description:
2.summary: Upgrade learn.moodle.net to 3.3.1
description:
3.summary: Upgrade lang.moodle.org to 3.3.1
description:
4.summary: Upgrade school.demo.moodle.net to 3.3.1
description:
5.summary: Upgrade demo.moodle.net to 3.3.1
description:
6.summary: Upgrade dev.mood... | 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:
Brea... |
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: Improvements to CSS and themes
description: This epic is a collection of improvements raised in the discussion and dev docs here: and here: The overall goal is to improve our CSS and provide better guidelines for developers.
| Solvable | 1.summary: Add to docs page the relationship between base, bootstrapbase and clean themes.
description: We need a clear policy on where to apply fixes, mobile enhancements, responsive elements and more. If we add a layer of mobile enhancements to bootstrapbase, we are adding more code that themers may not want (especia... | 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:
Brea... |
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 improvements
description: Some changes we would like to see done for 3.3.
| Unsolvable | 1.summary: A site configuration option to limit contacts search and messaging based on the courses you are in
description: A site configuration option to limit contacts search and messaging based on the courses you are in - if you are a student
2.summary: Send messages to members in groups
description: A function for s... | 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:
Brea... |
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: Make Atto Editor more accessible
description: This epic covers deliverable elements of the MUA "Make Atto Editor more accessible" 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 brin... | Unsolvable | 1.summary: Use aria-expanded to indicate the state of the "Show/hide advanced buttons" button
description: we should add the aria-expanded attribute to the "Show/hide advanced buttons" button. Maybe aria-pressed="true" as well.
2.summary: Move the screen reader helper button to the first row
description: Move the scree... | 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:
Brea... |
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.0)
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 ... | Unsolvable | 1.summary: Upgrade FPDI library in assignfeedback_editpdf to 1.5.4 for Moodle 3.0 release
description: Library FPDI Current version 1.4.4 Latest version 1.5.2 Make sure to update files: - mod/assign/feedback/editpdf/fpdi (library itself) - mod/assign/feedback/editpdf/thirdpartylibs.xml (indicate the current version) - ... | 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:
Brea... |
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 and Question bank in Moodle 4.0
description: Introduction The Quiz and Question in Moodle 4.0 project aims to improve behaviour and structure around questions and the question bank and probably some more. This project has been initiated by tkorner, lucaboesch and timhunt and is now in a pr... | Unsolvable | 1.summary: Create new plugin type - Qbank
description: Currently all Question bank features are "hard coded" in Moodle core and are not very extensible. This issue will introduce a new "Question bank" plugin type, with the `qbank_` prefix. It will also refactor core code to allow provide a straightforward interface to ... | 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:
Brea... |
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 Tour/Walkthough/Instructional overlays for first time user on page
description: There are quite a number of Tour/walkthough frameworks which can be used out-of-box to introduce new users to Moodle pages. Currently it is hard of non-computer savy user to start using Moodle and being LMS M... | Solvable | 1.summary: Moodle Tour/Walkthough/Instructional overlays for first time user on page (User tours)
description: There are quite a number of Tour/walkthough frameworks which can be used out-of-box to introduce new users to Moodle pages. Currently it is hard of non-computer savy user to start using Moodle and being LMS Mo... | 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:
Brea... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.