Issues are the fundamental building blocks for teams to capture and coordinate their work and get things done in Jira Software. Over time we’ve added more functionality to the issue experience in order to meet an ever-growing variety of needs beyond bug tracking–needs that range from Agile software development to tracking medical research to establishing legal processes.

However, the same power and flexibility that has led to Jira issues being customized to meet the needs of millions simultaneously brought unwanted complexity for many teams. And many of you told us directly through support tickets, emails, in-product feedback, user interviews, and other channels that Jira issues are often too cluttered with information and confusing to use. Moreover, you told us that your teams were constantly experimenting with new ways of working, and that Jira issues weren’t adapting to the needs of your teams fast enough.

So from improving the subtask experience, to making the process of linking issues more intuitive, to providing richer context and more realtime development information, we’ve been heads down working to remove the friction for the most common actions on Jira issues. Here’s a sneak peek into our progress.

A better way of working

We’ve begun rolling out the new issue experience for Jira Software Cloud, in a direct response to all the feedback we have received from customers, the breadth of use cases that we have seen… and a healthy serving of how we, as Atlassian, see the future of work.

Below is an overview of the issue experience that we are starting to share with some customers, learning and iterating as we go. This feedback loop allows us to ship improvements daily based on the ongoing feedback. If you haven’t yet seen this update within your Jira Software instance, it might be because you use some features that are not currently supported. Regardless of whether or not you’ve had a chance to experience our new issue design, stay updated on our progress here.

Focus on what matters

The new experience has completely reorganized disparate information on an issue into a simplified architecture that scales to meet powerful use cases. This means you get to keep all the power and flexibility of Jira Software while still being able to easily read through and understand what needs to be done.

We’ve also simplified how you view and add contextual information about a specific item of work, or an issue. All the fields configured for a specific issue type are available in the right column, with key pieces of information or fields that already have values displayed above the ‘Show more’ line.

This lets you quickly focus in on the relevant information for that issue. By clicking on ‘show more’, you can see all the fields and quickly add values. By giving value to a field, it automatically gets placed above ‘show more’ the next time someone views that same issue. This means that issues better represent the true work at hand by elevating information that’s been filled out and hiding information that may not yet be relevant.

Key actions are now frictionless

Good design includes understanding and making the right trade-offs. We’ve given prominence to the top actions that are performed on an issue and have taken this opportunity to improve upon them (or in some cases, drastically rethink how they should work).

This means that describing and adding content to your work, progressing it through a workflow, and collaborating through comments will always be easily accessible in consistent locations with consistent interactions whenever you may need them.

Stay in context of your work

Your work does not happen in a vacuum, which is why it’s important to have the context of where your work fits in with everything else going on. You can view all the information about an issue without leaving the board, backlog, issue navigator, or even Bitbucket (if you have that integration set up).

Even better, we allow you to perform all the different actions right from the issue. You don’t need to navigate to random places in the app when trying to do things like move an issue, create a subtask, or monitor realtime development information.

Work smarter and faster

We are working to ensure that the issues experience balances consistency with flexibility. It is consistent because the information structure and interactions will remain the same and should be familiar to you no matter where you are in Jira Software. It is flexible because anything within that framework is free to configure and experiment with, allowing for an almost infinite set of issues that can map to how your team works.

There is also a new rich WYSIWYG text editor that makes it much easier to write beautiful content so that you can better articulate your ideas. And by docking comments to the bottom it’s now easier than ever to instantly join the conversation.

So, what’s next?

Jira is known for being extremely powerful and giving teams a tremendous amount of flexibility to map the tool to their unique process. We’re focused on marrying that power with an experience that makes it easier to use issues to collaborate with your team and get things done. Many of you have already shared feedback on this new experience, feedback that we’ve used to further refine and improve the look and feel of Jira issues. And we’re just getting started.

We look at user feedback every day. It helps drive our understanding and decisions, and we are always eager to get more. Please share your feedback by clicking on “Give Feedback” at the top header of the issue view itself. We look forward to hearing from you!

A sneak peek into the future of Jira Cloud issues...