<!---
Please read this!

Before opening a new issue, make sure to search for keywords in the issues
filtered by the "Regression" or "Bug" label:

- https://foss.heptapod.net/heptapod/heptapod/issues?label_name%5B%5D=Regression
- https://foss.heptapod.net/heptapod/heptapod/issues?label_name%5B%5D=Bug


and verify the issue you're about to submit isn't a duplicate.
--->

### Summary

<!-- Summarize the bug encountered concisely. -->

### Steps to reproduce

<!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. -->

### Example Project

<!-- If possible, please create an example project here on foss.heptapod.net or over at heptapod.host that exhibits the problematic 
behavior, and link to it here in the bug report. If you are using an older version of Heptapod, this 
will also determine whether the bug is fixed in a more recent version. -->

### What is the current *bug* behavior?

<!-- Describe what actually happens. -->

### What is the expected *correct* behavior?

<!-- Describe what you should see instead. -->

### Relevant logs and/or screenshots

<!-- Paste any relevant logs - please use code blocks (```) to format console output, logs, and code
 as it's tough to read otherwise. -->

#### Details about the Heptapod instance where the bug occurs

<!--  If you don't have a reproduction on foss.heptapod.net nor heptapod.host,
please post some details about the instance exhibiting the problem

- Type of deployment (source, Docker, Omnibus, Heptapod Development Kit)
- Exact Heptapod version
- For source deployments, all possibly relevant versions.

On source production instances, one can get lots of information by running

```
bundle exec rake gitlab:env:info RAILS_ENV=production
```

from the Rails application directly, with the same system user that runs
it normally.

In the case of the Heptapod Development Kit, use this from the Rails
application repository:

```
bundle exec rake gitlab:env:info RAILS_ENV=production
```

-->

### Possible fixes

<!-- If you can, link to the line of code that might be responsible for the problem. -->

/label ~Bug
