Patch #10916
Optimisation in issues relations display
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | Code cleanup/refactoring | |||
| Target version: | 2.3.0 |
Description
In the relations loop some variables are recalculated too many times
Associated revisions
Store the other issue in a variable (#10916).
History
#1 Updated by Jean-Baptiste Barth 11 months ago
Setting.blah is already cached in an Setting's class variable. The other optimization might be relevant, it would save some == calls and conditions..
#2 Updated by Jérôme BATAILLE 6 months ago
Do you want us to bring a new patch taking in accound your remark ?
#3 Updated by Jean-Philippe Lang 5 months ago
- Category set to Code cleanup/refactoring
- Status changed from New to Closed
- Target version set to 2.3.0
Variable named other_issue added to store relation.other_issue(@issue) as proposed in the patch, thanks.
