github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-05-22 05:15:42 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Support issue forms #7549

New Issue
Closed
opened 2025-11-02 07:29:31 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 07:29:31 -06:00
Owner
Copy Link

Originally created by @delvh on GitHub (Jul 6, 2021).

  • Gitea version (or commit ref): 1.15.0+dev-541-g5bb97a12d

Description

As shown in #16349, GitHub now supports issue forms for a unified issue creation behavior.
It would be great and pretty user friendly, if Gitea would support the same.
Syntactically, it would be good, if a GitHub-similar syntax would be chosen (see the example currently integrated into Gitea itself or the GitHub syntax documentation), with the same structure as GitHub as well.

Included features

  • Issue Builder with basically all components that GitHub supports as well
  • config.yml in the template folder to change the configuration of the issue and PR templates
  • Automated Issue template updating when the template folder has been updated

Potential to be better than GitHub (Later on)

  • Localized text (i.e. so that comments can be displayed in the native language with English as fallback - i.e. by having a locale_<Locale>.ini in the template folder)
  • Ability to refer to a mail account in the clickable_links: section of the config.yml
  • Do not show optional columns where no text has been entered

Predicted Problems

  • Feature will be pretty big (I estimate ~2000-4000 lines of code)
  • How to handle issue/ PR creation over API (especially when blank_issues_enabled: false is part of the config.yml)

Screenshots

image
Current issue creation form displayed on GitHub when creating a new bug report for Gitea

image
Current representation for an issue created using issue forms

Originally created by @delvh on GitHub (Jul 6, 2021). - Gitea version (or commit ref): 1.15.0+dev-541-g5bb97a12d ## Description As shown in #16349, GitHub now supports issue forms for a unified issue creation behavior. It would be great and pretty user friendly, if Gitea would support the same. Syntactically, it would be good, if a GitHub-similar syntax would be chosen (see [the example currently integrated into Gitea itself](https://github.com/go-gitea/gitea/blob/main/.github/ISSUE_TEMPLATE/) or [the GitHub syntax documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms)), with the same structure as GitHub as well. ## Included features - Issue Builder with basically all components that GitHub supports as well - `config.yml` in the template folder to change the configuration of the issue and PR templates - Automated Issue template updating when the template folder has been updated ## Potential to be better than GitHub (Later on) - Localized text (i.e. so that comments can be displayed in the native language with English as fallback - i.e. by having a `locale_<Locale>.ini` in the template folder) - Ability to refer to a mail account in the `clickable_links:` section of the `config.yml` - Do not show optional columns where no text has been entered ## Predicted Problems - Feature will be pretty big (I estimate `~2000-4000` lines of code) - How to handle issue/ PR creation over API (especially when ` blank_issues_enabled: false` is part of the `config.yml`) ## Screenshots ![image](https://user-images.githubusercontent.com/51889757/124616072-154ff180-de76-11eb-8aaa-7fa5a2d231bf.png) Current issue creation form displayed on GitHub when creating a new bug report for Gitea ![image](https://user-images.githubusercontent.com/51889757/124616315-43cdcc80-de76-11eb-9ecb-a0068fb91ded.png) Current representation for an issue created using issue forms
GiteaMirror added the topic/issuestype/featuretype/proposal labels 2025-11-02 07:29:31 -06:00
GiteaMirror commented 2025-11-02 07:29:32 -06:00
Author
Owner
Copy Link

@delvh commented on GitHub (Aug 12, 2022):

Superseded by #20232.

@delvh commented on GitHub (Aug 12, 2022): Superseded by #20232.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label topic/issues type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#7549
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?