|
| 1 | +## Description |
| 2 | +_Description of the feature_ |
| 3 | + |
| 4 | +## Functional solution |
| 5 | +_Add task list of functionality to implement_ |
| 6 | + - [ ] functionality 1 |
| 7 | + - [ ] functionality 2 |
| 8 | + |
| 9 | +## Technical solution |
| 10 | +_Add task list of relevant technical modification_ |
| 11 | + - [ ] modification 1 |
| 12 | + - [ ] modification 2 |
| 13 | + |
| 14 | +## Security and Privacy |
| 15 | +> Risk level MUST be systematically assessed before designing a change. Actions to handle risk and approval depend on the risk level: |
| 16 | +>- None/low: no or low impact and probability considered. If the risk is considered low, actions to handle the risk may be defined. No approval required. |
| 17 | +>- Medium: either significant impact or significant probability considered. Actions must be defined in the sections below and approved/completed by a team lead before implementing the change. |
| 18 | +>- High: significant impact AND probability considered. Actions must be defined in the section below and approved/completed by CTO or CISO before implementing the change. |
| 19 | +
|
| 20 | +| Risk level | None | Low | Med. | High | |
| 21 | +|------------|----------|----------|--------|-----------------------| |
| 22 | +| Rating | | | | :heavy_check_mark: | |
| 23 | + |
| 24 | +### Actions to handle risk |
| 25 | +_to be filled by actions of any kind if level >= low_ |
| 26 | + |
| 27 | +## Personal data |
| 28 | +_Anything concerning user personal data that should be discussed with legal team_ |
| 29 | + |
| 30 | +> This section should **always** be updated. In case there is nothing to say, simply add "nothing relevant" or "nothing identified" |
| 31 | +
|
| 32 | +## Tests |
| 33 | +_In addition to the classic unit and functional tests, additional tests that should be performed either automatic or manual_ |
| 34 | + |
| 35 | +> This section should **always** be updated. In case there is nothing to say, simply add "nothing relevant" or "nothing identified" |
| 36 | +
|
| 37 | +## Impacts |
| 38 | +_List of impacted routes or functionality_ |
| 39 | + |
| 40 | +## Estimation |
| 41 | +x jH |
| 42 | + |
| 43 | +## Questions |
| 44 | +- Question |
| 45 | +> answer |
| 46 | +
|
| 47 | +## DoD |
| 48 | +_In front of each item write one of those: N/A, Done, link to infra issue, or the modification made_ |
| 49 | + |
| 50 | +| Item | | |
| 51 | +|-------------------------------------------------------------------------------------------------------------------------------------------|:---:| |
| 52 | +| New environment variables added in settings files and issue created in [infra board](https://git.clacos.ninja/infra/infradev/-/boards) | | |
| 53 | +| New command and consumer described in [Readme.md]() and issue created in [infra board](https://git.clacos.ninja/infra/infradev/-/boards) | | |
| 54 | +| Feature tested locally | | |
| 55 | +| Merge request created from feature to develop | | |
| 56 | + |
| 57 | + |
| 58 | +/label ~Feature |
0 commit comments