Please, create one MR for each new feature, don't submit multiple new features at once, unless they are very tied.

## What does it do?

Please, describe in a few words the new feature

## Is there a related issue?

## What part of MyPads are modified?

- [ ] backend
- [ ] frontend

## Check list

- [ ] did you [squash](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) your commits?
- [ ] did you respect the [coding guidelines](https://framagit.org/framasoft/Etherpad/ep_mypads/wikis/coding-style)?
- [ ] did you add new translations key?
- [ ] did you add new tests?
- [ ] did you run `npm run lint`?
- [ ] if you modified the frontend, did you run `npm run frontend:build`?

/label ~feature

Please, create one MR for each new feature, don't submit multiple new features at once, unless they are very tied.

Note: MR should be proposed on `development` branch, not on `master` branch.

## What does it do?

Please, describe in a few words the new feature

## Is there a related issue?

## What part of MyPads are modified?

- [ ] backend
- [ ] frontend

## Check list

- [ ] did you [squash](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html) your commits?
- [ ] did you respect the [coding guidelines](https://framagit.org/framasoft/Etherpad/ep_mypads/wikis/coding-style)?
- [ ] did you add new translations key?
- [ ] did you add new tests?
- [ ] did you run `npm run lint`?
- [ ] if you modified the frontend, did you run `npm run frontend:build`?

/label ~feature

Update feature MR template: ask for MR on dev branch, not master
Update feature MR template: ask for MR on dev branch, not master
