### Expected behavior
*[Insert details on expected behaviour]*

### Observed behavior
*[Insert details on observed behaviour]*

### Steps to reproduce
*[Insert reproduction steps (if known)]*

### Version
*[Insert version information]*

### Additional information
*[Insert any additional information]*

#### Can't comment on Issues?
Some users have been unable to comment on Github issues when an [adblocker extension is enabled](https://docs.bugsnag.com/platforms/browsers/faq/#is-bugsnag-blocked-by-ad-blockers).
We recommend temporarily disabling the extension, or if that fails, contacting support@bugsnag.com.

### Description
<!-- A quick description of what you're trying to accomplish -->

### Issue
<!--
  What went wrong? (If this issue is a general question or a proposed change,
  feel free to delete this and subsequent sections.
-->

### Environment

Library versions:

<!--
  Paste the output of this command into the code block below:
    bundle list | grep -E "(bugsnag|rails|sidekiq|que|sinatra|resque|shoryuken|mailman|delayed_job)"
-->
```

```

- OS / OS version:
- debug mode or production?:

<!--
  Below are a few approaches you might take to communicate the issue, in
  descending order of awesomeness. Please choose one and feel free to delete
  the others from this template.
-->
### Example Repo

- [ ] Create a minimal repository that can reproduce the issue after running
  `bundle install` and `rackup` (or `rails server`, or `ruby some-script.rb`,
  etc)
- [ ] Link to it here:

### Example code snippet

```ruby
require 'bugsnag'

# (Insert code sample to reproduce the problem)
```

<!-- Error messages, if any -->
```

```

Update issue template to be more env-specific
docs: Update issue template to be more env-specific
