Patch #15072
Optimization of issues journal custom fields display
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jean-Philippe Lang | % Done: | 0% | |
| Category: | Code cleanup/refactoring | |||
| Target version: | 2.4.0 |
Description
Custom filed is reloaded for each detail
even if cached by active record, we can avoid to reload them
Associated revisions
Avoid lots of CustomField.find_by_id calls when displaying an issue history with custom fields (#15072).
History
#1
Updated by Jérôme BATAILLE over 6 years ago
#2
Updated by Jean-Philippe Lang over 6 years ago
- Category changed from Issues to Code cleanup/refactoring
- Status changed from New to Closed
- Assignee set to Jean-Philippe Lang
- Target version set to 2.4.0
I've committed r12217 which avoids much more of these cache hits, thanks for pointing this out.
#3
Updated by Jérôme BATAILLE over 6 years ago
Sure your solution is more efficient.
Thanks !
#4
Updated by Jérôme BATAILLE about 3 years ago
Hi, you can indicate in the Resolution that's it's Fixed, if you have the time to, thanks a lot.
#5
Updated by Toshi MARUYAMA about 3 years ago
Jérôme BATAILLE wrote:
Hi, you can indicate in the Resolution that's it's Fixed, if you have the time to, thanks a lot.
"patch" tracker does not have "resolution" filed.