kosmos/gitea.kosmos.org
Archived
8
1 Fork 0
Code Issues Releases Activity

[Low Priority] Pre populating issue title fails #47

New Issue
Closed
opened 2020-11-15 05:55:55 +00:00 by melvin · 1 comment
melvin commented 2020-11-15 05:55:55 +00:00
Copy link
Copy source

Gitea allows issues to be pre populated using items on the query string

Additionally, the New Issue page URL can be suffixed with ?title=Issue+Title&body=Issue+Text and the form will be populated with those strings. Those strings will be used instead of the template if there is one.

https://docs.gitea.io/en-us/issue-pull-request-templates/

Trying this out here:

https://gitea.kosmos.org/kosmos/gitea.kosmos.org/issues/new?title=foo&body=bar

It populates the body correcly, but not the title

I have replicated this locally and it may be an upstream bug

Low priority: tho it could be helpful in automating ways to create issues from client side apps

Gitea allows issues to be pre populated using items on the query string > Additionally, the New Issue page URL can be suffixed with ?title=Issue+Title&body=Issue+Text and the form will be populated with those strings. Those strings will be used instead of the template if there is one. https://docs.gitea.io/en-us/issue-pull-request-templates/ Trying this out here: https://gitea.kosmos.org/kosmos/gitea.kosmos.org/issues/new?title=foo&body=bar It populates the body correcly, but not the title I have replicated this locally and it may be an upstream bug Low priority: tho it could be helpful in automating ways to create issues from client side apps
raucao commented 2020-11-15 11:53:17 +00:00
Owner
Copy link
Copy source

You can also use the API for creating issues:

https://gitea.kosmos.org/api/swagger#/issue/issueCreateIssue

I'm not sure how useful it is to keep upstream bugs open as issues in our own repos, unless it's something you're planning to actually work on. I would rather close this and suggest to open an issue on https://github.com/go-gitea/gitea/issues/.

You can also use the API for creating issues: https://gitea.kosmos.org/api/swagger#/issue/issueCreateIssue I'm not sure how useful it is to keep upstream bugs open as issues in our own repos, unless it's something you're planning to actually work on. I would rather close this and suggest to open an issue on https://github.com/go-gitea/gitea/issues/.
👍 1
This repo is archived. You cannot comment on issues.
No Branch/Tag Specified
Labels
Clear labels
bug
Something is not working
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 ops
question
Looking for an answer
 security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
bug
Something is not working
 design
Graphic/visual design
 dev environment
Config, builds, CI, deployment, etc.
 docs
Documentation
 duplicate
This issue or pull request already exists
 enhancement
Improving existing functionality
 feature
New functionality
 good first issue
Dive in, and start contributing
 idea
Something to consider
 invalid
Not a bug
 kredits-1
Small contribution
 kredits-2
Medium contribution
 kredits-3
Large contribution
 on hold
Currently not actionable
 ops
Manual IT ops activities
 question
Looking for an answer
 security
All your base are belong to us
 ui/ux
User interface, process design, etc.
 wontfix
This won't be fixed
release
major
release
minor
release
patch
No labels
Milestone
No items
No Milestone
Assignees
Clear assignees
bkero (bkero) bumi (bumi) fsmanuel (fsmanuel) galfert (galfert) greg (Greg) hueso (hueso) raucao (Râu Cao) slvrbckt (Nick Jennings)
No Assignees
2 Participants
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: kosmos/gitea.kosmos.org#47