| 1 |
efrain |
1 |
name: Feature request
|
|
|
2 |
description: Share your ideas for this project.
|
|
|
3 |
title: "Feature Request: "
|
|
|
4 |
body:
|
|
|
5 |
- type: markdown
|
|
|
6 |
attributes:
|
|
|
7 |
value: |
|
|
|
8 |
## Thanks for taking the time to share your ideas and suggestions.
|
|
|
9 |
We love hearing ideas and suggestions from people who use our plugins.<br>
|
|
|
10 |
***In a hurry for this new feature?*** Contact us directly for premium development and support services at [TNG Consulting Inc.](https://www.tngconsulting.ca/contact).
|
|
|
11 |
- type: checkboxes
|
|
|
12 |
id: prerequisites
|
|
|
13 |
attributes:
|
|
|
14 |
label: Prerequisites
|
|
|
15 |
description: Please answer the following questions before submitting a feature request.
|
|
|
16 |
options:
|
|
|
17 |
- label: I am requesting the new feature to the correct repository.
|
|
|
18 |
required: true
|
|
|
19 |
- label: I checked the latest version on GitHub and the [README.md](../blob/master/README.md) documentation to ensure that this functionality does not already exist.
|
|
|
20 |
required: true
|
|
|
21 |
- label: I searched to make sure that this feature has not already been requested.
|
|
|
22 |
required: true
|
|
|
23 |
- label: I have, or I know someone who has, the ability and willingness to test the new feature on a Moodle LMS-based site.
|
|
|
24 |
- label: I agree to submit one feature request per issue ticket (do not submit multiple requests in one issue ticket).
|
|
|
25 |
required: true
|
|
|
26 |
- label: I understand that development and support is provided by volunteer(s) and that all final implementation decisions are up TNG Consulting Inc.
|
|
|
27 |
required: true
|
|
|
28 |
- type: textarea
|
|
|
29 |
attributes:
|
|
|
30 |
label: Feature Request - The User Story
|
|
|
31 |
description: Provide a clear and concise description of the feature are you requesting or idea that you have. Be sure include one or more **real-life** examples of how you **will** use the new feature. Do not make up a story just because it is easier. We only implement new features if we understand your goal and it makes sense to us.
|
|
|
32 |
placeholder: e.g. As a [Moodle role], I need/want to [...], so that [...].
|
|
|
33 |
validations:
|
|
|
34 |
required: true
|
|
|
35 |
- type: textarea
|
|
|
36 |
attributes:
|
|
|
37 |
label: Screenshots / Mock-ups
|
|
|
38 |
description: Add any screenshots, videos or documentation which can help us visualize your vision.
|
|
|
39 |
- type: textarea
|
|
|
40 |
attributes:
|
|
|
41 |
label: Alterative you have considered
|
|
|
42 |
description: Provide a clear and concise description of any alternative solutions or features you've considered. If you have seen a similar feature in another plugin, please provide us with a link to it.
|
|
|
43 |
- type: textarea
|
|
|
44 |
attributes:
|
|
|
45 |
label: Additional information
|
|
|
46 |
- type: dropdown
|
|
|
47 |
attributes:
|
|
|
48 |
label: Planning on submitting a solution in a pull request (PR)?
|
|
|
49 |
description: If so, we look forward to working with you to integrate your work. Feature requests with a provided solution may be integrated sooner. Be sure to read the <a href="../blob/master/CONTRIBUTING.md" target="_blank">[CONTRIBUTING]</a> guidelines.
|
|
|
50 |
options:
|
|
|
51 |
- "Yes"
|
|
|
52 |
- "No"
|
|
|
53 |
- "Maybe"
|
|
|
54 |
validations:
|
|
|
55 |
required: true
|
|
|
56 |
- type: checkboxes
|
|
|
57 |
attributes:
|
|
|
58 |
label: Code of Conduct
|
|
|
59 |
options:
|
|
|
60 |
- label: I have read and agree to the project's <a href="../blob/master/CODE_OF_CONDUCT.md" target="_blank">code of conduct</a>.
|
|
|
61 |
required: true
|