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

Issue tracker url doen not support jira #6406

New Issue
Closed
opened 2025-11-02 06:54:57 -06:00 by GiteaMirror · 4 comments
GiteaMirror commented 2025-11-02 06:54:57 -06:00
Owner
Copy Link

Originally created by @ffbh123456 on GitHub (Nov 29, 2020).

  • Gitea version (or commit ref): docker image id 9058d7d9f1a1
  • Git version: 2.28.0
  • Operating system: macOS 11.0.1
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No

Description

My issue is recorded in the Jira system. When I set up the issue tracker of gitea, it reported an error saying that the URL is illegal, but I don’t think gitea needs to have this URL verification, because gitea just uses a new page to open the URL, I hope this URL can support any issue management system

Screenshots

image
截屏2020-11-29 11 57 09

Originally created by @ffbh123456 on GitHub (Nov 29, 2020). - Gitea version (or commit ref): docker image id 9058d7d9f1a1 - Git version: 2.28.0 - Operating system: macOS 11.0.1 <!-- Please include information on whether you built gitea yourself, used one of our downloads or are using some other package --> <!-- Please also tell us how you are running gitea, e.g. if it is being run from docker, a command-line, systemd etc. ---> <!-- If you are using a package or systemd tell us what distribution you are using --> - Database (use `[x]`): - [ ] PostgreSQL - [x] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [x] No ## Description My issue is recorded in the Jira system. When I set up the issue tracker of gitea, it reported an error saying that the URL is illegal, but I don’t think gitea needs to have this URL verification, because gitea just uses a new page to open the URL, I hope this URL can support any issue management system ## Screenshots <!-- **If this issue involves the Web Interface, please include a screenshot** --> ![image](https://user-images.githubusercontent.com/20750357/100532995-5de96180-323a-11eb-8f2c-b4ae99a17203.png) <img width="1190" alt="截屏2020-11-29 11 57 09" src="https://user-images.githubusercontent.com/20750357/100533002-722d5e80-323a-11eb-8b5a-4d2afbd975ce.png">
GiteaMirror commented 2025-11-02 06:54:58 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Nov 29, 2020):

When providing Gitea version please use the output of gitea --version as docker image IDs aren't easily determined.

@techknowlogick commented on GitHub (Nov 29, 2020): When providing Gitea version please use the output of `gitea --version` as docker image IDs aren't easily determined.
GiteaMirror commented 2025-11-02 06:54:58 -06:00
Author
Owner
Copy Link

@ffbh123456 commented on GitHub (Nov 29, 2020):

@techknowlogick
Hi,
Gitea version 1.14.0+dev-265-g742e21aeb built with GNU Make 4.3, go1.15.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify
But I think the above problem exists in most gitea versions

@ffbh123456 commented on GitHub (Nov 29, 2020): @techknowlogick Hi, Gitea version 1.14.0+dev-265-g742e21aeb built with GNU Make 4.3, go1.15.5 : bindata, timetzdata, sqlite, sqlite_unlock_notify But I think the above problem exists in most gitea versions
GiteaMirror commented 2025-11-02 06:54:58 -06:00
Author
Owner
Copy Link

@techknowlogick commented on GitHub (Nov 29, 2020):

Per this code de6ef14d04/modules/validation/helpers.go (L72) this is expected for security reasons.

@techknowlogick commented on GitHub (Nov 29, 2020): Per this code https://github.com/go-gitea/gitea/blob/de6ef14d04c36272143ad822bf5903f84c7f238b/modules/validation/helpers.go#L72 this is expected for security reasons.
GiteaMirror commented 2025-11-02 06:54:58 -06:00
Author
Owner
Copy Link

@ffbh123456 commented on GitHub (Nov 29, 2020):

@techknowlogick
I deploy both jira and gitea on my personal computer, I don’t understand why localhost has security issues

@ffbh123456 commented on GitHub (Nov 29, 2020): @techknowlogick I deploy both jira and gitea on my personal computer, I don’t understand why localhost has security issues
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
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#6406
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?