[Bug][Linear] Config UI cannot associate a scope config with Linear team scopes
維護者通常 2 天內回覆
@VictorColomb 已經在處理了。
開始於 2026年11月9日。
評估
這個 Issue 還沒有評估資料。
描述
Search before asking
- I had searched in the issues and found no similar issues.
What happened
The Config UI for Linear connections does not offer a way to create or attach a Scope Config to a Data Scope (i.e. Linear team). In other words, the "Associate Scope Config" button doesn't appear on the /connections/linear/1 page.
Without a scope config, my Linear issues are not classified by type, which affects the issue-based metrics, including DORA.
What do you expect to happen
I expect the same scope config experience for Linear as for the other issue-tracking plugins. I should be able to create a scope config, choose which issue types count as requirements, bugs and incidents, and apply it to one or more teams from Config UI, without calling the API myself.
How to reproduce
- Create a Linear connection.
- Open the connection page and add one or more teams as data scopes.
- Select a team in the table. The "Associate Scope Config" button never appears (compare with a GitHub connection, where it does).
- In a blueprint's connection detail, the data scope table gives no way to set a scope config for Linear scopes either.
Anything else
Other connection types (e.g. GitHub, Jira) already provide a UI to create and attach Scope Configs. The Linear plugin backend already provides the mechanic, and it's reachable via API (see below). I therefore believe that the fix is just wiring a Scope Config UI.
API workaround
curl -X POST <base-url>/plugins/linear/connections/1/scope-configs \
-H 'Content-Type: application/json' \
-d '{"name":"default","entities":["TICKET"],"issueTypeRequirement":"^Story$","issueTypeBug":"^Bug$","issueTypeIncident":""}'
curl -X PATCH <base-url>/plugins/linear/connections/1/scopes/<team-id> \
-H 'Content-Type: application/json' -d '{"scopeConfigId":1}'
Version
v1.0.3-beta19
Are you willing to submit PR?
- Yes I am willing to submit a PR!
Code of Conduct
- I agree to follow this project's Code of Conduct
- 主要語言
- Go
- 星號
- 3.2k
- 分支
- 840
- 平均合併
- 1 天 21 小時
- 30 天內合併 PR
- 104
環境準備
在瀏覽器裡用你自己的 GitHub 帳號啟動這個專案的開發容器。
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 沒有貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
apache/devlake 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 60/100
維護者通常 2 天內回覆
-
[Bug][CircleCI] collectPipelines panics with a nil pointer dereference when the sync policy has no timeAfter可能已有人在做 @ShivamSharma43 今天認領。 未關閉
apache/devlake#9367 · 已指派 1 人 ·
維護者通常 2 天內回覆
-
[Bug][Asana] Story, subtask and tag collectors stop at 100 per task; task and user collectors restart on a full last page可能已有人在做 @ShivamSharma43 今天認領。 未關閉
apache/devlake#9365 · 已指派 1 人 ·
維護者通常 2 天內回覆
-
[Bug][GitHub] Extract Issues succeeds without extracting when the issue regexes or milestones can't be loaded可能已有人在做 @ShivamSharma43 於 1 天前認領。 未關閉
apache/devlake#9358 · 已指派 1 人 ·
維護者通常 2 天內回覆
-
[Bug][JIRA Service API TOKEN] Jira API Gateway: saved service-account token truncated by varchar(255), causing Base64 errors and HTTP 500可能重新可做 關聯的 PR 已關閉且未合併。 未關閉type/bug
難度 3/5 1-2 天 新手友好度 58/100
維護者通常 2 天內回覆
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 75/100
維護者通常 1 天內回覆
-
GitHub webhook is not subscribed to release events, so `event: release` never triggers可能已有人在做 @qsun 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 78/100
woodpecker-ci/woodpecker#7542 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 74/100
zilliztech/milvus-backup#1386 ·
維護者通常 1 天內回覆
-
Pipelined flush no longer observes kill signals after #2042: flush backoffer is built with nil vars未關閉
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆