labels are not stored, if you want to add a label to an already existing issue. page gets reloaded, but label was not set.
Confirmed, also on other instances
the problem seems to be a POST request which is triggered on selecting the label. since the page gets reloaded, it seems that the request gets interrupted. If you wait for some seconds to get the POST request to be finished, before clicking somewhere (which triggers the page reload), the problem is gone. at least for me
For me this issue was a misunderstanding, I could not add labels because I did not set up labels for this repo. Very confusing, and yes, page reloads
Is the slow REST response a byproduct of running on a skeleton infrastructure? Or is there an issue in the request? The UI in the case of adding tags doesn’t have much in the way of request confirmation (there’s no green checkmark that shows up when the response comes back), so the route should be one directional. Update the database on click and that’s that.
It’s not a technical issue, but a bit unintuitive UI: you can enable a labelset and create new labels using the labels/milestones button at the top of the page.
Then you can add them
in my case, i already had labels created and some tagged to the issue, but i wanted to edit them (adding or removing one). i thought that this request does not need confirmation, like scott-joe mentioned above, but for some reasons, the update of the labels only succeeded if i wait for the response of the request
Hm, the user interface definitely has room for improvement, but functionality works. (Add label+edit tested via labels/milestones button at top of page).
What browser are you using?
Firefox (Fedora 29 repo version)
Actually it works here in Firefox
Related to https://github.com/go-gitea/gitea/issues/6191 ?
i think so.
This bug has been fixed upstream in master (not 1.7 branch), I plan to backport and deploy it on codeberg if it has not been backported by upstream by then.
Ok I backported this fix to our codeberg branch, so it should work now!
Please test and close if fixed (unfortunately this race condition did not occur on my (too slow?) machines.
seems to work. thanks
No due date set.
This issue currently doesn't have any dependencies.
Deleting a branch is permanent. It CANNOT be undone. Continue?