callerobertsson/jiracli: commands/epics.go; 3 LoC

Found a possible issue in [callerobertsson/jiracli](https://www.github.com/callerobertsson/jiracli) at [commands/epics.go](https://github.com/callerobertsson/jiracli/blob/84275767f636c5d54be99c34ac6c63661a88ec40/commands/epics.go#L45-L47)

Below is the message reported by the analyzer for this snippet of code. Beware that the analyzer only reports the first issue it finds, so please do not limit your consideration to the contents of the below message.

> reference to issue was used in a composite literal at line 46

[Click here to see the code in its original context.](https://github.com/callerobertsson/jiracli/blob/84275767f636c5d54be99c34ac6c63661a88ec40/commands/epics.go#L45-L47)

Click here to show the 3 line(s) of Go which triggered the analyzer.

```go
for _, issue := range issueList.Issues {
printIssueRow(&issue, "")
}

```

Leave a reaction on this issue to contribute to the project by classifying this instance as a **Bug** :-1:, **Mitigated** :+1:, or **Desirable Behavior** :rocket:
See the descriptions of the classifications [here](https://github.com/github-vet/rangeclosure-findings#how-can-i-help) for more information.

commit ID: 84275767f636c5d54be99c34ac6c63661a88ec40

Start with commands/epics.go lines 45-47 and inspect printIssueRow plus the type of issueList.Issues to understand whether the referenced range variable can produce incorrect output. Run the project's available Go tests or checks, then confirm the analyzer finding is addressed without changing expected issue-row behavior.

Written by the indexing model from the issue text.