Issue Summary

The customer has raised concerns about the current Jira Cloud UI experience, highlighting the following key issues:

• Excessive blank spaces and inefficient use of screen real estate in the issue view.

• Cluttered information below the issue description, including unnecessary plugin sections.

• Inconsistent and cumbersome navigation, particularly for accessing Project Settings and other admin functionalities.

• Lack of organisation in starred items and dashboards.

• Unrestricted team creation and unnecessary visibility of the Apps section for non-admin users.

• General concerns about rushed updates and the lack of critical features like assigning issues to groups.

These issues collectively impact the usability, clarity, and efficiency of Jira Cloud for admins and end-users, making it less intuitive compared to Jira Server.

---

Feature Suggestions

1. Field Layout and Spacing

• Reduce excessive blank space in the issue view on both the left and right sides to better utilise screen real estate.

• Minimise the gaps between fields like Assignee, Reporter, and Request Participants in the right-side column for a more compact and efficient layout.
• Ensure fields with long names (e.g., custom fields) are displayed on a single line wherever possible, rather than wrapping over multiple lines.

---

2. Cluttered Information Below Issue Description

• Reduce unnecessary clutter in the issue view, particularly below the issue description.

• Hide unused plugin sections (e.g., Tempo, Personal Notes) by default and only display them when values are entered.

• Move plugin sections like Personal Notes to a less prominent location (e.g., under the Details section) to improve transparency and focus.

---

3. Navigation and Accessibility

• Simplify the navigation process for Project Settings. For example:

• • Provide quicker access to Project Settings with a single click, similar to the Jira Server experience.

• • Eliminate the need to open the navigation pane, locate the project, click three dots, and then select Project Settings—streamline this process for admins.

• Improve the visual structure and consistency of the navigation pane:

• • Clearly differentiate main menu items from sub-items to avoid confusion.

• • Reduce unnecessary clicks and inconsistencies in the navigation experience.

• Allow role-based customisation of the navigation pane to make it intuitive and tailored for different user types (e.g., admins, project managers, or team members).

  ---

  4. Starred Items and Dashboards

• Add tabs within the Starred Items section to separate Filters, Projects, and Dashboards, making it easier to organise and locate items.

• Allow users to customise the order of dashboards to prioritise their most frequently used ones.

---

5. Team Creation and App Management

• Restrict the ability to create teams to organisation admins only, as unrestricted team creation can lead to disorganisation, especially in companies that don’t actively use this feature.

• Manage the visibility of the Apps section via permissions, ensuring it is only visible to org-admins or users with specific roles, reducing unnecessary clutter and confusion for non-admin users.

• Ensure that app management is intentional and purposeful, rather than being overly accessible to all users by default.

---

6. General Feedback on Updates

• Prioritise real user feedback and testing before rolling out significant changes or new features to ensure usability and quality.

• Address longstanding requests, such as assigning issues to groups, which many users have been waiting for.

• Focus on maintaining clarity and transparency in UI updates to avoid overwhelming users with unnecessary or cluttered information.

  ---

  Expected Result

• Jira Cloud UI should provide a streamlined, user-friendly experience by addressing the issues outlined above.

• The layout should be clear, compact, and focused on the most relevant information, minimising unnecessary clutter and blank spaces.

• Navigation should be intuitive, consistent, and tailored to different user roles, reducing the number of clicks required for essential actions.

• Features such as team creation, app visibility, and dashboard organisation should be intentionally designed to improve usability and control for admins and end-users.

---

Actual Result

• The current Jira Cloud UI introduces excessive blank spaces, unnecessary clutter, and inconsistent navigation, which slows down workflows and reduces transparency.

• Plugin sections and unused features take up space even when they are not actively in use, adding to the clutter.

• Navigation requires multiple clicks and lacks clarity, making it harder for users (especially admins) to access essential functions quickly.

• Long-awaited features like assigning issues to groups remain unavailable, and updates sometimes feel rushed without sufficient user testing.

---

Workaround

• There is no current workaround to address these issues. Users are limited to the existing Jira Cloud UI experience, which impacts efficiency and usability.

  ---

  Conclusion

The suggestions outlined above aim to address the customer’s concerns and improve the Jira Cloud UI experience by making it more user-friendly, efficient, and aligned with user needs. These changes focus on enhancing clarity, reducing unnecessary clutter, and streamlining navigation and workflows for all users, especially admins.

By implementing these improvements, Jira Cloud can provide a better experience for both end-users and administrators, ensuring that productivity and usability are prioritized.

 Note: Legacy automation is not available in new Jira Service Management sites. Learn more about legacy automation