Introducing the new, streamlined Create experience in Jira

[#1]

Hi Jira Community,

We're updating how work items are created in Jira Cloud through the Global Issue Create button and wanted to give you a heads up on what’s changing.

Why this change?

Today, creating a work item from Jira Cloud’s top navigation Global Issue Create (GIC) button opens the large full form create screen. Over time, this screen has accumulated many fields – and today, the default form shows far more than what most users need for creating a typical work item. This leads to unnecessary friction: slower load times, a steeper learning curve for new users, and a flow that feels heavyweight even for simple tasks creation.

Instead, we wanted to design an experience that is easier to start with, and just as powerful when you need it.

---

What's changing?

We’re introducing a faster, redesigned create experience that gives you a focused quick-create flow by default, while keeping the full form available whenever you need it.

Before	After

Here’s what’s new and different:

 Window and Layout Control

The new modal supports two main modes - a compact Quick Create mode and a Full Form mode

• Quick Create form by default: The create dialog now opens as a focused modal showing the most essential fields – instead of the full list upfront. 

         

                                                           Quick form mode

• Full form is still available: You can expand to the full form anytime by clicking on the expand icon.

                                                 Full form mode

• Additionally, you can also dock the create modal to the bottom-right of your screen (similar to the old GIC). Docked mode lets you continue working on other tasks and return to finish creating your work item whenever you're ready – without losing your context or interrupting your flow.

                                                   Docked mode

 Info

While the Quick Create is the default mode for simpler work items, you will see the Full Form load automatically if your work item has more complex requirements - tabs, more than three required fields, custom create screens (CMP spaces), Forge UI app modifications, or a complex field type such as rich text.

 Main Input Area

• "Summary" is now labelled "Title" in the UI: "Title" more accurately describes what this field is – the name of the work item. JQL queries, API calls, and integrations referencing summary still work as before – this is only a UI label change.

• Description field is responsive : Expands vertically to accommodate long descriptions, code blocks, table edits, and pasted images.
  
                                            

              Exhibit | Responsiveness of create dialog with long code block

• Description field supports slash commands: Continue to use / in the Description field to insert elements or invoke Rovo. A formatting toolbar appears when text is selected
  
  

  Exhibit | Use `/` to invoke Rovo	Exhibit | Demonstrating Formatting       toolbar and More elements in `/`

Field Chips

• Required and optional fields are separated: Required fields appear first on the quick create form. Optional fields appear beside them. When there aren’t any required fields, the quick create modal shows only the optional fields.
  
  

• The order of fields in the required and optional sections matches the order set by admins in the space setting - with two refinements: fields that always have a system default (such as Reporter) and fields that a user rarely interacts with are excluded from the default view, keeping the form focused. These fields remain accessible via "Show more fields."
  
  

---

What does this mean for you?

A faster create experience

• A compact form allows us to load the create screen faster for you. In our internal testing, we have seen ~35% reduction in loading times.
  
  
  
  
• The quick create form allows for more focussed work item creation. No fields are being removed. The full set of fields remains available – they're just not shown upfront by default

Field visibility customization as a Jira user

• You can customize which specific optional fields appear — select More actions (•••), then Configure Fields, then choose Custom fields from the dropdown to pick the fields you want. Unchecked fields will be hidden from both the quick create and full form.
  
  

  ​

• You can also make Full Form your default. Select More actions (•••) while in full form mode, then toggle on “Always open in this view”. No admin action needed.
  
  
  
  

If you're an admin

You can control which fields your team sees by default in Quick Create via Space Settings.

                       

                                              Select Space Setting

• For team-managed spaces,

  1. Once inside Space Setting, select Work types.

  2. Select the work type you want to configure.

  3. Reorder the fields to control what your team sees in Quick Create. The Quick Create form always shows Summary, Description and upto 3 required fields – those are fixed. Beyond those, it picks the top optional fields based on the ranking below. For instance, if you want your team to see Team and Due Date in Quick Create, drag those to the top of the field list.
     
     
     
     

• For company-managed spaces

  • Once inside Space Setting, select the Screen corresponding to create issue and the targeted work type. Based on your configuration, you may find either (A) a single screen across create/edit/view issue operations or (B) a custom screen for create operations.

    (A) single screen for all operations	(B) custom screen for create                          operation

  • CASE A : Reorder the fields to control what your team sees in Quick Create.
    
    
    
    
  • CASE B : Having a custom create screen always opens the Full Form by default.

Note: Admins can also revert their site to the previous create experience via Settings > System > General Configurations, then set "Simple Create as Default" to off. This applies to the entire site.

                   

Note

1. With this change, other entry points in Jira that previously opened the older create form will now open the new modal – including inline creation in Board, Timeline, and Roadmap views (where the new modal appears when required fields need to be completed), and creating child items within a work item.
   
   

2. The new changes do not apply yet to Jira Service Management (JSM) and Jira Product Discovery (JPD).

---

When is this rolling out?

This update will roll out progressively to all Jira Cloud customers starting mid-July with the summer Jira release.

---

Questions or feedback?

If you have questions about this change or run into anything unexpected, please share in the comments below. We'll do our best to respond and take your feedback into account.

Thank you!

[Dave Mathijs]

Thanks @Kanad Dagaonkar Today, I learned a new acronym: The Global Issue Create (GIC) button. 💡

Are there any future plans on the roadmap to expand this to JSM and JPD?

[Julia Foden]

Hi @Kanad Dagaonkar 

Well I'm glad to see there is finally a Community post about this, but it has actually been rolling out since at least May. I gave my strongly negative views on it here and the Release Note says that it started rolling out in April!

The most important thing for everyone to know is that as admins we can switch it off entirely, as you said:

Note: Admins can also revert their site to the previous create experience via Settings > System > General Configurations, then set "Simple Create as Default" to off. This applies to the entire site.

My feedback:

• I'm glad to see that it now names the space and work item type rather than relying on icons
• Renaming Summary as Title is madness. What do you hope to achieve by this? Increasing speed is a valid reason for some of the changes (even though I don't like them), but I can't think of any valid reason for giving the Summary field a different name in the Create screen! I am forever telling people to take note of exact field names for the purpose of searching, reporting, dashboards etc. The Issue Navigator (JQL) uses Summary. It does not recognise Title. The field name is Summary - please change it back. And what about sites who have a custom field called Title?