SergeyDjam/jirasignal: main.go; 10 LoC

Found a possible issue in [SergeyDjam/jirasignal](https://www.github.com/SergeyDjam/jirasignal) at [main.go](https://github.com/SergeyDjam/jirasignal/blob/47269a779f63038b18e56be22a66e3e5f8b48362/main.go#L62-L71)

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 65

[Click here to see the code in its original context.](https://github.com/SergeyDjam/jirasignal/blob/47269a779f63038b18e56be22a66e3e5f8b48362/main.go#L62-L71)

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

```go
for _, issue := range issues {

n := newNotificationFromIssue(issue)
fmt.Println(issue.Key, "has some changes ->", jiraIssue{&issue}.getLink(), "at", timeNow())

go func(n notification) {
sendNotification(n)
time.Sleep( time.Duration(i) * time.Second)
}(n)
}

```

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: 47269a779f63038b18e56be22a66e3e5f8b48362

Read main.go lines 62-71 in the referenced commit, starting with the range loop and the analyzer message about a reference used in a composite literal. Check whether this usage is a bug, mitigated, or desirable behavior in context. Done means classifying the finding with the corresponding issue reaction.

Written by the indexing model from the issue text.