Adding fox for ticket 1204: Truncating epics query to 10 most recent …

…epics.

docs/devlog.md

@@ -8,6 +8,9 @@ Using this as a change log (apart from git log).
 
 Fixed #[1206](http://172.16.20.20/issues/1206): Only open tickets are displayed in search results.
 
+Fixed #[1204](http://172.16.20.20/issues/1204): Truncated epics to the most recent 10 (until paging is implemented)
+
+
 ### 2023-08-29
 After the ticket workflow discussions, I've been thinking about how to better integrate the "issue source of truth" (was osticket, becomming redmine) with the tools that *humans* use for discussion and issue resolution (Discord). Esther suggested an integration that tracked ticket discussion in specific threads, which was similar to slack-thread-per-issue in a few startups.
 

tickets.py

@@ -233,7 +233,7 @@ def get_epics(self) -> dict[str, list[Ticket]]:
         # query tickets pri = epic
         # http://localhost/issues.json?priority_id=14
         epic_priority_id = 14 # fixme - lookup based on "EPIC", from redmine.get_priorities()
-        response = self.session.get(f"/issues.json?priority_id={epic_priority_id}include=children&limit=100")
+        response = self.session.get(f"/issues.json?priority_id={epic_priority_id}&include=children&limit=10&sort={DEFAULT_SORT}")
         if not response:
             return {}