API returns issues filtered by label, when the label is empty #304
Labels
No labels
Backlog Status
Needs Review
Backlog Status
Ready
Chore
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forge/forge#304
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I enabled forge.fedoraproject.org in jira_sync today and found out that https://forge.fedoraproject.org/api/v1/repos/cle/requests-test/issues?labels=cle&limit=50 is returning issues that have
labels: [].I assume this is caused by namespace being same as the label to filter the issues by.
@zlopez, I have initialised a repository of the same name,
requests-testand have created four issue tickets in total there. Two of those issue tickets (i.e. cle/requests-test#2 and cle/requests-test#4) have the labelcleassigned to them, while the other two of those tickets (i.e. cle/requests-test#1 and cle/requests-test#3) do not. When making the same API request from before, I see the following content.Could you please acknowledge the same that the issue that you mentioned of no longer persists so that this issue ticket could be closed?
As the jira_sync is no longer used for forge.fedoraproject.org I can't test it anymore. I'm OK with just closing this as the sync is now done by webhooks and that seems to work.
Yeah, the webhooks make use of the same API endpoints, so I have confirmed them to be working just fine this morning. Thanks for the confirmation, @zlopez - I am going ahead with closing this issue ticket.