**As** a user
**I want to** Begin of the insertionnot wait for activity to get renderedEnd of the insertion Begin of the deletion \[enter objective\]End of the deletion
**so that** Begin of the insertionI can use it efficientlyEnd of the insertion Begin of the deletion \[enter desired result\]End of the deletion

**Acceptance criteria**

* Begin of the insertionThere are no separate queries made for each journal detail requiring to load modelsEnd of the insertion Begin of the deletion <br>End of the deletion


**Technical notes**

* Begin of the insertionFollowing should currently be the complete list of formatters that are querying more data:

End of the insertion Begin of the deletion <br>


**Permissions and visibility considerations**

End of the deletion * Begin of the insertionlib\_static/plugins/acts\_as\_journalized/lib/journal\_formatter/named\_association.rb

* lib/open\_project/journal\_formatter/attachment.rb

* lib/open\_project/journal\_formatter/cause.rb

* lib/open\_project/journal\_formatter/custom\_field.rb

* lib/open\_project/journal\_formatter/file\_link.rb

* lib/open\_project/journal\_formatter/project\_life\_cycle\_step\_active.rb

* lib/open\_project/journal\_formatter/project\_life\_cycle\_step\_dates.rb

* lib/open\_project/journal\_formatter/subproject\_named\_association.rb

* lib/open\_project/journal\_formatter/time\_entry\_named\_association.rb

* modules/meeting/lib/open\_project/journal\_formatter/meeting\_work\_package\_id.rb

* Some formatters can query even more data, like custom\_field when typeEnd of the insertion Begin of the deletion _To whomEnd of the deletion is Begin of the insertionlistEnd of the insertion Begin of the deletion this feature visible?_End of the deletion

* Begin of the insertionCurrently the only mitigation for N+1 queriesEnd of the insertion Begin of the deletion _WhenEnd of the deletion is Begin of the insertionin `JournalFormatter::NamedAssociation` which uses `JournalFormatterCache` passed through `cache:` argument, butEnd of the insertion it Begin of the insertionis duplicating rails query cache, so probablyEnd of the insertion not Begin of the insertionmaking it more any more efficient and still queries models one by one

End of the insertion Begin of the deletion visible?_


**Translation considerations**

End of the deletion * Begin of the insertionI thinkEnd of the insertion Begin of the deletion _Key terms and phrases inEnd of the deletion the Begin of the insertionway to resolve it is to group all detailsEnd of the insertion Begin of the deletion key languages_&nbsp;


**OutEnd of the deletion of Begin of the insertionall journals per formatter class and request every formatter to fetch all needed dataEnd of the insertion Begin of the deletion scope**

* <br>End of the deletion