ShivamSharma43 opened a new pull request, #9402:
URL: https://github.com/apache/devlake/pull/9402

   ### Summary
   
   The Opsgenie `convertTeams` subtask writes the team's UUID to `teams.name` 
and the real team name to `teams.alias`:
   
   ```go
   Name:  team.Id,
   Alias: team.Name,
   ```
   
   Opsgenie is the only plugin that writes the `teams` table. DevLake's team 
dashboards (DORA by team, Engineering Throughput and Cycle Time - Team View, 
Work Logs) list and filter teams by `teams.name`. So Opsgenie teams show up 
there as UUIDs like `6a95a94a-2db4-4ec0-9f0f-694c40e017fe`, not as `old_team` / 
`new_team`. The id is already in `teams.id` (`opsgenie:Team:<connection>:<team 
id>`), so `name` doesn't need to hold it.
   
   Changes:
   
   - `tasks/teams_convertor.go`: `Name` is set to the Opsgenie team name. 
`Alias` is left empty, because Opsgenie teams have no separate alias and the 
name would only be repeated.
   - `e2e/snapshot_tables/teams.csv`: `name` is `old_team` / `new_team` (from 
`_raw_opsgenie_teams.csv`), and `alias` is empty. No other column changes.
   
   No migration: rows are rewritten on the next conversion.
   
   ### Does this close any open issues?
   
   No issue is open for this. The bug is described above.
   
   ### Screenshots
   
   N/A
   
   ### Other Information
   
   - `go test ./plugins/opsgenie/tasks/`: pass. The e2e test that checks 
`teams.csv` needs `E2E_DB_URL`, which I didn't run locally. The snapshot values 
come from the team names in the raw fixture.
   - `go vet ./plugins/opsgenie/...` and `gofmt`: clean.
   - No open PR touches the opsgenie plugin.
   - Suggested label: `pr-type/bug-fix`.
   - AI assistance disclosure: I prepared this change with Claude Code (Claude 
Opus 5.5), reviewed the diff and ran the tests. The commit has a 
`Generated-by:` trailer, following the ASF generative tooling guidance.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to