Hi, per https://jira.atlassian.com/browse/JRACLOUD-73660 I am still seeing checkboxes on my "create" screen in my Jira cloud instance even though I have selected a global field type of multi-select. I've tried this several times without fail. Am I doing something wrong to get a global, multi-select field to show up in the create view the same way it does in the view screen? I can't add attachments, but it shows up as a regular multi-select in the View screen, only displaying the selected options. In the Create screen it shows every option...

Try [TaskCompose for Jira Cloud| https://bit.ly/3pK1cO2 ]. It's a Chrome extension. It allows you to create a task in Jira from any browser tab with a convenient editor. You can also take screenshots and add annotations to them. You can also perform basic operations with web elements on the page.

I hope you find it useful!

Hello @Jira Cloud Team,

I believe my issue is a bit different from what's described here... I'm actually attempting to have a table displayed within a custom 'Paragraph' type field I've created and added to the 'Create, Edit, and View' screens of multiple issue types. I've already attempted to use both RTF and Markdown formatting to no avail. Can you or anyone else on this thread tell me how I might accomplish this if it is even feasible at all? 

Below is how I ideally want this table to look on all the screens when viewed by users.

When using the "Create Issue In Epic" button on the Epic Issue Screen, the editor that pops up after I enter the summary (it pops up because we have a required field), the editor used is the old Wiki Editor.  

I am sorry, but it seems that the new editor was not implemented in all create-issue screens !

When I navigate to this page of my cloud instance, then I get the old editor:

https://<mysite>.atlassian.net/secure/CreateIssue.jspa

The new GIC has been rolled out to 100% of users

Customer is losing their summary when switching from Issue Type in the Create Issue modal. 

https://twitter.com/joachimnicolas/status/1514221583757365253

dc7c78296a7c any update on the transition screens or somewhere we can follow along for those? They are much more important for our use-cases than create screens since we need to be able to know which editor is being used for comments (formatting implications in Canned Responses) and methods for adding attachments to the comment.

Creating a version in the "new issue view" is not working as in the regular "new issue view" described here JRACLOUD-73256 Allow users to create new Versions directly from the new issue view - Create and track feature requests for Atlassian products.

Hi Atlassian,

What is the status for this implementation?

Regards,

Nadica

i need text formatting for table on jira cloud

(https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all) 

@mwren, I had noticed a problem where the cursor-right key jumps out of the Description field.  Did you use the cursor-right key, perchance?

The description field on the Create Issue screen loses focus after I type 1-3 characters. I can't enter a description. The most important field when creating an issue is broken...

> the issue of tabbing from the "subject" text box to the "comments" text box

This! A thousand times this. I get that they should be accessible via the keyboard, but if you are focused on the field before and press tab, obviously you want to go to the next text input, like in any other form on the web. Jira should be all about making it easy to input new tickets. Seriously, how did this get past QA? 

Almost as bad is that you need to click on a very specific area in the comments text box for it to actually focus. If you click (visually inside the border) but too far down, it doesn't focus! You need to click in about a 16px high area inside the 90px high boundary! That gets me as a serious wtf almost every time (and I usually try to click into it due to the tabbing issue).

This is all completely understandable. After all, creating new tickets is an edge case that most individuals and organizations will rarely encounter with a product like Jira. Ahem.

I'm surprised no one has talked about the issue of tabbing from the "subject" text box to the "comments" text box. Instead of bringing you to typing text it cycles through all the elements of the WYSIWYG text editor. I've had multiple users complain about this.

@Adam Charron

Update: The day after I posted this the feature is now available on my companies cloud instance. If someone on the Jira side saw this and enabled it, thank you. Glad to have a consistent UX again.

I have some kind of similar experience. I raised support ticket on Friday. Yesterday, on Tuesday, support guy responded to me asking for details and screenshots - and issue magically went away in the next hour. I did change settings a lot during that time, though (trying to recall how do things work here and there), so I'm not even sure, maybe it was me who somehow caused the result.

In any case, "create issue" screen is finally OK for me, but "resolve issue" screen still has old interface I'm not sure, if it's ok or not currently - just posting it here in case magic works this way indeed

Is it possible that CreateIssue.jspa has been forgotten? Here, the old editor is still being used...

When I create a ticket with the "create" button of the main menu, then I have the new editor.

But when I load the CreateIssue.jspa screen, then the old editor is still there. (my URL to this is https://<mycustomer>.atlassian.net/secure/CreateIssue.jspa )

I'm a fullstack developer and maintainer of a few generations of text editor for the product I work on, including older text based BBCode, Markdown, and "kind of WYSIWYG" editors, and a new "Rich" editor similar to the Jira's new editor. Jira's new editor handles a couple of things worse than our implementation, and a few things better. Overall I like the new Jira editor quite a bit though.

With that said this has to be one of the worst feature release cycles I've seen:

• The new issue view came with a new text editor. Instead of having the editor be its own feature/configuration it was bundled into a rebuild of the pages that has lasted over a year.
• Some people don't like the new editor due to disruption of various workflows and a few shortcomings. Instead of letting admins configure which editor it is tied to these new pages.
• The editor and the create view are two totally different implementations for some reason. This results in a disjointed release cycle for the 2 features.
• The new edit view with the new editor is force enabled ** before the new create view is even available to turn on.
• Finally after months of forcing users to use 2 different editors (with no way to have a consistent editor between the 2), an announcement is made that they will both be unified and a date is given.
• We blow right past that date and still aren't even offered a configuration setting to opt-in.

My team has been moved over to Jira relatively recently and this has been an overall very janky experience.

There are a few ways this could have been rolled out better:

• Change the editor in both places separately from the pages.
• Leave both feature flags as optional until they were both ready.

Even though I like the new issue view forcing it out before the new create view is even available seems like a poor decision. It breaks the UX of a user significantly and forces to people to learn 2 editors at once.

Update: The day after I posted this the feature is now available on my companies cloud instance. If someone on the Jira side saw this and enabled it, thank you. Glad to have a consistent UX again.

CREATE Issue form called from top of the page is indeed updated.

But what about create issue called as for Epic issue or for subtask? Those are the same forms (please do not say opposite)

How much time it will take to refine those ones? Next  2 years?

Good for you, @alexandr

Hi. My another comment is here: https://community.atlassian.com/t5/Jira-articles/Announcement-New-Issue-Create-modal-will-be-available-to-all/bc-p/1932188#M6117

The announcement says:

we are happy to announce that the new Issue Create will start rolling out to all customers starting 6th December 2021. As this is a key experience for our users in Jira, our rollout is going to be a cautious one so that we can closely monitor key stats and usage. We expect the rollout to be completed by the end of January 2022.

My interface for issue creation still differs for issue editing. Does it mean, that rollout is still in progress (not finished), or am I missing something?

Hi Everyone, 

We are happy to announce that we have begun the rollout of the new Issue Create modal. More details here - https://community.atlassian.com/t5/Jira-articles/Announcement-New-Issue-Create-modal-will-be-available-to-all/ba-p/1874003

Thank you for your patience.

Regards,
Arjoon Som
Sr. PM, Jira Cloud

Hi ea582e71db54 The work on the modernization of transition screens is scheduled to start soon after the rollout of the new Issue Create modal.  I'll share more information on this once it is available. 

Thank you

Arjoon Som
Sr. PM, Jira Cloud

How close are the transition screens?  Will they be rolled out with the Create modal?  Those are very disruptive to the user experience and do not have any work-arounds.

I shall now cease holding my breath

Finally! Thank you!
It was an active showstopper in getting acceptance for the whole product in non-tech areas of my company.

I really like a lot of the functionality and features of Jira but please keep in mind to get the basics right. Otherwise it's like trying to sell a car with all thinkable technology options but with no way of getting in without hitting your head hard every single time

So ... looking forward to the rollout
Best regards

Yay - bring it on!

Hi Everyone,

A quick update. We have completed our Beta testing of the new Issue Create modal and the results have been very positive. We are now planning to roll out the new modal to all customers starting December 2021 through January 2022. The new Issue Create modal will be consistent with the Issue View modal in terms of markdown support. 

Thank you!

Arjoon Som
Sr. PM, Jira Cloud

Please implement this asap. It's these in consistencies that business user are frustrated about and makes the life of a Jira admin and/or solution partner very hard when working with non-IT staff.

Atlassian's answer to everything is to always add more complexity and mix up all the documentation.

I (my team) need this asap. 

Hi There - I'm working on migrating to the cloud from server, and in following through our workflows and screens, to make sure the experience is the same, or making note of differences, I noticed that for new issues that are still on the create screen, Markdown (or wiki markup?) appears when a user clicks the bold button. Instead of making it "bold" like it does in an existing edit screen, it makes it ***bold*. Many of our users are not technical folks (marketing, designers, business), they think this is a mistake and then delete the mark-up.  If I'm reading all of this right, in the cloud instance, there's no way around this. This, at this point, is the way it is.  Is that correct? We only have 25 users, so we wouldn't qualify for any beta programs

Hi dc7c78296a7c, I know that you mentioned this briefly in one of your past comments, but is the work to address the upgrade of transition screens still slotted for slightly after the create screens?  Our users are far more interested in the transition screens having the New View.  Is there a different Jira issue that we should be following or will this one only be resolved when both the Create and Transition screens are moved into the New View?

Hi Everyone,

We still have a few slots available for our new Issue Create Phase-I Beta program. For those who wish to use the new Issue Create with the updated Atlassian Editor for fields such as description and other multi-line fields, I would urge you to kindly sign up so that we can make it available to your instance early. If you do not exactly match the ideal criteria for the signup, I would still recommend that you indicate your willingness to participate so that we can evaluate your instance for minimum criteria. 

Please go through the post above for more details. If you have any questions, please do comment on the community post and we will respond to you at the earliest.

Thank you!
Arjoon Som

Sr. PM, Jira Cloud

Hi Everyone, 

We are happy to announce the Phase-I Beta program of the new Issue Create experience. The new Issue Create has the new Atlassian editor and a bunch of other features and performance optimizations. For more details, please read this community post https://community.atlassian.com/t5/Jira-articles/New-Issue-Create-Experience-Phase-I-Beta-Program-signup/ba-p/1735393#M4839

This post will also give you a good understanding of how far the development has come along. If you would like to be a part of the Beta program, please read through the post and then comment your willingness to participate. 

Thank you!
Arjoon Som
Sr PM, Jira Cloud

/date (hmm macro not working) -> 

26/Feb/2021 - last update.

Progress on this? 

Also expected the editor when creating tickets to be updated with the new release/layout.

Hope it will be considered and worked on asap.

+ 1 to the comments. Its so strange that this was not fixed when releasing the new editor 

BTW: "Please be assured that we are actively working on this project and will continue to share updates. " --> After 4 months it would be nice to get an update. 

I'm glad this is carded, but frankly it's 2021 and this archaic and clunky screen is the number one touchpoint for a good chunk of users. I don't understand how a company that considers itself at the forefront of project tooling can treat this sort of user experience as acceptable. (Actually, I do, it's called incompetent leadership and management)

• A two year old incomplete ticket
• For a wildly important interface
• That would have been considered substandard 10 years ago

Remind me in 20 years to check to see if every JIRA page is still making 300 AJAX requests.

This is causing issues when trying to copy/paste formatted text from an existing ticket into a new ticket being created. All of the formatting (bullets, bold text...etc) is dropped. 

+1 from me as well.

Not having a user friendly create issue screen makes the whole product loose (or not even initially get) acceptance by our not so technically experienced users. I was just planning to introduce Jira with the new work management features to our markerting and sales department but as I realized that this simple but more than annoying issue still exists and will not be solved for another half year (at best), I was really (really!) disappointed. That way I will have no chance to get user acceptance for it and thus need to look for other options.

With this issue being on the list here for more than 2 years already and the availability of a fix not before end of this year ("best-case scenario"), I can only state that this is clearly not my understanding of "remove our customer’s frustrations and impediments".

I understand that a long term solution with clean overall architecture is the goal. And it's a good one! But not addressing most user's needs in any way in the meantime will likely cost you even more customers and reputation on the way. Please take this into careful consideration and provide a quick solution for the biggest pain as stated above so many times.

If you break your leg, you understand and accept that you cannot get final treatment right away where it happened but instead go to a hospital for it. But you expect some intermediate help from a medic at the place of accident and not being told "just walk to the next hospital, you will get your treatment there". The imagination alone hurts and so does this issue here. Do something against the pain, please!

+1 To Andrew and Matt. I just want the same text editing experience in create and edit. Seems like a simple ask, and frankly, part of an MVP for creating a new editor in the first place. As it is now, I usually just create stubs and then head on over to the edit view so I'm not struggling with different displays, hotkeys, and available functions. 

That this wasn't done initially and that it has taken this long reflects very poorly on Atlassian.

+1 for being agile and just delivering a consistent "Description" editing experience by using the new text editor in the "old" create view as an MVP/phase 1 release.  

Maybe it would have resulted in some throw away work, but you would be resolving the single largest pain point tactically with relatively low risk (and I imagine) effort, giving you much more runway and time to complete the more strategic and complex long-term transition.  

Though I can appreciate wanting to fix tech debt and make for an overall better/consistent experience, it seems a bit of a missed opportunity to have wrapped such a simple "quick win" into a massive, 12+ month and very risky project.

I completely understand what you are saying Arjoon, but this only shows how detached Atlassian has become from its users. To think it is acceptable to change something so key everywhere but one core area for several years speaks volumes to the poor decision making at Atlassian.

We, the customers, are all paying for your product and just because something "would require an inordinate amount of effort because of technical reasons and stack differences" is not our issue, that is your issue, and it should have been thought about before ploughing forward with changing it everywhere else.

I think it is a particularly silly issue to have lost customers over, but I'm afraid for us it was the straw that broke the camels back and we have migrated elsewhere now. July/Aug 2021 for EAP, so probably 6 - 12 months later for GA, is simply too long to wait.

Thank you for the ongoing transparency on this effort, @Arjoon Som.

Hi Everyone,

Apologies for the late response. I am currently on carer’s leave and have limited access to JAC. I’d like to thank everyone here for your responses and your thoughts on this matter. Please know that we hear you and we take your feedback very seriously. I’d like to provide some more clarity and an update on this project.

david.stokes1221510987 & greg.draper310998593 - For now, the focus is on the create modal and not on the transition screens but there are plans (but not confirmed) to revamp those screens as a follow-up to the create modal. I expect those to follow suit quickly because most of the important groundwork would have already been completed as part of the create modal revamp.

5224784fa7e3 , david.biesack1 & pdame1152700862 - Yes, you’re absolutely right. We understand that a large part of our community does not want a rewrite of the create modal and wants just the editor to be replaced. However, our thinking here was how do we solve for the customer long term. @G has actually come pretty close to some of the primary reasons why we decided to go with a full rewrite (kudos to you ). As we moved ahead as a product, it became very clear to us that we needed to step away from the code base that powers the current GIC in order to ensure that we can convincingly support the future needs of our customers in terms of functionality, performance, scale and also very importantly, for consistency of experience across Jira. Would it have been possible to just force-fit the new editor onto the old Issue Create modal? Yes, but it would require an inordinate amount of effort because of technical reasons and stack differences. Honestly, it would have been an implementation that our team felt would not make for the most optimal user experience.

Please know that our primary motive here is to remove our customer’s frustrations and impediments but with the caveat - we solve for the long term. The move to a modernised stack was inevitable because we anticipated that a time would come very soon that customers would need something very important and we simply wouldn’t be able to deliver it quickly because of the limitations of the current stack. I firmly believe that what we are doing now (although painful) is good for our customers and for the product overall. I hope I have managed to convince you too.

Lastly, I would like to give you an update on our timelines. As I mentioned before, we take your feedback very seriously. I am happy to share that we are internally working to expedite this project and to have something for our customers sooner. Our teams are working to release the new Issue Create experience sometime by the end of this calendar year. PLEASE understand that this is our best-case scenario. We have done our best to parallelise the work to bring forward our timelines but with it, comes more uncertainty and risk. Hence, these timelines may be subject to change. I will continue to provide updates on the progress of our work so that you are aware and can plan accordingly. We also have plans for an Early Access Program and will share more information with the community on this sometime in July/Aug 2021.

Thank you.

Arjoon Som
PM, Jira Cloud

@Arjoon I'll re-re-echo Andrew's comment. We only want the same text editor UI component that is used when editing the issue. Nothing more. I see no reason that cannot be incorporated given one can edit the issue description a second after it is created. Just swap the component.... PLEASE just expedite that one change. It would indeed make a world of difference. This cannot wait another year or more - it's insanity.

@Brandon, this is not quite right: we're using a Next-gen project and the "Create new Issue" button brings up the old editor.

As a workaround we're not using the create button any more and do create new issues directly from the backlog list view, then being able to use the modern editor right away.

I am quite disappointed that this will take so long .. mid FY22 WTF??  .. I do fully agree with Andrew's comment here!

Wow, two more years before the the rich text editor will be working on issue creation in Classic projects?! It already works like this on the Next-gen project. Well, at least we know it's on the roadmap...

FYI, regarding your sentiment here, a couple of years ago when Atlassian just dropped us all into the New View for full issue view and wouldn't let us control it for users as an Admin (nightmare fuel), I asked why they would even be working on this when we all were fine with the experience and really wanted other real problems fixed instead.  I was able to learn that one of the big problems with the old view code is that literally every issue screen is/was siloed in the code (create, transition, board, etc.).

I don't have access to their code and cannot fully understand the challenge, but it seems like something with the monolithic structure blocks them from making edits (or everything will fail with the functionality).  So they are completely rewriting the functionality and cannot repurpose what they have already done (I think it is a valid argument that this re-write still could be done much faster).  But I think Atlassian is trying to make this more stable in their infrastructure.  I am making assumptions here, but when they launch the new create screen it will probably have micro-services that are tied to the same functionality in the other views.... so in the future if they want to provide better functionality (e.g. let us create a new portal-only Reporter with a display name directly in the Reporter field, they would code that, QA it in one place and know that it now applies everywhere across their service... create screen, transition screen, full issue view screen, service desk portal screen, board screen, mobile app screen, Mac app screen, etc.).  Feel free to correct me, Arjoon.

I really just wish that Atlassian would be more transparent about this if it is true (the Marketing people don't seem to understand how savvy we all are).  That is why I commend Arjoon on his message here... because he addressed that it is a full rewrite and gave us helpful details.  He also said that they are looking for ways to speed this up and I have noticed the performance improvements across my instances (that is always appreciated).  Hopefully we can help get this shipped faster!  

I'll echo Andrew's comment - I think the vast majority of us are not asking for or expecting an entire rewrite of the experience. We just want the Create Issue page to use the same text editor UI component that is used when editing the issue. If nothing else change, that one fix would make the experience soooo much better. Please?

@Arjoon - Thanks for the update, but I think Atlassian has missed the point with this whole thing and many other issues like this I've seen over the years. No one was asking for a "whole new experience" for creating issues, we just wanted the existing issue create experience to have the same editor as the edit issue experience. Essentially, when you replaced the editor, it should have been replaced "globally" and not just in one place, giving this inconsistent experience. If this wasn't possible without creating a new "create issue experience", then the editor shouldn't have been replaced on the edit screen until it was possible to have the same editor everywhere. To me, this shows a fundamental misunderstanding internally at Atlassian to what makes for a good user experience, and as I said, it isn't the first time. With tools like this, consistency in experience is really important, particularly for "power users" and I'm afraid that Jira Cloud, which just seems to have random updates thrown at it with much consideration for the end-user, just doesn't offer that and for us is no longer "fit for purpose". We are migrating elsewhere.

Yes, thank you so much for updating us like this. We really appreciate the transparency and want these things to be shipped as soon as possible. Please let us know if we can help in any way (as David said).

I am also interested if you plan to upgrade the transition screens and the create linked issue screen at the same time as part of the same code. Those are far more important since there is no effective workaround to leverage those functions.

I have some questions on possible new functionality too. Finally I’m wondering if we will be able to exclude comments from the transition screens as a part of this update.

Thanks for the update Arjoon.  Please let us know if you have any questions or want us to test it - we all want to see this work well for us and our customers.

BTW - while we talk about the Create Issue screen, note that screens that open as a result of a workflow transition suffer from the same problem, so I'm hoping that those screens are included in this update.

Thanks

David

Hi Everyone,

We'd like to give you an update on the progress of the work regarding the new Issue Create experience. The project is firmly on track and the team is working towards completing the project on time. We are also exploring avenues internally to expedite this work in order to hopefully roll this out to customers sooner. We'd like to reiterate that we are fully aware of the inconveniences the existing Issue Create causes to our customers and we know that it is not the most ideal experience. We are working towards solving most of the problems that have been raised. 

The reason why this project is time-consuming is because of the need to build this experience from scratch in the backend and also to ensure that we support the staggering number of fields that the existing Issue Create experience supports. We do not want to roll something out to customers that will only be able to support a small subset of the fields and issue types that exist on their instances/projects. We predict that this would lead to even greater levels of frustration for our customers. 

Some of the key improvements you can expect from the new Issue Create experience are:

• A game-changing improvement in performance and reliability. The new issue experience will be fast and also fast at scale.
• The new editor will be integrated into the new Issue Create experience which will be in line with the Issue View experience. You will no longer have to skip entering the description field during the creation of an issue. 
• Look and feel parity of other fields on the new Issue Create when compared with Issue View
• A simpler attachment upload functionality
• Adding the option to add certain fields onto the Issue Create form that was not possible before (we are still investigating this)
• We have also taken cognizance of certain improvement suggestions from this thread and others and assure you that we will attempt to incorporate these suggestions into the new experience as well
• Other minor, but important improvements

Over the course of the past few months, we have also made backend improvements to the performance of the existing Issue Create experience. Our data shows that now the existing Issue Create loads, on average, 34% faster for our customers. 

Please be assured that we are actively working on this project and will continue to share updates. We thank you for the patience shown so far and ask that you continue to bear with the current experience for some more time. 

Thank you

Arjoon Som
PM, Jira Cloud