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

Show graph for issue dependencies #9419

New Issue
Closed
opened 2025-11-02 08:38:12 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2025-11-02 08:38:12 -06:00
Owner
Copy Link

Originally created by @Zocker1999NET on GitHub (Aug 17, 2022).

Feature Description

It would be great if Gitea could show a graph with an issue's dependencies. This would make more visible if:

  • any sub tasks / dependency tasks are still to be done and
  • any parent tasks / dependent tasks exists and which they are.

It would also be great, if this could work recursively (see example screenshot below), however that is not required for a first implementation. Just making dependent tasks (optionally) more visible would be helpful as well.

Screenshots

An extreme example is Phabricator, which does show a tree with recursive resolution:
image
(Source: https://secure.phabricator.com/T7577)

Originally created by @Zocker1999NET on GitHub (Aug 17, 2022). ### Feature Description It would be great if Gitea could show a graph with an issue's dependencies. This would make more visible if: - any sub tasks / dependency tasks are still to be done and - any parent tasks / dependent tasks exists and which they are. It would also be great, if this could work recursively (see example screenshot below), however that is not required for a first implementation. Just making dependent tasks (optionally) more visible would be helpful as well. ### Screenshots An extreme example is Phabricator, which does show a tree with recursive resolution: ![image](https://user-images.githubusercontent.com/1645646/185253641-ef7d8984-6536-44fe-9eaa-0b7989ce38d5.png) (Source: https://secure.phabricator.com/T7577)
GiteaMirror added the type/proposaltype/feature labels 2025-11-02 08:38:12 -06:00
GiteaMirror commented 2025-11-02 08:38:13 -06:00
Author
Owner
Copy Link

@Zocker1999NET commented on GitHub (Aug 17, 2022):

Sorry for the duplicate, found #8794 after giving this one a better title and searching for it.

@Zocker1999NET commented on GitHub (Aug 17, 2022): Sorry for the duplicate, found #8794 after giving this one a better title and searching for it.
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 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#9419
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?