Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Retiring full-page issue create in Jira Cloud

TL;DR: The full-page issue create experience will be retired for all Jira Cloud customers over the next 6 months.

Hello Jira Community,

I’m Arbaaz, a product manager on the Issue Create team in Jira Cloud. I’m announcing today that we’ll be retiring the full-page issue create experience over the next 6 months.

What is the full-page issue create experience?

Currently, you can find the full-page issue create experience by adding /secure/CreateIssue.jspa to your Jira site’s URL. While this was never an officially supported experience for Jira Cloud, some admins and users may have set it up using this knowledge base article for Jira Server and Data Center.

Why are we retiring it?

We’ve been working on modernising the Issue Create experience to make it enterprise-ready in terms of performance, reliability, and scale. In this pursuit, we also researched legacy trigger points that are now redundant/duplicated and identified full-page issue create as one of them.

What does this mean for me?

When we retire the full-page issue create, its URL will instead open the new and modernised issue create experience. This means that you’ll still be able to create issues with the same URL, and any bookmarks to the URL won’t break.

Pre-fill fields in the new issue create modal

If you prefill fields, like the Summary and Description fields, in the full-page issue create experience, you can still do the same in the new issue create modal. Try it out by using the Behaviours - ScriptRunner for Jira Cloud or Dynamic Forms for Jira apps on the Atlassian Marketplace.

Give us feedback

If you want more space on your issue create modal — for example, if you want to expand it to full screen — please vote and comment on this open feature request so we can prioritise it accordingly.

To let us know how we can make the new issue create experience better, any problems you’d like us to fix, or any concerns in general, leave us feedback in the comments section below. We’d love to hear how we can help you.

Thank you,
Arbaaz Gowher
Product Manager, Jira Platform


Thanks for this article @Arbaaz Gowher  - i did not know of that URL, but will be sure not to use it :)

One thing, I wonder is if I click on the Create button or press c for a Service Management project, how can I limit it us the same fields as on the customer portal?

Thank you

For me, in the new issue screen experience, there are too many horizontal lines and boxes in which fields are shown... it makes the screen overly crowded. Especially if you have Assets/Insight fields.

This is a JSM ticket, with some Assets fields as it really shows:


In order to show how many lines and boxes there really are, I've exaggerated them below, in green:


For me, as a user it is just too much. It doesn't help. It distracts.... And this is only half of the issue.

You might say: but yes, you can hide details, and so on, but is it really necessary that just a couple of fields fill up the entire screen? Do we need all these lines and boxes? In this sense, the old issue view was soberer, cleaner and less crowded to show the same info.

Just saying....

Like # people like this

Hi @Yatish Madhav

That's a great question. We've recently updated the issue create experience in Jira Service Management. We now surface the portal experience (with the exception of "Hide with preset value" fields, which do appear). You can toggle this off if needed, but if the toggle remains on, the experience is largely the same as the portal. 

You can read more about it here:

Does this answer your question? 


Best regards,



Thanks for the link @Jehan Gonsalkorale  - I will read it and see if that does answer my question. I really hope it does :D

Like Jehan Gonsalkorale likes this


Log in or Sign up to comment

Atlassian Community Events