Reformat the Template

[flixx]

The template is not optimal yet, because it contains a lot of unnecessary information and does not give space to define important information.

Suggestions:

• Include the type(s) of the PR in the title
• Don't list all the non-applying items. All the options that are not ticked are just wasting space in the PR.
• Rename "Other information" to "Description" and move it to the top of the template. A free-description is the most important thing for me when I write PRs.
• Give the possibility to define custom options under "Review and Merge". E.g. "Merge after PO approves"

[flixx]

Example:

The most important information here is at the bottom.

Better would be:

Refactor[B3-3867] - Refactor of project comments api

This is more or less just moving files around, so we won't have big bloated views with multiple views inside, the same is applied here to serializers.

Testing procedure

Case 1

1. Just test the commenting system in yoda

Case 2

1. You can also just run the tests

Does this PR introduce a breaking change?
no

Review and Merge
Last approver merges after > 51% of the reviewers approved

Changelog
Note
• refactoring of project comments API structure to match standards, closes #3867

[igeligel]

Normally the best case is that we just copy the description out of JIRA issue in the pull request. For now, we can add a description field and replace Other Information with that.

I would prioritize the topics like this:

1. Title
2. Description
3. Type
4. Breaking
5. Testing Procedure
6. (Other information)
7. Merger
8. Changelog

I guess i can also use some kind of analytics system to see what of the features are the most used and put them to the beginning since these are the most important then.