Pullrequest dependencies are disabled when internal issue tracker is disabled #2893

New Issue

GiteaMirror · 2025-11-02T04:52:54-06:00

GiteaMirror commented

2025-11-02 04:52:54 -06:00

Originally created by @markusamshove on GitHub (Feb 11, 2019).

Gitea version (or commit ref): master

Description

When selecting an external issue tracker in the repository settings (see 1st screenshot), it is no longer possible to add dependencies between pull requests.

In our current workflow, we do use an external issue tracker for all of our repositories.

However, we're leveraging PRs and would love to be able to have dependencies between PRs (which does work when internal issue tracker is enabled).

Screenshots

Originally created by @markusamshove on GitHub (Feb 11, 2019). - Gitea version (or commit ref): master ## Description When selecting an external issue tracker in the repository settings (see 1st screenshot), it is no longer possible to add dependencies between pull requests. In our current workflow, we do use an external issue tracker for all of our repositories. However, we're leveraging PRs and would love to be able to have dependencies between PRs (which does work when internal issue tracker is enabled). ## Screenshots ![grafik](https://user-images.githubusercontent.com/2401875/52583765-b61a5e00-2e30-11e9-9118-fdc6708b3677.png)

GiteaMirror added the issue/confirmed type/bug labels 2025-11-02 04:52:54 -06:00

GiteaMirror closed this issue

2025-11-02 04:52:55 -06:00

GiteaMirror commented

2025-11-02 04:52:55 -06:00

@markusamshove commented on GitHub (Feb 13, 2019):

I tried to have a go on this, but I'm kinda lost on how to implement this.

My first try was to pull out the option from Enable Repository Issue Tracker as an additional option, which can be enabled when either PRs or Issues are enabled.

However, the name issue dependencies and the option EnableDependencies in IssueConfig wouldn't make sense anymore.
Also, the DB table seems to be issue_dependencies, so when trying to do it clean I have to change the database, translation keys etc..

Is there another approach I could to?
Is an additional option in for pull request config, to have 2 options, a better idea?

I think this needs a bit of design thought from the Gitea side, as this would be my first PR and got kinda huge :-)

@markusamshove commented on GitHub (Feb 13, 2019): I tried to have a go on this, but I'm kinda lost on how to implement this. My first try was to pull out the option from ` Enable Repository Issue Tracker` as an additional option, which can be enabled when either PRs or Issues are enabled. However, the name `issue dependencies` and the option `EnableDependencies` in `IssueConfig` wouldn't make sense anymore. Also, the DB table seems to be `issue_dependencies`, so when trying to do it clean I have to change the database, translation keys etc.. Is there another approach I could to? Is an additional option in for pull request config, to have 2 options, a better idea? I think this needs a bit of design thought from the Gitea side, as this would be my first PR and got kinda huge :-)

GiteaMirror commented

2025-11-02 04:52:55 -06:00

@stale[bot] commented on GitHub (Apr 14, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Apr 14, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 04:52:56 -06:00

@stale[bot] commented on GitHub (Apr 29, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Apr 29, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 04:52:56 -06:00

@markusamshove commented on GitHub (Dec 12, 2019):

Still relevant :-)

@markusamshove commented on GitHub (Dec 12, 2019): Still relevant :-)

GiteaMirror commented

2025-11-02 04:52:56 -06:00