Jobs in actions are restarted in an incomprehensible order

[vjarskee]

Description

I have a few workflows of roughly this type:

jobs:
  First test:
    runs-on: node-16.16.0
  Second test:
    runs-on: node-16.16.0
  Build:
    needs: [First test, Second test]
    runs-on: ubuntu-22.04
  Run:
    needs: Build
    runs-on: ubuntu-22.04

When automatically started, workflow runs as it should, but if you manually restart one job or all of them with a button in the interface, they may start in an unclear order, for example, Build or Run may start together with First test and Second test, although they need First test and Second test.

Gitea Version

1.21.0

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

Ubuntu 20.04.4 LTS

How are you running Gitea?

Official docker image gitea/gitea:1.21.0

Database

PostgreSQL

[lng2020]

same as #27884

[yp05327]

Close this one as duplicated #27884.
If it is not expected, feel free to reopen it.