[feature]: Allow deeper customization of the issue detail layout, sidebar, activity history, and action placement

Is there an existing issue for this?

• I have searched the existing issues

Summary

It would be useful to allow workspace or project admins to customize the issue detail page layout more deeply.

The customization should not be limited only to custom fields. It could also include the organization of the main content area, the right-side panel, the activity/history section, comments, tabs, field groups, and action buttons.

This would allow teams to adapt the issue page to their workflow and prioritize the information that matters most.

Requested behavior

Allow admins to customize the issue detail layout, including both the main area and the side panel.

Possible customization options:

- Customize the main issue content area
- Customize the right-side properties panel
- Create custom tabs
- Reorder fields
- Group fields into sections
- Hide less relevant fields
- Pin important fields
- Move fields between the main area and sidebar
- Change the default order of activity/history
- Choose whether new comments appear at the top or bottom
- Choose where action buttons are displayed
- Create different layouts per project, issue type, or workspace

Main area customization

The main issue area could allow teams to define which sections appear and in which order.

Example sections:

- Description
- Business rules
- Acceptance criteria
- Steps to reproduce
- Expected behavior
- Current behavior
- Technical details
- Attachments
- Sub-issues
- Linked issues
- Activity
- Comments

Example layout:

Tab: Overview
- Description
- Business impact
- Acceptance criteria

Tab: Development
- Technical details
- Linked issues
- Sub-issues
- Pull requests

Tab: QA
- Steps to reproduce
- Expected behavior
- Current behavior
- Test evidence

Tab: History
- Activity
- Comments

Sidebar customization

The right-side panel could allow field reordering, grouping, and visibility configuration.

Example:

Planning
- Status
- Priority
- Assignee
- Due date
- Estimate

Business
- Customer
- Request type
- Business impact
- Approval status

Technical
- Module
- Environment
- External reference
- Version

Admins could also choose which fields should be pinned at the top.

Example:

Pinned fields:
- Status
- Assignee
- Priority
- Due date

This would make the most important fields immediately visible without scrolling.

Move fields between main area and sidebar

Some fields are too important to stay only in the sidebar.

It would be helpful to allow certain fields or custom field groups to be moved into the main issue area.

Example:

Business impact
Acceptance criteria
Customer requirements
QA checklist
Deployment notes

These fields may need more space than a compact sidebar field.

Activity and comment ordering

The activity/history section could allow layout preferences.

Possible options:

- Newest activity first
- Oldest activity first
- Comments at the top
- Comments at the bottom
- Separate comments from system activity
- Show only comments by default
- Collapse system activity by default

This is useful because different teams read issue history differently.

Some teams prefer the latest updates at the top, similar to a feed.

Other teams prefer chronological order, especially when reviewing the full history of a requirement, bug, or decision.

Comments position

Allow admins or users to choose where the comment box appears.

Possible options:

- Comment box at the top of the activity section
- Comment box at the bottom of the activity section
- Sticky comment box
- Comment box inside a dedicated Comments tab

This would improve usability for teams that use comments heavily.

Action button placement

The placement of action buttons could also be customizable.

Examples of buttons:

- Add comment
- Update status
- Assign
- Add attachment
- Link issue
- Add sub-issue
- Convert issue
- Archive
- Delete

Possible locations:

- Top header
- Bottom of the issue page
- Sidebar
- Floating action area
- Inside each tab

For example, teams that frequently update status or add comments may want those actions always visible.

Teams that rarely use destructive actions may want archive/delete moved to a secondary menu.

Per-project or per-issue-type layouts

Different issue types may need different layouts.

Example bug layout:

Main area:
- Current behavior
- Expected behavior
- Steps to reproduce
- Evidence
- Technical notes

Sidebar:
- Severity
- Environment
- Affected version
- Assignee
- Priority

Example feature layout:

Main area:
- Business goal
- Requirements
- Acceptance criteria
- Design references
- Implementation notes

Sidebar:
- Customer
- Business impact
- Priority
- Target release
- Owner

Example support layout:

Main area:
- Customer request
- Investigation
- Resolution
- Internal notes

Sidebar:
- Customer
- SLA
- Support priority
- Environment
- Responsible team

Layout templates

Plane could provide layout templates that admins can customize.

Examples:

- Default layout
- Bug layout
- Feature layout
- Support layout
- Enterprise requirements layout
- QA layout
- Minimal layout

This would make customization easier without requiring every team to start from scratch.

Personal vs admin-level customization

Some settings should be controlled by admins, while others could be personal preferences.

Admin-level settings:

- Field groups
- Required sections
- Project layout
- Issue type layout
- Sidebar structure
- Hidden fields

Personal user preferences:

- Activity order
- Comment order
- Collapse/expand sections
- Default active tab
- Compact or expanded view

Why should this be worked on?

The issue detail page is one of the most important screens in Plane.

Different teams use issues in different ways. A fixed layout works well for simple task tracking, but it becomes limiting for structured workflows, enterprise usage, support flows, QA processes, migration from Jira, and teams that rely heavily on custom fields.

This would help teams:

- Prioritize important information
- Reduce visual noise
- Improve readability
- Make the issue page faster to scan
- Support different workflows
- Improve usage of custom fields
- Make Plane more adaptable to enterprise processes
- Reduce the need for external documentation outside the issue

Expected result

Admins should be able to customize how the issue detail page is structured.

This should include the main content area, the sidebar, field ordering, field grouping, tabs, activity ordering, comment placement, and action button placement.

The result would be a more flexible issue page that can adapt to different teams, workflows, and issue types.