Skip to content
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

[Question][Devlake Config UI] Problem with Adding Data Scopes #7436

Closed
Matoro17 opened this issue May 7, 2024 · 6 comments
Closed

[Question][Devlake Config UI] Problem with Adding Data Scopes #7436

Matoro17 opened this issue May 7, 2024 · 6 comments
Labels
type/question This issue is a question

Comments

@Matoro17
Copy link

Matoro17 commented May 7, 2024

Question

When configuring the "Add Data Scope: Jira", I'm facing a strange issue and I would like to know what can cause that.
A specific Jira Board cannot be selected, the API token has all the permissions, but still, what can cause this block?
I know that if you already have a Jira board added in the Data scope list you cannot add that again, but this one is not on the list.

Screenshots

image

@Matoro17 Matoro17 added the type/question This issue is a question label May 7, 2024
@Matoro17 Matoro17 changed the title [Question][Module Name] Question title [Question][Devlake Config UI] Problem with Adding Data Scopes May 7, 2024
@klesh
Copy link
Contributor

klesh commented May 8, 2024

Hi, can you share the API output from the Developer Toolbar under the Network tab? Thanks.

@Matoro17
Copy link
Author

Matoro17 commented May 8, 2024

Is this information that you are referening to?
{ "children": [ { "type": "scope", "parentId": null, "id": "59", "name": "Team Program Design Board", "fullName": "Team Program Design Board", "data": { "createdAt": "0001-01-01T00:00:00Z", "updatedAt": "0001-01-01T00:00:00Z", "_raw_data_params": "", "_raw_data_table": "", "_raw_data_id": 0, "_raw_data_remark": "", "connectionId": 0, "boardId": 59, "projectId": 10052, "name": "Team Program Design Board", "self": "https://correlation-one.atlassian.net/rest/agile/1.0/board/59", "type": "kanban", "jql": "" } }, ...... { "type": "scope", "parentId": null, "id": "41", "name": "User board", "fullName": "User board", "data": { "createdAt": "0001-01-01T00:00:00Z", "updatedAt": "0001-01-01T00:00:00Z", "_raw_data_params": "", "_raw_data_table": "", "_raw_data_id": 0, "_raw_data_remark": "", "connectionId": 0, "boardId": 41, "projectId": 10044, "name": "User board", "self": "https://correlation-one.atlassian.net/rest/agile/1.0/board/41", "type": "scrum", "jql": "" } } ], "nextPageToken": "" }
image

@klesh
Copy link
Contributor

klesh commented May 9, 2024

@Matoro17 Yes, can you share the entries of the problematic boards?

@Matoro17
Copy link
Author

Matoro17 commented May 9, 2024

The problematic board is the "User Board", that is in the Json

@mintsweet
Copy link
Member

Hi @Matoro17, Can you share all of the API returns? We need to know if there is a duplicate ID. Alternatively, could you check whether the added data scope includes an entry with ID 41?

@Matoro17
Copy link
Author

Matoro17 commented May 10, 2024

I think that I understand what happened now.
The users that were using the Jira Board changed the name of the Jira Board

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/question This issue is a question
Projects
None yet
Development

No branches or pull requests

3 participants