Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't use issue templates on 1.20.4 #27060

Closed
colejohnson66 opened this issue Sep 13, 2023 · 2 comments · Fixed by #27061
Closed

Can't use issue templates on 1.20.4 #27060

colejohnson66 opened this issue Sep 13, 2023 · 2 comments · Fixed by #27061
Labels
Milestone

Comments

@colejohnson66
Copy link

colejohnson66 commented Sep 13, 2023

Description

Issue templates do not work on 1.20.4. When creating a new issue, we're taken to the template picker. However, picking a template does not work; It puts the template path in the URL, but then reloads the template picker. We downgraded back to 1.20.3, and it started working again.

The end of the URL the button links to hasn't changed; Both versions link to /<org>/<repo>/issues/new?template=<template-path>. However, when attempting to request that URL, Gitea responds with a 303 See Other to /<org>/<repo>/issues/new/choose?template=<template-path>.

Gitea Version

1.20.4

Can you reproduce the bug on the Gitea demo site?

Have not tried

Log Gist

No response

Screenshots

No response

Git Version

2.41.0.windows-3

Operating System

Windows Server 2022

How are you running Gitea?

As a Windows service. To upgrade/downgrade, we stop the service, overwrite the executable, and restart it.

Database

MySQL/MariaDB

@wxiaoguang
Copy link
Contributor

Related to #26813 @JakobDev

I would prefer not to limit it so strictly, give end users the freedom, or at least give repo members the freedom.

@JakobDev
Copy link
Contributor

Sorry I should really have tested this better

I would prefer not to limit it so strictly, give end users the freedom, or at least give repo members the freedom.

Blank Issues are enabled by default. If the repo owner wants to disable it, it's their choice. For allowing it only for repo members, we need finer settings.

@lunny lunny added this to the 1.20.5 milestone Sep 14, 2023
silverwind added a commit that referenced this issue Sep 14, 2023
Fixes #27060

---------

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: delvh <dev.lh@web.de>
GiteaBot pushed a commit to GiteaBot/gitea that referenced this issue Sep 14, 2023
Fixes go-gitea#27060

---------

Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: delvh <dev.lh@web.de>
silverwind added a commit that referenced this issue Sep 14, 2023
Backport #27061 by @JakobDev

Fixes #27060

Co-authored-by: JakobDev <jakobdev@gmx.de>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: delvh <dev.lh@web.de>
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 30, 2023
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
…o-gitea#27082)

Backport go-gitea#27061 by @JakobDev

Fixes go-gitea#27060

Co-authored-by: JakobDev <jakobdev@gmx.de>
Co-authored-by: silverwind <me@silverwind.io>
Co-authored-by: delvh <dev.lh@web.de>
(cherry picked from commit b139234)
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants