The "Add dependency" selector shows issues non related to the current account/organization #244

manheraz commented 2020年08月29日 12:07:23 +02:00

Hi!

I'm trying the dependency feature between issues.

I find it's behaviour a bit weird. Not sure if this is a bug or just the way it should work.

So, I have created a test repo (https://codeberg.org/manheraz/test/) with two issues: "#1-This is a blocking issue" and "#2-This is a blocked issue".

When I click on the "Add dependency" combo in the "#2-This is a blocked issue", it waits for a few seconds and shows both the "#1-This is a blocking issue" and other issues not related to my account/organization/repositories.

Please, take a look to the attached screenshot (adding_blocking_issues.png)

As you can see in the second screenshot (unrelated_repo_issue.png), I have been able to add a blocking issue from an unrelated project, adding noise to their issue/repository.

@ncc1988: sorry about that, it was just a test.

Is this the intended behaviour?

If that is not the case, is this a Codeberg bug or a Gitea bug?

Thank you in advance.

Manu

Hi! I'm trying the dependency feature between issues. I find it's behaviour a bit weird. Not sure if this is a bug or just the way it should work. So, I have created a test repo (https://codeberg.org/manheraz/test/) with two issues: "[#1-This is a blocking issue](https://codeberg.org/manheraz/test/issues/1)" and "[#2-This is a blocked issue](https://codeberg.org/manheraz/test/issues/2)". When I click on the "Add dependency" combo in the "#2-This is a blocked issue", it waits for a few seconds and shows both the "#1-This is a blocking issue" and other issues not related to my account/organization/repositories. Please, take a look to the attached screenshot (adding_blocking_issues.png) As you can see in the second screenshot (unrelated_repo_issue.png), I have been able to add a blocking issue from an unrelated project, adding noise to their issue/repository. @ncc1988: sorry about that, it was just a test. Is this the intended behaviour? If that is not the case, is this a Codeberg bug or a Gitea bug? Thank you in advance. Manu

ncc1988 commented 2020年08月29日 13:09:21 +02:00

@ncc1988: sorry about that, it was just a test.

It's ok :)

> @ncc1988: sorry about that, it was just a test. It's ok :)

hw commented 2020年08月29日 19:08:22 +02:00

@6543 : what is your take here?

@6543 : what is your take here?

6543 commented 2020年08月29日 20:59:38 +02:00

@manheraz it's a feature:

lets take repo "awesom-lib" from organisation A witch is a depencency of "awesom-project" of organisation/user B, now B can link to upstream-lib issue

and a tip: if you like to get a issue quick: copy the whole title of the issue and paste it int toe dependency search box

@manheraz it's a feature: lets take repo "awesom-lib" from organisation A witch is a depencency of "awesom-project" of organisation/user B, now B can link to upstream-lib issue and a tip: if you like to get a issue quick: copy the whole title of the issue and paste it int toe dependency search box

6543 commented 2020年08月29日 21:01:47 +02:00

@hw can be disabled: https://docs.gitea.io/en-us/config-cheat-sheet/#service-service

DEFAULT_ENABLE_DEPENDENCIES

but I would not do this - since it limit things, only if it become abused by spamers to mouch ...

@hw can be disabled: https://docs.gitea.io/en-us/config-cheat-sheet/#service-service `DEFAULT_ENABLE_DEPENDENCIES` but I would not do this - since it limit things, only if it become abused by spamers to mouch ...

6543 commented 2020年08月29日 21:02:40 +02:00

... or add a time lock for issue/pull depencendy linking like it is done for comments/issues ...

... or add a time lock for issue/pull depencendy linking like it is done for comments/issues ...

lhinderberger commented 2020年09月13日 11:59:43 +02:00

It would be great if dependencies could be limited to the current repo. When referring to other repos, it might be enough to add the repo name in the box, similar to referring to issues in Markdown.

That would first and foremost speed up the search box, which right now is very slow, to the point of it becoming hard to use. It also would solve the issue of accidentally adding other people's issues to the own dependencies list.

Does someone know about a pre-existing upstream issue for this? I searched "dependency" and "issue dependencies" but couldn't find a matching issue.

It would be great if dependencies could be limited to the current repo. When referring to other repos, it might be enough to add the repo name in the box, similar to referring to issues in Markdown. That would first and foremost speed up the search box, which right now is very slow, to the point of it becoming hard to use. It also would solve the issue of accidentally adding other people's issues to the own dependencies list. Does someone know about a pre-existing upstream issue for this? I searched "dependency" and "issue dependencies" but couldn't find a matching issue.

6543 commented 2020年09月13日 18:02:48 +02:00

@lhinderberger I dont - go on for create a new one, if there realy exist one it will be linked there

@lhinderberger I dont - go on for create a new one, if there realy exist one it will be linked there

lhinderberger commented 2020年09月13日 22:27:11 +02:00

Done :) https://github.com/go-gitea/gitea/issues/12827

Done :) https://github.com/go-gitea/gitea/issues/12827

6543 commented 2021年08月29日 22:52:50 +02:00

should be fixed - feel free to reopen if not

should be fixed - feel free to reopen if not

Codeberg/Community