-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty loading issue context popup for external issue tracker #17047
Comments
would it be possible to check the web console - there is likely to be an error in there. |
OK it's likely something to do with: gitea/web_src/js/features/contextpopup.js Lines 5 to 12 in e2f0ab3
this shouldn't be firing for external issues - so probably these need to have a different class instead of |
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Sep 14, 2021
The issues pop-up context cannot work for external issues - therefore do not show these. Fix go-gitea#17047 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
that referenced
this issue
Sep 15, 2021
The issues pop-up context cannot work for external issues - therefore do not show these. Fix #17047 Signed-off-by: Andrew Thornton <[email protected]>
zeripath
added a commit
to zeripath/gitea
that referenced
this issue
Sep 15, 2021
Backport go-gitea#17050 The issues pop-up context cannot work for external issues - therefore do not show these. Fix go-gitea#17047 Signed-off-by: Andrew Thornton <[email protected]>
lunny
pushed a commit
that referenced
this issue
Sep 15, 2021
Backport #17050 The issues pop-up context cannot work for external issues - therefore do not show these. Fix #17047 Signed-off-by: Andrew Thornton <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm seeing an empty issue context popup that remains loading, when an external issue tracker is configured.
This is since upgrading from 1.14 to 1.15.
Screenshots
The text was updated successfully, but these errors were encountered: