The current Timesheet view in Jira lacks flexibility regarding which issues are displayed and how they are organized. I propose an overhaul of the view to include advanced filtering capabilities (Status, Key, JQL), the ability to manually pin/unpin issues, and expanded grouping options to improve time-tracking accuracy and user efficiency.

Problem Statement

Currently, users struggle with the Timesheet view for two main reasons:

1. Clutter: The view often populates with irrelevant tickets (e.g., closed issues or old tasks), making it difficult to locate active work.

1. Invisibility: If a user works on a ticket they are not explicitly assigned to, it does not appear in their default view, forcing them to search for it repeatedly to log time.

1. Rigid Structure: The inability to group by criteria other than the default makes it hard to visualize time distribution across Epics or Sprints.

Proposed Solution

I suggest implementing the following three enhancements to the Timesheet UI:

1. Advanced Filtering Toolbar

Users should be able to filter the rows in their timesheet dynamically, similar to the "Search Issues" navigator.

• Status Filter: Allow users to hide "Done" or "Closed" issues to clean up the view.

• Key/Text Filter: A quick search bar to filter visible rows by Issue Key or Summary.

• JQL Support: Allow power users to apply a saved filter or JQL query to populate the timesheet rows (e.g., project = X AND priority = High).

2. Manual Issue Management (Add/Remove)

Users need manual control over the specific rows displayed in their grid:

• "Add Issue" Button: A simple input field to search for an issue by Key or Summary and add it to the timesheet view immediately, even if the user is not the assignee.

• "Remove/Hide" Action: An option on the row level (e.g., a context menu) to remove a specific issue from the view for the current week without deleting logged work.

• Pinning: The ability to "Pin" specific overhead tickets (e.g., "General Meetings," "Management") so they persist week-over-week.

3. Flexible Grouping Options

Introduce a "Group By" dropdown menu to organize the timesheet rows hierarchically.

• Group by Epic: To see total time spent per initiative.

• Group by Sprint: To separate active sprint work from backlog/maintenance work.

• Group by Component/Label: For teams organized by functional areas.

Benefits

• Increased Accuracy: Users are less likely to book time to the wrong "general" ticket if they can easily find the correct specific ticket.

• Efficiency: Reduces the time spent scrolling and searching for issues every day.

• Better UX: Provides a personalized experience that adapts to how different teams (Developers vs. PMs) manage their work.