edtro / edtro/EdTro.AzureDevOps.Extensions.querybasedboards

Bug: queries not shown in settings after project is renamed

Đang mở
#47 11 bình luận 1 reaction 1 người được giao Được @edtro nhận Xem trên GitHub
bug
Ngôn ngữ chính
Không có dữ liệu ngôn ngữ
Star
28
Fork
3
Chỉ số merge pull request
Không có pull request nào được merge trong 30 ngày

Mô tả

## Quick tipp
If you are stumbeling over the same issue, see the workaround solution here: https://github.com/edtro/EdTro.AzureDevOps.Extensions.querybasedboards/issues/47#issuecomment-812130248

## Original request

I've created a couple of shared queris in a project and none of them is showing up in the project settings to allow configuration. I guess there is something screwed up but I don't know exactly where to start. I've a couple of projects where I've done similar setups and it's working quite well.

Special in the affected project: it has been renamed.

Other inputs or hints: in the development console of the brwoser I get a 404 when I want to open the settings:

```
GET https://server/collection/_apis/ExtensionManagement/InstalledExtensions/realdolmen/EdTro-AzureDevOps-Extensions-QueryBasedBoards-Public/Data/Scopes/Default/Current/Collections/querybasedboards-import/Documents 404 (Not Found)
```

When I run a query and click the "show as board" button there is a super quick error message I'm not able to capture. In the developer console I see a bunch of errors:

```
ms.vss-web.platform-…jTC5yBclkr.min.js:1 POST https://server/collection/_apis/ExtensionManagement/InstalledEx…copes/Default/Current/Collections/querybasedboards-configuration/Documents 400 (Bad Request)

Could not create configuration for query: ee5fca6e-219e-4811-a071-4bedefa767da

GET https://server/collection/_apis/GraphProfile/MemberAvatars/win.Uy0xLTUtMjEtMzMwMDg0MjA5Mi04MTkxODE4MjUtMjEzMzgyNzUzOC0zMzg1MQ 401 (Unauthorized)

```
(I guess the last one is not relevant, only to be complete)

What I also can say: I can add the global config but it is not repected in the queries.

Please let me know how I can help to investigate further.

**EDIT**
Just found out a very important thing I guess: I had a collection backup restored as test environment before we renamed the affected project. And before we renamed the project the queries have worked propperly. So I assume that this is linked to renaming projects.

Hướng dẫn đóng góp

Chưa lập chỉ mục được hướng dẫn đóng góp cho kho mã nguồn này

Đánh giá

Issue này chưa được đánh giá.

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.