Current Gitea version incorrectly displays issue template #79

New Issue

Alaska · 2024-04-15T08:36:09+02:00

Alaska commented

2024-04-15 08:36:09 +02:00

As part of the project in #78, it was decided that the triaging team may update the bug reporting infrastructure in multiple parts (This was discussed in a module meeting).

Update the Gitea issue template for the Blender repository to be more informative and/or laid out in a better way.
Then start working on something more custom if necessary.

One of the issues we have at the moment is that the version of Gitea used by the Blender foundation does not use the Gitea issue template properly in some situations.

According to https://docs.gitea.com/next/usage/issue-pull-request-templates some parts of the issue template can be restricted to just the reporting form, both the reporting form and the report, or just the report. However the version of Gitea used by the Blender foundation does not seem to do this.

Testing the same test case in Gitea on https://try.gitea.io/ does work. And they are using a more up to date version of Gitea. This implies the Blender foundation just needs to update their own version of Gitea, but I couldn't find the exact version in which this issue was fixed to tell you the minimum version that needs to be updated too.

Steps to reproduce this issue:

Create a issue template in a repository that makes use of the "restricting" feature. I've created one here: https://projects.blender.org/Alaska/bug-report-testing/src/branch/main/.gitea/issue_template/restriction-test.yaml
Upload issue template to a respository on the Blender foundation Gitea and test it. You can test the template here: https://projects.blender.org/Alaska/bug-report-testing/issues/new?template=.gitea%2fissue_template%2frestriction-test.yaml
Notice that the restrictions on which checkboxes should be visible and when is not working.

	Report form	Completed report
Result from Blender Gitea
Expected result

As part of the project in https://projects.blender.org/infrastructure/blender-projects-platform/issues/78, it was decided that the triaging team may update the bug reporting infrastructure in multiple parts (This was discussed in a module meeting). 1. Update the Gitea issue template for the Blender repository to be more informative and/or laid out in a better way. 2. Then start working on something more custom if necessary. One of the issues we have at the moment is that the version of Gitea used by the Blender foundation does not use the Gitea issue template properly in some situations. According to https://docs.gitea.com/next/usage/issue-pull-request-templates some parts of the issue template can be restricted to just the reporting form, both the reporting form and the report, or just the report. However the version of Gitea used by the Blender foundation does not seem to do this. Testing the same test case in Gitea on https://try.gitea.io/ does work. And they are using a more up to date version of Gitea. This implies the Blender foundation just needs to update their own version of Gitea, but I couldn't find the exact version in which this issue was fixed to tell you the minimum version that needs to be updated too. --- Steps to reproduce this issue: 1. Create a issue template in a repository that makes use of the "restricting" feature. I've created one here: https://projects.blender.org/Alaska/bug-report-testing/src/branch/main/.gitea/issue_template/restriction-test.yaml 2. Upload issue template to a respository on the Blender foundation Gitea and test it. You can test the template here: https://projects.blender.org/Alaska/bug-report-testing/issues/new?template=.gitea%2fissue_template%2frestriction-test.yaml 3. Notice that the restrictions on which checkboxes should be visible and when is not working. ||Report form|Completed report| |-|-|-| |Result from Blender Gitea|![Actual form.png](/attachments/2d467868-9759-43f5-89fa-0fb60f8bff62)|![Actual report.png](/attachments/ee084fcb-2116-4d78-b00d-d68175129f09)| |Expected result|![Expected form.png](/attachments/2dffc09d-6087-4f80-8506-cbd82204ee3a)|![Expected report.png](/attachments/4d98d7db-5acb-4a27-9691-95f7c0695b4c)|

Actual form.png

61 KiB

Expected form.png

46 KiB

Expected report.png

58 KiB

Actual report.png

68 KiB

Alaska commented

2024-04-15 08:38:00 +02:00

This report is just to inform you of a issue with the Blender foundation Gitea that appears to be fixed upstream. Maybe the report can remain open until the Blender foundation has updated their version of Gitea with the fix.

Alaska commented

2024-04-15 09:23:31 +02:00

Upon further investigation, this is not a bug with the Blender foundation Gitea that needs to be resolved with a update. It's actually a feature that's available in the upcoming Gitea 1.22 release.

So instead of being a "bug report", it's a "feature request". I will close this issue and continue the discussion on #78

Upon further investigation, this is not a bug with the Blender foundation Gitea that needs to be resolved with a update. It's actually a feature that's available in the upcoming Gitea 1.22 release. So instead of being a "bug report", it's a "feature request". I will close this issue and continue the discussion on #78

Alaska closed this issue

2024-04-15 09:23:31 +02:00

Sign in to join this conversation.