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

Migrate Performance Issues to Issue Platform #43973

Closed
4 tasks done
wedamija opened this issue Feb 1, 2023 · 7 comments
Closed
4 tasks done

Migrate Performance Issues to Issue Platform #43973

wedamija opened this issue Feb 1, 2023 · 7 comments
Assignees

Comments

@wedamija
Copy link
Member

wedamija commented Feb 1, 2023

We want to start serving performance issues via the Issue Platform. We'll need to dual write them for a while, migrate existing data across, and then have a way to switch search to use the issue platform.

Tasks

Preview Give feedback
  1. Status: Stale
    barkbarkimashark
  2. Status: Backlog
    udameli
  3. barkbarkimashark
  4. Status: Backlog
    barkbarkimashark

epic in Jira

@wedamija wedamija changed the title Migrate Performance Issues too Issue Platform Migrate Performance Issues to Issue Platform Feb 1, 2023
@chadwhitacre
Copy link
Member

What's the right Team: * label to apply to this issue? I'll assume it's the same for #42044.

@getsantry
Copy link
Contributor

getsantry bot commented Feb 4, 2023

Routing to @getsentry/issue-platform for triage, due by Tuesday, February 7th at 4:14 pm (sfo). ⏲️

@wedamija
Copy link
Member Author

wedamija commented Feb 4, 2023

What's the right Team: * label to apply to this issue? I'll assume it's the same for #42044.

Do we need to apply these team labels for internal projects? I've added issue platform, but it feels a bit onerous to need to add this label to every issue

@chadwhitacre
Copy link
Member

chadwhitacre commented Feb 6, 2023

I've added issue platform

Thanks. :)

it feels a bit onerous to need to add this label to every issue

A Team label is not needed for every issue (yet; it's something I'm mulling over). In this case we need it because it's Type: Epic and we want that auto-populated in Jira, we need a team label to map to the right project in Jira (also suggests why having every GH issue assigned to a team is helpful, so we don't have orphans in the backlog—idea would be to automate this based on author, but need a lot of teams cleanup and groundwork first).

@chadwhitacre
Copy link
Member

PITA, sorry. Deets.

@wedamija
Copy link
Member Author

wedamija commented Feb 7, 2023

@udameli This was closed due to an issue with github -> jira sync. If you start work on this before we get that sync fixed, we can just duplicate this epic to work around the problems

@chadwhitacre chadwhitacre reopened this Feb 7, 2023
@sync-by-unito sync-by-unito bot closed this as completed Feb 7, 2023
@logicalbomb logicalbomb reopened this Feb 15, 2023
@logicalbomb
Copy link
Contributor

Unito is dead, long live Unito. Sorry for the shenanigans.

@scefali scefali closed this as completed May 30, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants