[Bug][Linear] Config UI cannot associate a scope config with Linear team scopes

Aberta
#9,355 0 comentários 0 reações 1 responsável Ver no GitHub

Mantenedores costumam responder em até 2 dias

@VictorColomb já está trabalhando nisso.

Desde 9/11/2026.

Avaliação

Esta issue ainda não foi avaliada.

Descrição

type/bug
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
  1. Create a Linear connection.
  2. Open the connection page and add one or more teams as data scopes.
  3. Select a team in the table. The "Associate Scope Config" button never appears (compare with a GitHub connection, where it does).
  4. 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
Linguagem predominante
Go
Estrelas
3.2k
Forks
840
Merge médio
1d 21h
PRs com merge (30d)
104

Preparar o ambiente

Abrir no Codespaces

Inicia o contêiner de desenvolvimento do projeto no navegador, com a sua própria conta do GitHub.

  • Sem Dockerfile nem arquivo Docker Compose
  • Tem um modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de apache/devlake

Todas as issues de apache/devlake

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.