Constant ISSUE_DETAIL 

pub const ISSUE_DETAIL: &str = "query($id:ID!,$first:Int!,$after:String,$nestedFirst:Int!,$boardItems:Int!,$duplicates:Boolean!,$relationshipEvents:[IssueTimelineItemsItemType!]=[BLOCKED_BY_ADDED_EVENT,BLOCKED_BY_REMOVED_EVENT,BLOCKING_ADDED_EVENT,BLOCKING_REMOVED_EVENT,PARENT_ISSUE_ADDED_EVENT,PARENT_ISSUE_REMOVED_EVENT]){\n      node(id:$id){__typename ...BoardIssue ... on Issue{comments(first:$first,after:$after){nodes{id author{login} createdAt updatedAt body url}pageInfo{hasNextPage endCursor}}}}\n    } fragment BoardIssue on Issue{__typename id number title body url createdAt updatedAt state stateReason(enableDuplicate:$duplicates) repository{nameWithOwner} parent{id} subIssuesSummary{total} commentCount:comments{totalCount} relationshipEvents:timelineItems(itemTypes:$relationshipEvents){totalCount}\n      labels(first:$nestedFirst){nodes{id name color}pageInfo{hasNextPage}}\n      projectItems(first:$boardItems){nodes{id updatedAt project{id number}\n        fieldValues(first:$nestedFirst){nodes{\n          ... on ProjectV2ItemFieldSingleSelectValue{name field{\n            ... on ProjectV2SingleSelectField{id name options{id name}}\n          }}\n          ... on ProjectV2ItemFieldTextValue{text field{... on ProjectV2Field{id name}}}\n        }pageInfo{hasNextPage}}}pageInfo{hasNextPage endCursor}}}";

One issue by its own node id, with a page of its comments: what task show and a comment listing read, in one request.

ISSUE and ISSUE_COMMENTS in one document, rather than one then the other. The comments are selected here and not on the shared board_issue! fragment, which SEARCH_ISSUES and SUB_ISSUES nest under a page of a hundred issues: a comment connection there would multiply through both of those documents’ price, and neither needs one.