Profiling Issue launch

[logicalbomb]

Final items to do before we launch Profiling Issues.

Tasks

Preview Give feedback

1. Update Jira integration to support generic issue types #42048
   +0
   
2. Update GitHub integration to support generic issue types (ticketing feature) #42049
   +0
   
3. Update PagerDuty to support generic issue types #42050
   +0
   
4. Update digests to handle generic issue types #42055
   Status: Stale +1
   
5. Make ingestor fault tolerant and production ready #42178
   Status: Backlog +1
   
6. Update post process forwarder to work with generic issues #42529
   +0
   
7. Add a way to process generic events in post_process_group #42530
   +0
   
8. Make the event and occurrence available in post_process_group #42531
   +0
   
9. Finalize IssueOccurrence message format #43948
   +0
10. Latest/oldest events endpoints need to query issue platform dataset to fetch next/prev ids #42278
    Status: Backlog +1
    
11. [FE] Pass dataset param to discover endpoints #43413
    Status: In Progress +1
    
12. Pass release info to save_issue_occurrence and create group related release rows #44085
    +0
    
13. Process contexts in search_issues #44129
    +0
    
14. Add profiling issue resources section #44117
    +0
    
15. Modify text in stack trace component to no longer say "Crashed in" for profile traces #44121
    Status: In Progress +1
    
16. Add link to profile from profiling issue details #44122
    +0
    
17. Add "issue.category:profile" autocomplete option in issue search #44429
    +0
    

---

epic in Jira

[chadwhitacre]

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

[getsantry]

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

[chadwhitacre]

Okay this is painful, I'm sorry. Details on getsentry/team-ospo#105, likely to be some additional noise before the automation is set up correctly. Sorry.