Issue creation via api with an user from a different team is incomplete #14654

New Issue

GiteaMirror · 2025-11-02T11:19:08-06:00

GiteaMirror commented

2025-11-02 11:19:08 -06:00

Originally created by @kim2048 on GitHub (Jun 25, 2025).

Description

Hello,
I have a strange behavior when I try to create an Issue via the api (POST /repos/{owner}/{repo}/issues, auth via token). The setup looks like this:

organization
  repos
    repoA
    repoB
  members
    userX
      role: Member
      accessToken: write:issue
  teams
    teamA
      repoA
    teamB
      userX
      repoB

When I try to create an issue (with title,body,labels,assignees) with the access token of userX in repoA the following happens:

The Issue will be created but neither labels or assignees are applied. No errors in the response. In repoB everything works as expected, also when I add userX to teamA.

Should userX be able to create issues in repoA? Why is the issue incomplete?

Gitea Version

1.23.8

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

No response

Operating System

No response

How are you running Gitea?

I don't know

Database

PostgreSQL

Originally created by @kim2048 on GitHub (Jun 25, 2025). ### Description Hello, I have a strange behavior when I try to create an Issue via the api (`POST /repos/{owner}/{repo}/issues`, auth via token). The setup looks like this: ``` organization repos repoA repoB members userX role: Member accessToken: write:issue teams teamA repoA teamB userX repoB ``` When I try to create an issue (with title,body,labels,assignees) with the access token of `userX` in `repoA` the following happens: The Issue will be created but neither labels or assignees are applied. No errors in the response. In `repoB` everything works as expected, also when I add `userX` to `teamA`. Should `userX` be able to create issues in `repoA`? Why is the issue incomplete? ### Gitea Version 1.23.8 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version _No response_ ### Operating System _No response_ ### How are you running Gitea? I don't know ### Database PostgreSQL

GiteaMirror added the type/bug label 2025-11-02 11:19:08 -06:00

GiteaMirror commented

2025-11-02 11:19:08 -06:00

@wxiaoguang commented on GitHub (Jun 25, 2025):

Can you try 1.24 nightly? I think it might have fixed the problem

@wxiaoguang commented on GitHub (Jun 25, 2025): Can you try 1.24 nightly? I think it might have fixed the problem * https://dl.gitea.com/gitea/1.24-nightly/ * https://hub.docker.com/r/gitea/gitea/tags?name=1.24-nightly

GiteaMirror commented

2025-11-02 11:19:09 -06:00

@kim2048 commented on GitHub (Jun 26, 2025):

No, I'm using gitea at work. But I can ask the admins if we can update to the 1.24.2 release soon.

@kim2048 commented on GitHub (Jun 26, 2025): No, I'm using gitea at work. But I can ask the admins if we can update to the 1.24.2 release soon.

GiteaMirror commented

2025-11-02 11:19:09 -06:00

@wxiaoguang commented on GitHub (Jun 26, 2025):

Not 1.24.2, but 1.24 nightly (will be 1.24.3 soon) which contains some team related fixes.

@wxiaoguang commented on GitHub (Jun 26, 2025): Not 1.24.2, but 1.24 nightly (will be 1.24.3 soon) which contains some team related fixes.

GiteaMirror commented

2025-11-02 11:19:09 -06:00

@kim2048 commented on GitHub (Jun 26, 2025):

Ok, then I have to wait for 1.24.3 ;) But the repro should be easy

@kim2048 commented on GitHub (Jun 26, 2025): Ok, then I have to wait for 1.24.3 ;) But the repro should be easy

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#14654