Add next and previous thread buttons

[tsondergaard]

Summary

In the issue view the thread combobox can have many items - looking through the stacktraces of threads is a lot of clicks and you have to remember the current thread yourself and find the next one in the thread combobox. This problem could be addressed very simply by adding two buttons - previous thread and next thread. The same type of buttons that are present in the same view for going through the list of events associated with the issue

Motivation

Dramatically improves thread navigation and it is a small task to implement it.

Additional Context

In the screenshot, I have borrowed the buttons for navigating events in the issue. The "Older" and "Newer" texts would be replaced with "Previous" and "Next".

[github-actions]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Accepted, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

[tsondergaard]

Please don't close this issue. The thread dropdown is a very big frustration. So many other things have been improved, but this remains a significant problem.

[karol-pilch]

I'm also interested in this feature. The implementation doesn't really matter for me, as long as there's an easy way to navigate to next / previous threads. I personally was googling for keyboard shortcuts and only found this issue here.

[markhajnal]

When you have an issue with 30-40 threads in it, it's really frustrating to use the dropdown list every time. Especially it doesn't remember where it was scrolled before and also the currently viewed thread is not highlighted.
This feature would be so helpful from UX POV. It would be very much appreciated.

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[Shreypatel13ll]

Hi there,

I'm interested in helping implement this improvement. Could someone please point me to the specific code file or files where these changes need to be made? Having the file path(s) would be extremely helpful in getting started.

Thanks!

[hubertdeng123]

@malwilley Is this something that we would prefer to do ourselves? Or should we help guide @Shreypatel13ll implement this?

[Shreypatel13ll]

any updates?

[getsantry]

Routing to @getsentry/product-owners-issues for triage ⏲️

[malwilley]

@Shreypatel13ll sorry for the late response! We have been thinking about revisiting the threads interface and may have a redesign incoming in the near future. So while we appreciate your offer to help, we need some guidance from design first on what we want this thread control to look like.

[rachrwang]

@tsondergaard, @karol-pilch, @markhajnal, @Shreypatel13ll - we're actively working to design an updated experience, and would love to get feedback on our upcoming direction. Would any of you be open to chatting with the team to review designs for this? You can schedule directly with us here: https://calendar.app.google/FiLw4JTPxErwr69t6

[tsondergaard]

@rachrwang I'm thrilled to hear that sentry is working on this. I won't be able to join any meetings, but I will be happy to answer questions and provide feedback in an asynchronous manner.