streamline "Create GitHub Issue" workflow

[chadwhitacre]

Per Twitter.

Here's my current workflow:

A. Click "Create GitHub Issue" in the sidebar. Here's what I see:

B. Remember that I have to copy/paste the actual traceback from elsewhere.

C. ⌘-click my browser's "Back" button to open the previous page in a new tab so I don't lose my current state.

D. Switch over to that new tab.

E. Scroll around until I see the "Raw" button and click it.

F. Copy the Stacktrace ("Stacktrace?" 😞) from the popup.

G. Close the popup.

H. Close the second tab.

I. Paste the traceback:

J. Edit the traceback to look like a Python traceback:

K. Now I'm ready to begin. I can write a descriptive title, and fill out the description with more info.

It'd be nice to cut out B through J (inclusive). :-)

[dcramer]

As a note to myself, the bug is here:

    def _get_group_body(self, request, group, event, **kwargs):
        interface = event.interfaces.get('sentry.interfaces.Stacktrace')
        if interface:
            return interface.to_string(event)
        return

We broke this when we started storing stacktraces as part of exceptions

[chadwhitacre]

Why did you decide to call them stacktraces instead of tracebacks? To come across as being more language-neutral?

[dcramer]

Literally no idea :)

[chadwhitacre]

Well, cutting out B through I would still be a win. :-)

[MaxBittker]

the github plugin accomplishes this now, right?