Create a command bar to show all available commands for the selected element of the dashboard view list table.

2 cases:

1. Empty Slot:

   • Allowed: Add View
   • Not Allowed: Replace View, Remove View

2. View Slot:

   • Allowed: Replace View, Remove View
   • Not Allowed: Add View

If a Custom View has already been loaded, then it should not be reloaded across page navigations.

Issue: Currently all Workflow States are fetched, however Issues within a specific team can only be moved within the specific team.

Solution: Fetch workflow states relevant only to the team's issues currently being displayed on the dashboard.

Implement a Route and Component which provides a selectable menu of Custom Views from which a single one can be selected.

On Selection of a Custom View, trigger the Custom View Resolver with the relevant filter object.

Pressing the down arrow key multiple times on the last issue within the display can cause duplicate pagination requests to be sent, resulting in duplicate issues being displayed.

Store and concatenate keyboard input before flushing after lack of input for configurable period of time.

Expected Behavior:

• Table columns able to be specified with: minimum-width, priority, and label.
• Table columns resize correctly in response to layout changes, first attempting to claim enough space within a table for each column's minimum width, then attempting to claim enough any more space as specified by column priority.

Implement the Initial Issue Load for CustomViews which are loaded using the DirectQueryPaginate strategy.

Create a framework to load the initial required data for a particular route or component on load.

Implement a resolver for Custom View 'team' filters. The 'team' filter can either be null (all teams) or a team object (issues from only one team). This filter will be considered an indirect filter which will not be directly queried.

Behavior in ViewLoader strategies:

• DirectQueryPaginate: Apply on fetched issues
• GenericIssuePaginate: If a team is selected (not all teams) query for the issues from that team, otherwise query on all issues.

"filters": { "team": { "id": "3e2c3a3a-c883-432f-9877-dcbb8785650a", "name": "Test-1", "key": "TES", "description": null } }

Ability to select View Panels by positional number and scroll through their issues.

Selection should be indicated by a change in border color of selected panel table.

Since querying for the 'timezone' field on the 'Team' Object returns only a location name, e.g. 'America/New_York', it is necessary to create a HashMap at execution time which will store all mappings from aforementioned location names to a float GMT offset which will be used for timezone transformations.

Implement a resolver which can use the 'creator' attribute of a custom view filter in order to fetch issues matching the provided Creator list.

Example of Creator Filter:
"filters": { "creator": [ { "ref": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf", "value": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf" } ], },

Refactor the CustomViewSelect and ViewPanel components to use the new table column layout framework, update column labels as well to be more space-efficient.

Allow for ENV variable 'LINEAR_VIEW_PANEL_PAGE_SIZE' to modify Linear View Panel Issue page size & ViewLoader loading procedure.

Custom Views should track how many API requests are required to achieve resolution and display this on their ViewPanels. This will help debugging and further strategy development.

Paginate and load new Issues for DirectQuery-strategy based ViewLoaders on scroll of ViewPanel.

Instead of creating a new client for every request, the reqwest client should be initialized to the relevant API endpoint and cloned for usage in GraphQL queries.

See: https://docs.rs/reqwest/0.8.4/reqwest/struct.Client.html

Implement a resolver which can use the 'subscriber' attribute of a custom view filter in order to fetch issues matching the provided Subscribers.

Example of Subscriber Filter :

"filters": { "subscribers": [ { "ref": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf", "value": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf" } ] },

Similar to 'LoadCustomViews' command; pagination does not need to be a separate command.

Shift workflow state modification to ViewPanel and remove deprecated routes/events.

Expected Behavior: When selecting and interacting with issues displayed in a view panel I should be able to see a highlighted list of available actions (with corresponding keyboard shortcuts) I can take on the selected issue (e.g. change workflow state, etc).

Implement a resolver which can use the 'labels' attribute of a custom view filter in order to fetch issues matching the provided Label list.

Example of Label Filter (No Label filter included) :

"filters": { "labels": [ {}, { "ref": "5e948c53-e672-46d7-b2a7-dc2194ae67b4", "value": "bug" }, { "ref": "3c053660-ea0c-4804-9fe5-e206ee40bd17", "value": "test-label-1" } ] },

Create a ViewLoader struct from a Custom View Filter.

The View Loader struct will be responsible for managing initial issue loads for a custom view (will encode filter, decide loading strategy) as well as maintaining all state required for Custom View Issue Pagination.

Implement a resolver which can use the state attribute of a custom view filter in order to fetch issues matching the provided workflow states.

Example of Workflow State Filter:
"filters": { "state": [ { "ref": "e4d5a438-381e-44b0-945f-211481f769e6", "value": "test-column-1" } ] }

Implement a resolver which can use the assignee attribute of a custom view filter in order to fetch issues matching the provided Assignee list.

Example of Assignee Filter (No Assignee filter included) :
"filters": { "assignee": [ { "ref": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf", "value": "ce943fa6-e9e1-4bc5-8131-ebf3ab1928bf" }, {} ] },

Create separate command bar component for re-use across separate command bars.

Implement the ability to use a keyboard shortcut while selecting a Linear Issue in order to open a modal to display the issue with an initial set of relevant fields:

• Team
• Title
• Description
• Labels
• Assignee
• Creator
• Status
• Priority
• Cycle
• Project
• Creation Date

Implement a resolver which can use the 'priority' attribute of a custom view filter in order to fetch issues matching the provided Priorities.

Example of Priority Filter :

"filters": { "priority": [ { "ref": 2, "value": 2 }, { "ref": 1, "value": 1 }, { "ref": 3, "value": 3 } ] },

Implement a resolver which can use the 'project' attribute of a custom view filter in order to fetch issues matching the provided Project.

Example of Project Filter (No Project filter included) :

"filters": { "project": [ {}, { "ref": "34197686-1d88-47ec-a1e0-321d9144eacd", "value": "34197686-1d88-47ec-a1e0-321d9144eacd" } ] },

At application start, paginate through all team objects within given organization (from PAT), and populate a HashMap mapping a team id to a timezone location.

Both the HashMap as well as a flag for timezone load state should be added to the 'App' struct.

Plan: Implement two separate classes of shortcut Commands: Sorting and Filtering.
Questions:

• Should these shortcuts always make new API requests?
• Is there ever a case where they can modify the display in place?

Answers:

• Sort Commands should always make new API requests to get a paginated list of ordered Issues
• Filter Commands should initially be implemented to always make new API requests.

Implement concurrent loading of all user-created view panels for main dashboard on navigation to ActionSelect Route.

Custom Views currently expect all of their filters except for filters within the same group as a directly queried filter to match for any given issue within a view; however, this is inaccurate, only one filter from each filter group present within the custom view needs to match.

Example:
Ignorable Filters needs to be included in the comparison process since, e.g.
if we have a Filter with two SelectedLabel filters and two SelectedState filters
and we are querying on one of the SelectedLabel filters, this method will correctly ignore the non-queried SelectedLabel filter
but it will expect both SelectedState filters to be applied simultaneously to the issue