A clearer, more focused Jira work item view is coming

[#1]

Hi everyone,

Starting 3 August, we’re opening a Beta of the redesigned Jira work item view: the screen your teams use every day to view and update work.

The redesign brings your most important actions and information front and center, reduces the steps to get common tasks done, and makes the overall experience clearer and more focused for every team, whether technical or not.

This is a UI and experience uplift, not a change to how Jira works. Your automations, extension points, field IDs, reporting, and integrations all continue to work exactly as they do today. The data and configuration behind your work items are unchanged.

 

What’s new

Key actions and information front and center. The layout surfaces what matters most and reduces clicks to get things done.

Inline control over related work: Add, edit, and manage child and linked work items in their own consistent sections without leaving the work item.

A cleaner, more usable activity feed: A unified history view with better-formatted updates and comments that are easier to write, sort, and act on.

Field personalization: Pin, reorder, and hide fields to match how you work, without affecting your teammates.

 

Unified attachments: Uploads, Confluence pages, Loom recordings, and web links all in one place.

Voice-to-text: Now you can capture your thoughts without typing. Speak and your words appear directly in the description and comment fields of any Jira work item.

  

How to join

No sign-up is required. From 3 August, admins can enable the Beta from Open Beta Features in Jira admin settings.

Once enabled, users on that site will see the new work item view by default.

Individual users can switch back to the classic experience at any time from the three-dot menu in the top-right corner.

We’d love your feedback

This Beta is an important opportunity for us to learn from customers before the experience becomes more widely available.

As you try the new work item view, let us know what’s working well, what feels harder than before, and what your team needs to feel confident using it every day.

Please share your feedback by replying to this post or using the feedback option in Jira.

Thanks for helping us shape a clearer, more focused Jira experience.

The Jira Cloud team

[Tomislav Tobijas]

Thanks for sharing this @Ahmud Auleear !

While some things are welcome on my side (e.g., field personalization, "See more", and voice-to-text), I do have some questions/comments:

• Details pane - The whole concept of having 'labels' for field names and values under it could be okay-ish if the right side is small in width, but as soon as you expand it, it feels really 'empty'
  I like the concept of having 2 columns - one for field name and one for values better
• There seems to be much emphasis on the 'automation' tab, and I don't think that will be used that much. Although this path with tabs leaves room for adding more things in the future. 🤔
• Attachments - It would seem like this area can become a mess really quickly. I/we do use Confluence content links (and more recently Loom as well), to quickly find and open linked content. Even though there's an option to filter attachments by type, this would feel like 'an extra step' to find something. 
• Status bar/icon - personally, I like the 'bigger button' (current one is okay) as status is one of the key elements that you look at when looking at work item. Potentially I would just need to adjust to the new UI, but I'm keen to see what others have to say about this.
• Linked items - I hope "Add existing" will be selected by default rather than "Create new." 
  From my experience, users mainly link existing items rather than create new ones.

All in all, it looks okay-ish, but I would need to actually test this out to provide more concrete feedback. 👀

Cheers,
Tobi

[Daniel Santiago]

In "Linked items" section, I think that "Add existing" should be the default option.

[Dave Mathijs]

Please enable the possibility to hide/remove the Agents panel/widget (and third-party app widgets) in the main area.

Also, the ability to create, edit, show/hide and remove third-party and custom field panels in the sidebar via Configuration (issue layout).

[zoltanersek _outpostlabs_dev_]

I like Inline control over related work, it saves me from having to open up a new tab with the issues 

[Rodolfo Romero - Adaptavist]

Can you bring back the explicit "Work type" (former Issue type) to the screen? It is very annoying having to hover over the work type icon every time I want to know the type of work I'm on.

[Todd Thomas]

Can we pin comments yet?

[James Rickards _SN_]

Please allow the ability to hide the development panel for spaces where it is not relevant.

[Yatish Madhav]

Thanks for this @Ahmud Auleear - overall, looks like a nice positive change. As much as I know some community members may feel too comfortable at times which makes sense too.

I agree with the comments added thus far. Quick thoughts/questions from me:

• I really like the highlighted Status section and the Status Category icon in there
• It would be nice to have a few more additional views to the Attachments in addition to the thumbnail and list view - perhaps adjusting the size (like explorer on Windows), adding a few additional details to list view, etc
• Not sure if this is new or why no one commented, but I love that summary sticks to the top! I would like if maybe just 1 line of the description sticks to so we can click to scroll up to read it, in cases of many fields in the center ... I wonder if anyone else has thoughts on this
• Agree that work item type text should with the icon
• In some of our cases, the right pane has so many fields it's tough to find the field - i think a quick filter like text search or field type search may also help. Eg if there are 50 fields on the right, which I know may not always be best practice but is a practice, how can users find the field. Thoughts?
• With the Automations tab on the right, for manual automation triggers (currently a lightening bolt) how would that look? Still a lightening bolt next to status or would users need to go to Automation to click it?
• When beta is rolled out, can i enable it just for a group or set of users or admins instead of everyone please?
• Would Voice-to-text be on all text fields? And on desktop and mobile app?

Thanks again for this @Ahmud Auleear  and the Atlassian team and well done

Yatish

[Josh]

@Ahmud Auleear

1. Will pinned fields support *all* types of fields (e.g. including Assets)?
2. Can more control be provided at the space-level to hide app panels (e.g. not every space needs Tempo)?

[Dave Mathijs]

Suggestion:

Please fix the UI of Assets Objects fields in the work item view:

Replace the hidious '+ Add object' in blue by the same design as other system/custom fields.

When a value is selected, it is surrounded by a border and misaligns with the other fields.

Make it fewer clicks, right now it takes:

1. Click '+ Add object'
2. Select or search for objects
3. Confirm or cancel

Users really get frustrated by this UI/UX.

[Ahmud Auleear]

Thanks everyone, this is exactly the kind of detailed, specific feedback that helps us build the right thing. Really appreciate you taking the time, and great to see so much of it building on each other.

A few of you have called out similar themes, so I’ll group them:
Linked items default to “Add existing”: Yes, that’s the default behaviour. When linking, it defaults to “Add existing.”

Work type text alongside the icon: Its a deliberate choice not to render the work type as text. It adds to the breadcrumb area, which is already tight on space. I know it’s a bit annoying, and it’s a genuine trade-off, but the broader direction is to lean more minimal: surface core actions, reduce clutter, and cut the “overwhelming” feeling a lot of people associate with Jira. In most cases here, less on screen is doing more for focus.

Finding fields when there are many: we’ll look into this. A future milestone is making every field findable via the command palette, so that becomes the go-to way to find and update a field when you’re dealing with a long list.

Automation tab: the entire automation experience now lives in the Automation tab, including the manual automation triggers.


Beta rollout scope : Beta is enabled for the whole instance. Individual users can opt out, and they’ll stay opted out for the duration of the Beta.

Voice-to-text: currently on the description and comment fields on web. We’ll explore other surfaces based on Beta feedback.

More control over panels: hiding/removing the Agents panel and third-party widgets, space-level control over app panels, and hiding the development panel is an area I'm exploring now. If you would like to discuss this, can you book a time in via this link to chat. 

For the feature requests here, the plan is to add them to our backlog and prioritise them alongside the rest of the Beta feedback. I can’t commit to timing on individual items yet, but nothing here is falling through the cracks, it’s going straight into our tracking.

Thanks again, genuinely, keep it coming.

Ahmud

[Sascha Weber]

Hi @Ahmud Auleear , 
I noticed 3 things:

1. Detail Panel, Pin a field as personal favorite - needing to click "..." and then "Pin Field" as the only option is one click too much. As long as there is only one option, offer the 📍 icon instead of the "...". The way it works now is great already!
2. Can we as administrators decide if the "Agent" zone is visible or not? Not every JIRA Space will benefit or have the need for an agent. So it may be misleading to simple-user-target groups
3. Having attachments, confluence Pages, looms etc all in one "Attachment" panel is really confusing. 
   
   1. If you go this way, then Attachments is likely not the right wording and will mislead users.
   2. If you introduce the change, equip it with a proper and representative wording. 
   3. I hope the E-Mail view for E-Mails attached via Outlook Plug-In will be integrated here as well? Even potentially offer great rendering for All E-Mails, independent of their origin! Manually uploaded e-mails do not benefit from uploaded emails via outlook

Thanks & BR

Sascha

[Rick Westbrock]

Is this going to roll out to JSM spaces also? I ask because a lot of recent changes to Jira were not applied to JSM spaces and that makes life more difficult for people who must work in both Jira and JSM spaces every day.

[Tobias Viehweger]

@Ahmud Auleear In regards to "More control over panels" I would like to chime in as an app vendor. I always see discussions around hiding app panels and the like, unfortunately I also see the other side where it's getting harder and harder for our customers to make sure the app panel is actually visible, consistently (e.g. see https://ecosystem.atlassian.net/browse/FRGE-1513). The same applies to app buttons, which have been hidden behind a dropdown, with no option for any customization. 

I think there are different needs across your customer base, where customers would very much like to have customizability for these things, not just "hiding them". We already built customizability like this into our apps, where customers can configure panel visibility, I'd very much like to see these things in Jira itself, although in both directions, making sure that where apps are part of a core workflow, they can be made so on the UI as well. Happy to talk in case you'd like the vendors perspective as well!

Thanks

Tobias

[Josh]

+1 for @Rick Westbrock's comment about the growing UI divide between Jira and JSM. It's becoming mentally jarring for users of both apps as they switch back and forth throughout the day.

@Tobias Viehweger you make a fair argument about app panels. It's a delicate balance between keeping the UI "clean" and ensuring that users have the necessary functionality visible. Some Marketplace vendors have been a bit aggressive in making their content visible within the work item view, even in situations where the app is irrelevant. Not every vendor is like that though. Granular customizability (e.g. at the space or work type level) is usually something admins appreciate and it sounds like app vendors may be supportive of that approach as long as there is careful consideration of impacts to apps.

[Becker_ Rene]

I did not enable the Beta because we only have 1 instance and my users are very fragile when it comes to changes. Since we only have the standard license, Sandboxing also isn't an option.

What I see from the images though, is that there are no classical form screens tabs in the center.

Are you removing classic form screens?

Why am I asking:

We use Jira to handle our customer projects. They are created via API when our CRM reaches a certain status with the orders.

Layouts had drawbacks:

- No central configuration per project (as form screens could be administered centrally) and no API either

- Layout was so cluttered that many users just gave up

- form screens allowed for tabs, which helped to structure data (as you may imagine, a customer project task may have many fields that are needed in a task)

That is, why we chose classic form screens:

- can be rolled out globally via schemes

- data can be structured centrally (creating a standard over all projects -> allow to train users)

- no extras like automatically hiding fields

- no involuntary fields like development

----

Can you please provide info on that topic?

Thanks

Rene

---

[Julia Foden]

Hi @Ahmud Auleear 

Echoing @Becker_ Rene 's question about whether we will still be able to use tabs in the central part of the screen. Tabs are important when there are many fields - they reduce the visual clutter on first viewing the work item but still allow users to access the data if required. And the tab names guide users to where they can find the field.

Also, your images show only the Description in the central part of the screen and all other fields in the right hand column. What about multi-line text fields?