• 102
    • 151
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Atlassian Update - 13th Jun 2022

      Hi Everyone, 

      As informed earlier, the new Issue Create experience has been rolled out to 100% of our users in Jira. Additionally, we have recently announced that the process to deprecate the legacy Issue Create experience will begin this month. 

      We are also actively monitoring feedback and resolving any bugs our customers are reporting and you can find the latest updates to the fixes https://jira.atlassian.com/browse/JRACLOUD-77212

      As the primary goal of this ticket has now been achieved, we are going to close this ticket.

      Thank you.

      Arjoon Som
      Sr. PM, Jira Cloud

      Summary

      When creating an Issue in Jira, text Wiki renderable fields such as the Description field are displayed in text mode which does not format the markdown syntax. This happens because the Create Issue screen still uses the old view.

      This means that on the Create screen, you're seeing a bunch of symbols (+,*,-,{) and need to rely on knowing the syntax and seeing the output after creating the issue or by changing the field to "view" mode.

      bold
      italic
      colour
      strikethrough

      Suggestion

      Apply the new Jira issue view in the Create Issue screen so the formatting of the Wiki markdown is clearly visible.

            [JRACLOUD-71890] New view on Create Issue screen for Wiki Editor

            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...

            Michael Gardiner added a comment - 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...

            Ostin Hops added a comment - - edited

            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!

            Ostin Hops added a comment - - edited 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.

            Name Type Notes
                 

            Marq Herrod added a comment - 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. Name Type Notes      

            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.  

            Martin Wasiak added a comment - 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.  

            Kevin Palm added a comment -

            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

            Kevin Palm added a comment - 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

            Arjoon Som added a comment -

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

            Arjoon Som added a comment - The new GIC has been rolled out to 100% of users

            Arjoon Som added a comment - - edited

            Hi Everyone, 

            As informed earlier, the new Issue Create experience has been rolled out to 100% of our users in Jira. Additionally, we have recently announced that the process to deprecate the legacy Issue Create experience will begin this month. 

            We are also actively monitoring feedback and resolving any bugs our customers are reporting and you can find the latest updates to the fixes https://jira.atlassian.com/browse/JRACLOUD-77212

            As the primary goal of this ticket has now been achieved, we are going to close this ticket.

            Thank you.

            Arjoon Som
            Sr. PM, Jira Cloud

            Arjoon Som added a comment - - edited Hi Everyone,  As informed earlier, the new Issue Create experience has been rolled out to 100% of our users in Jira. Additionally, we have recently announced that the process to deprecate the legacy Issue Create experience will begin this month.  We are also actively monitoring feedback and resolving any bugs our customers are reporting and you can find the latest updates to the fixes https://jira.atlassian.com/browse/JRACLOUD-77212 As the primary goal of this ticket has now been achieved, we are going to close this ticket. Thank you. Arjoon Som Sr. PM, Jira Cloud

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

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

            Kalee Williams added a comment - Customer is losing their summary when switching from Issue Type in the Create Issue modal.  https://twitter.com/joachimnicolas/status/1514221583757365253

            Greg D added a comment -

            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.

            Greg D added a comment - 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.

            Deleted Account (Inactive) added a 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

            Atlassian Sales added a comment - Hi Atlassian, What is the status for this implementation? Regards, Nadica

            PK added a comment - - edited

            i need text formatting for table on jira cloud

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

            PK added a comment - - edited 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?

            Kai Grossjohann added a comment - @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?

            mwren added a comment -

            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...

            mwren added a comment - 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...

            Allan Jardine added a comment - - edited

            > 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).

            Allan Jardine added a comment - - edited > 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.

            Brad Kelley added a comment - 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.

            Patrick Harrold added a comment - 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

            Alexandr Paliy added a comment - @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

            Kevin Palm added a comment -

            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 )

            Kevin Palm added a comment - 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 )

            Adam Charron added a comment - - edited

            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.

            Adam Charron added a comment - - edited 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.

            Michal Bartak added a comment - - edited

            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?

            Michal Bartak added a comment - - edited 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

             

            Jehosúa Ibuarben added a comment - 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?

            Alexandr Paliy added a comment - 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?

            Arjoon Som added a comment -

            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

            Arjoon Som added a comment - 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

            Arjoon Som added a comment -

            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

            Arjoon Som added a comment - 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

            Greg D added a comment -

            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.

            Greg D added a comment - 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

            Joe Maguire added a comment - 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

            Roland Schroth added a comment - 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!

            David Stokes added a comment - Yay - bring it on!

            Arjoon Som added a comment -

            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

            Arjoon Som added a comment - 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.

            Erik Neudert added a comment - 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.

            Brian Oconnell added a comment - Atlassian's answer to everything is to always add more complexity and mix up all the documentation.

            ambujp added a comment -

            I (my team) need this asap. 

            ambujp added a comment - 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

            Jeana Clark added a comment - 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

            Greg D added a comment -

            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?

            Greg D added a comment - 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?

            Arjoon Som added a comment - - edited

            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

            Arjoon Som added a comment - - edited 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

            Arjoon Som added a comment -

            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

            Arjoon Som added a comment - 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? 

            Boyd Hemphill added a comment - /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.

            Pierrick Brossin added a comment - Also expected the editor when creating tickets to be updated with the new release/layout. Hope it will be considered and worked on asap.

            Sebastian Jopen added a comment - - edited

            + 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. 

            Sebastian Jopen added a comment - - edited + 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.

            Andrew Grossman added a comment - 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. 

            David Bounds added a comment - 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!

            Roland Schroth added a comment - +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.

            Ryan Davis added a comment - +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.

            Matt Vlasach added a comment - +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.

            Andrew Dixon added a comment - 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.

            Deleted Account (Inactive) added a comment - Thank you for the ongoing transparency on this effort, @Arjoon Som.

            Arjoon Som added a comment -

            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.biesack1pdame1152700862 - 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 Som added a comment - 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

            Phil added a comment - - edited

            @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.

            Phil added a comment - - edited @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!

            Remus Lazar added a comment - @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!

            Brandon added a comment -

            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...

            Brandon added a comment - 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...

            Greg D added a comment -

            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!  

            Greg D added a comment - 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!  

            djb added a comment -

            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?

            djb added a comment - 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.

            Andrew Dixon added a comment - @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.

            Greg D added a comment -

            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.

            Greg D added a comment - 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

            David Stokes added a comment - 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

            Arjoon Som added a comment -

            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

            Arjoon Som added a comment - 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

            We are in the process of evaluating alternatives for Jira as well.  Given how much our enterprise spends on Jira monthly (along with the various subscriptions) this is really unacceptable.  One almost wants to lend them an intern to spend the day it would take to address this.

            BRAD WARDELL added a comment - We are in the process of evaluating alternatives for Jira as well.  Given how much our enterprise spends on Jira monthly (along with the various subscriptions) this is really unacceptable.  One almost wants to lend them an intern to spend the day it would take to address this.

            I also do the same workaround, with the addition of a few more fields like assignee. But I always worry about clicking the link to the new issue in time; otherwise I have to go searching for the new issue. The link to the new issue is different depending on the underlying page - board works different from backlog works different from other pages.

            I wish the create issue form displayed the issue on submit, maybe optional by using a checkbox that the form remembers.

            The mix of new and old in Jira is disjointed.

            Don Arsenault added a comment - I also do the same workaround, with the addition of a few more fields like assignee. But I always worry about clicking the link to the new issue in time; otherwise I have to go searching for the new issue. The link to the new issue is different depending on the underlying page - board works different from backlog works different from other pages. I wish the create issue form displayed the issue on submit, maybe optional by using a checkbox that the form remembers. The mix of new and old in Jira is disjointed.

            Same workaround here... it's really a shame.

            Vivian Steller added a comment - Same workaround here... it's really a shame.

            My workaround for now and until FY22 is:

            1. Create the issue by only filling the summary
            2. When the new issue created notification is displayed, Cmd-click to open it in a new tab
            3. Continue with the issue creation (e.g. description, screenshots, etc.)

            That doesn't sound right...

            Simon Godard added a comment - My workaround for now and until FY22 is: Create the issue by  only filling the summary When the new issue created notification is displayed, Cmd-click to open it in a new tab Continue with the issue creation (e.g. description, screenshots, etc.) That doesn't sound right...

            Wow. I just rolled out Jira to a team used to Github and I'm starting to regret it. Seriously, being able to use markdown syntax is key for these folks, and not being able to do that in the create issue screen is so much more confusing that not being able to in the first place.

            This and ridiculously unfinished stuff like JRACLOUD-69876 will make me go away pretty soon. You're annoying both the users who don't care what the tool actually is, as well as the power users who care about being able to quickly edit epic links.

            Now you'll be forcing all users to the "new and unfinished" issue view from Mar 31, 2021? Good job Atlassian! Good job.

            Matthias Eichstedt added a comment - Wow. I just rolled out Jira to a team used to Github and I'm starting to regret it. Seriously, being able to use markdown syntax is key for these folks, and not being able to do that in the create issue screen is so much more confusing that not being able to in the first place. This and ridiculously unfinished stuff like  JRACLOUD-69876  will make me go away pretty soon. You're annoying both the users who don't care what the tool actually is, as well as the power users who care about being able to quickly edit epic links. Now you'll be forcing all users to the "new and unfinished" issue view from Mar 31, 2021? Good job Atlassian! Good job.

            I'm unsubscribing, our migration to YouTrack is completed. Bye, Atlassian.

            Philip Chinery added a comment - I'm unsubscribing, our migration to YouTrack is completed. Bye, Atlassian.

            FY22 ??? Like others mentioned, this is really a long time to wait. At least, change the Editor to the new one... right now, all of our users need to use 2 syntax and the result is confusion. 

            Simon Godard added a comment - FY22 ??? Like others mentioned, this is really a long time to wait. At least, change the Editor to the new one... right now, all of our users need to use 2 syntax and the result is confusion. 

            D.R. added a comment -

            Keep in mind that this also impact the transition screens. (such as the resolution screen where you want to use a reply to customer)

            D.R. added a comment - Keep in mind that this also impact the transition screens. (such as the resolution screen where you want to use a reply to customer)

            Are you kidding me? Markdown in create... Who the hell is behind this?

            arnaud.quivoron added a comment - Are you kidding me? Markdown in create... Who the hell is behind this?

            Rai added a comment - - edited

            FY22?

            Honestly ridiculous that you need 18+ months to implement this from the time you've rolled out the updates to the view issue experience. Something is clearly awry at Atlassian. 

            Rai added a comment - - edited FY22? Honestly ridiculous that you need 18+ months to implement this from the time you've rolled out the updates to the view issue experience. Something is clearly awry at Atlassian. 

            Michael Hedman added a comment - - edited

            FY22?????  This seems like a major gap.  And it's already been a year 2 years (2019).  3 4 years for something that was a huge gap in design.  Are you running waterfall over there?

            Michael Hedman added a comment - - edited FY22?????  This seems like a major gap.  And it's already been a year  2 years (2019).  3 4 years for something that was a huge gap in design.  Are you running waterfall over there?

            Our customer would like to have the ability to place their custom fields in the same line rather than one under the other in order.

            Phyllis.Boruk@mutualofamerica.com added a comment - Our customer would like to have the ability to place their custom fields in the same line rather than one under the other in order.

            @Hans Moleman - yes, I've been running on EAP and submitting bugs to PhpStorm for few years already. And the difference in approach to bug reports and feature requests seems like night and day. Where with Jetbrains I get support engineer checking the issue and then actual technical person dealing with it. Here it seems that issues are mostly handled by something like a "comunity managers" who are mostly interested in defusing the discussions rather than solving the problems  Obviously, with Jetbrains there are some issues, that are long running and people get annoyed, but they are mostly "political" - like if they should start supporting some new tool - whether the demand is large enough to justify the investment. But I would be hard pressed to remember one technical issue/bug that was not solved in a few months once it was verified and debugged. 

            tomasfejfar added a comment - @Hans Moleman - yes, I've been running on EAP and submitting bugs to PhpStorm for few years already. And the difference in approach to bug reports and feature requests seems like night and day. Where with Jetbrains I get support engineer checking the issue and then actual technical person dealing with it. Here it seems that issues are mostly handled by something like a "comunity managers" who are mostly interested in defusing the discussions rather than solving the problems   Obviously, with Jetbrains there are some issues, that are long running and people get annoyed, but they are mostly "political" - like if they should start supporting some new tool - whether the demand is large enough to justify the investment. But I would be hard pressed to remember one technical issue/bug that was not solved in a few months once it was verified and debugged. 

            Greg D added a comment -

            I thought about it a little more and I really do love Jira Cloud... I just become very passionate about fixes that would eliminate the complaints from all of the users and allow me to fully stand behind the software.  And I just want the fixes to happen faster.

             

            Pertaining to this particular issue, after the switch, will everything need to be in markdown?  For issues that get created via API that use Wiki Markup, will everything need to be switched over to function properly?  I'm guessing probably yes, but just want to get ahead of that.

             

            If possible and if it would be faster, you could start with upgrading the transition screens so that at least we can better predict our user experiences (create starts with wiki, then everything after creation will actually be in the new markdown and new view).  I think from what I recall, that is the same code though.

             

            My preference would be for create and transition screens to be upgraded well before March 2021 so that we can get everyone fully into the new world and properly predict our commenting templates and other things that are currently fragmented between the two views.

            Greg D added a comment - I thought about it a little more and I really do love Jira Cloud... I just become very passionate about fixes that would eliminate the complaints from all of the users and allow me to fully stand behind the software.  And I just want the fixes to happen faster.   Pertaining to this particular issue, after the switch, will everything need to be in markdown?  For issues that get created via API that use Wiki Markup, will everything need to be switched over to function properly?  I'm guessing probably yes, but just want to get ahead of that.   If possible and if it would be faster, you could start with upgrading the transition screens so that at least we can better predict our user experiences (create starts with wiki, then everything after creation will actually be in the new markdown and new view).  I think from what I recall, that is the same code though.   My preference would be for create and transition screens to be upgraded well before March 2021 so that we can get everyone fully into the new world and properly predict our commenting templates and other things that are currently fragmented between the two views.

            Greg D added a comment - - edited

            I'll make an edit since I like PyCharm and Intelli,J so I checked out YouTrack (seems decent).  Redmine is free and open source if you want to build it out with themes yourself (I don't really like it though).  I prefer Jira Cloud with the super complex use-cases that we have, but if you can't wait for your use-cases it might be worth the switch since YouTrack has a Jira importer. 

             

            To echo what you were saying, Markus, I love Jira Cloud and just want it to be better with the critical things that need fixing.  I want to be an advocate with just a wish-list of nice-to-haves instead of needs.

            What pains me the most (and probably the rest of you) is that there are tons of important bugs that need fixing that we all uncover for Atlassian and there are features that would actually help current customers and give Atlassian more market share... and we all actually lay out the path to fixing these deficiencies pretty clearly... but for some odd reason, they just don't get worked on for a very, very long time.  Instead, each quarter you just get an email about a new release of something that no current customer actually needs.  It is a big problem in our industry that at the top level, Product doesn't properly prioritize what is needed from their Operations teams and their customers before working on newer things instead.

             

            I have to throw in an analogy since I'm editing... it's like you take your car to the mechanic because your gears keep slipping, your brakes are squealing, and your window is stuck... and then the mechanic gives you the car back and says, "We agree those are problems... we won't fix your gears, probably can fix the brakes in 2 years, and the windows sometimes get stuck like that (they'll be better on the next model).  We tinted your windows and gave you a power liftgate."...  Ok, those are nice and the tinting does look great, but I could have easily opened and closed the trunk manually.  Couldn't you have spent the time just fixing the things that are actually preventing me from driving properly?

             

            I am optimistic that Atlassian will speed up their cycle times after migrating to the New View (new infrastructure)... but it still probably won't be fast enough for my liking.  Prove me wrong though, Atlassian.  Speed it all up and fix things weekly to make me a believer again.

            Greg D added a comment - - edited I'll make an edit since I like PyCharm and Intelli,J so I checked out YouTrack (seems decent).  Redmine is free and open source if you want to build it out with themes yourself (I don't really like it though).  I prefer Jira Cloud with the super complex use-cases that we have, but if you can't wait for your use-cases it might be worth the switch since YouTrack has a Jira importer.    To echo what you were saying, Markus, I love Jira Cloud and just want it to be better with the critical things that need fixing.  I want to be an advocate with just a wish-list of nice-to-haves instead of needs. What pains me the most (and probably the rest of you) is that there are tons of important bugs that need fixing that we all uncover for Atlassian and there are features that would actually help current customers and give Atlassian more market share... and we all actually lay out the path to fixing these deficiencies pretty clearly... but for some odd reason, they just don't get worked on for a very, very long time.  Instead, each quarter you just get an email about a new release of something that no current customer actually needs.  It is a big problem in our industry that at the top level, Product doesn't properly prioritize what is needed from their Operations teams and their customers before working on newer things instead.   I have to throw in an analogy since I'm editing... it's like you take your car to the mechanic because your gears keep slipping, your brakes are squealing, and your window is stuck... and then the mechanic gives you the car back and says, "We agree those are problems... we won't fix your gears, probably can fix the brakes in 2 years, and the windows sometimes get stuck like that (they'll be better on the next model).  We tinted your windows and gave you a power liftgate."...  Ok, those are nice and the tinting does look great, but I could have easily opened and closed the trunk manually.  Couldn't you have spent the time just fixing the things that are actually preventing me from driving properly?   I am optimistic that Atlassian will speed up their cycle times after migrating to the New View (new infrastructure)... but it still probably won't be fast enough for my liking.  Prove me wrong though, Atlassian.  Speed it all up and fix things weekly to make me a believer again.

            @Philip I would be interested to hear about this too.

            Jira (cloud) is not bad, it's really great in many aspects but some basic aspects fall so flat, it hurts. I literally stopped filling out the initial description field for new story/bugs/etc. because they experience is so bad. I just create empty ones, reload them, start writing. The stark different behaviour of the two worlds (=editors) is just not worth the pain to deal with both and their different aspects of formatting outcome etc.

            Markus Fischer added a comment - @Philip I would be interested to hear about this too. Jira (cloud) is not bad, it's really great in many aspects but some basic aspects fall so flat, it hurts. I literally stopped filling out the initial description field for new story/bugs/etc. because they experience is so bad. I just create empty ones, reload them, start writing. The stark different behaviour of the two worlds (=editors) is just not worth the pain to deal with both and their different aspects of formatting outcome etc.

            @Philip Chinery pretty much agreed. I'd love to hear your feedback on the migration process and about YouTrack usage compared to Jira. 

            tomasfejfar added a comment - @Philip Chinery pretty much agreed. I'd love to hear your feedback on the migration process and about YouTrack usage compared to Jira. 

            @Phil: Yes, you understand this correctly. In my opinion, Atlassian and especially Jira is broken and I don't have hope that it can be fixed. This issue was the final drop for us and we are migrating to a different solution right now (YouTrack in our case), as we are fed up with the super slow development pace and the ridiculous time frames for issues like this (other issues are open for 10 years). The Atlassian support sounds understanding, but noone seems to have the ability to change something. Therefore, we'll go and spend our money somewhere else.

            Philip Chinery added a comment - @Phil: Yes, you understand this correctly. In my opinion, Atlassian and especially Jira is broken and I don't have hope that it can be fixed. This issue was the final drop for us and we are migrating to a different solution right now (YouTrack in our case), as we are fed up with the super slow development pace and the ridiculous time frames for issues like this (other issues are open for 10 years). The Atlassian support sounds understanding, but noone seems to have the ability to change something. Therefore, we'll go and spend our money somewhere else.

            Phil added a comment -

            I see the update on this issue says a fix will be a complete rewrite of the New Issue flow and this is coming "mid FY22"... Fiscal year 2021 just got started August 1st for Atlassian, right? So a solution for this glaring issue is still 18 months away despite having been documented here since April 2019?! Am I understanding this correctly?

            Phil added a comment - I see the update on this issue says a fix will be a complete rewrite of the New Issue flow and this is coming " mid FY22 "... Fiscal year 2021 just got started August 1st for Atlassian, right? So a solution for this glaring issue is still 18 months away despite having been documented here since April 2019 ?! Am I understanding this correctly?

            Ricardo N added a comment -

            Ricardo N added a comment - https://getsupport.atlassian.com/browse/JST-608488

            Same for me, and it's not just Confluence.

            The formatting simply works differently so I started to muscle train to create empty issues at first and then edit the initial description, which then follows the laws of the new editor.

            Markus Podar added a comment - Same for me, and it's not just Confluence. The formatting simply works differently so I started to muscle train to create empty issues at first and then edit the initial description, which then follows the laws of the new editor.

            Kaspar von Gunten added a comment - - edited

            Only thing I can ad to this is: When I create issues and e.g. copy-paste text from Confluence I have to go back and edit every single one to apply formatting again.

            Worse even, if I copy stuff with markup syntax into the issue description, I have to go back and edit out the markup and edit it in again (e.g. backticks), because the create editor will not have understood them (unless I replace them at creation time with  {code}, how fun is that).

            In other words: when creating lots of issues from text prepared elsewhere, I usually use "create another" to improve my performance, but above problem makes this advantage completely irrelevant, because I have to go back and re-edit all of them again after creation, in a very tedious way.

            If only the description field would be from the new issue view, this would already solve 90% of my problems with this being still the old view. 

            Kaspar von Gunten added a comment - - edited Only thing I can ad to this is: When I create issues and e.g. copy-paste text from Confluence I have to go back and edit every single one to apply formatting again. Worse even, if I copy stuff with markup syntax into the issue description, I have to go back and edit out the markup and edit it in again (e.g. backticks), because the create editor will not have understood them (unless I replace them at creation time with  {code}, how fun is that). In other words: when creating lots of issues from text prepared elsewhere, I usually use "create another" to improve my performance, but above problem makes this advantage completely irrelevant, because I have to go back and re-edit all of them again after creation, in a very tedious way. If only the description field would be from the new issue view, this would already solve 90% of my problems with this being still the old view. 

            Arjoon Som added a comment -

            Hi Mykenna,

             

            Thank you for your candid thoughts and feedback. We hear you and we understand the inconvenience that you have to face because of the discrepancies between Issue Create and Issue View. The Issue Create experience is not just being refactored but is actually being re-built from scratch. The reason for this is because we know that if we are to truly solve for the customer, a piecemeal approach to solving issues will no longer work. We’ve chosen to take a step back, look at the experience in its entirety and invest considerable resources in building an experience which we are confident will be a much better, faster, and more reliable experience. This is what is best for our customers in the long term. Building from scratch takes time as there are fundamental architectural frameworks that need to be designed, developed, and deployed before we can build an experience on it. 

             

            While I cannot go into the specifics of the timelines of the rollout of this new experience as it is still way too early in the development, please be assured that we are working at full throttle to bring this to customers ASAP. Moreover, we can expect customers to onboard early to the new Issue Create experience through an Early Access Program that will be announced closer to the roll-out date (sometime early 2021) and I would encourage our customers here on this thread to participate. We will definitely share more details on this thread at the appropriate time. 

             

            Thanks and regards,
            Arjoon Som
            Product Manager, Jira Cloud

            Arjoon Som added a comment - Hi Mykenna,   Thank you for your candid thoughts and feedback. We hear you and we understand the inconvenience that you have to face because of the discrepancies between Issue Create and Issue View. The Issue Create experience is not just being refactored but is actually being re-built from scratch. The reason for this is because we know that if we are to truly solve for the customer, a piecemeal approach to solving issues will no longer work. We’ve chosen to take a step back, look at the experience in its entirety and invest considerable resources in building an experience which we are confident will be a much better, faster, and more reliable experience. This is what is best for our customers in the long term. Building from scratch takes time as there are fundamental architectural frameworks that need to be designed, developed, and deployed before we can build an experience on it.    While I cannot go into the specifics of the timelines of the rollout of this new experience as it is still way too early in the development, please be assured that we are working at full throttle to bring this to customers ASAP. Moreover, we can expect customers to onboard early to the new Issue Create experience through an Early Access Program that will be announced closer to the roll-out date (sometime early 2021) and I would encourage our customers here on this thread to participate. We will definitely share more details on this thread at the appropriate time.    Thanks and regards, Arjoon Som Product Manager, Jira Cloud

            I bet they are using stash (server) version of Jira which is more powerfull, packed with features and flexible. It's more expensive so likely gets better support. I used to use such version for years and I can say it's like heaven and hell (where hell is cloud Jira: slow (check out how many data it loads with every pageview), limited feature-wise, with support we can see here.

            Michal Bartak added a comment - I bet they are using stash (server) version of Jira which is more powerfull, packed with features and flexible. It's more expensive so likely gets better support. I used to use such version for years and I can say it's like heaven and hell (where hell is cloud Jira: slow (check out how many data it loads with every pageview), limited feature-wise, with support we can see here.

            Mike Odom added a comment -

            Mykenna had a very intelligent and well thought out response that I very much appreciate.

            (I would have done a user mention, but the @ sign has been broken for months as well.)

            I am less intelligent, so I'll add that this bug tells me that Jira doesn't use Jira to project manage Jira. There's no way a competent project manager would put up with this for so long. What do you guys use these days, Asana? Trello? Or have you gone back to straight-up post-its on a whiteboard? (I actually recommend this for small teams, it's pretty effective.)

            What's actually far more likely: Jira's development team internally uses an older version of Jira because their team doesn't want to deal with the upgrade and change. Or they're using some private version of Jira that's not going to be released for a year. Please eat your own dog food. Your clients are on this weak version, you should feel the same pain that we do.

            Mike Odom added a comment - Mykenna had a very intelligent and well thought out response that I very much appreciate. (I would have done a user mention, but the @ sign has been broken for months as well.) I am less intelligent, so I'll add that this bug tells me that Jira doesn't use Jira to project manage Jira. There's no way a competent project manager would put up with this for so long. What do you guys use these days, Asana? Trello? Or have you gone back to straight-up post-its on a whiteboard? (I actually recommend this for small teams, it's pretty effective.) What's actually far more likely: Jira's development team internally uses an older version of Jira because their team doesn't want to deal with the upgrade and change. Or they're using some private version of Jira that's not going to be released for a year. Please eat your own dog food. Your clients are on this weak version, you should feel the same pain that we do.

            FY22? I hope it's typo. IMO FY21 is long way too far for such change.

            Michal Bartak added a comment - FY22? I hope it's typo. IMO FY21 is long way too far for such change.

            Hi Arjoon. Thanks for the transparency. Those of us following this issue have a better sense of what to expect here.

            However, I'd just like to feed back to you some of the "optics" of your response, from the perspective of end-users. A fair rephrasing might be "We know this is a problem, and we have a significant refactoring in progress to address it. Please wait another 18 months." The proposed fix is now targeted for 3+ years after the initial report.

            Look, we understand that Atlassian can't "fix everything right away". Most of us are in software, we understand the struggles of maintaining mature products with a large user base. It's not easy. We get it.

            However, please also understand that most of us are used to modern products with shorter cycle times. Atlassian needs to see their lack of agility in the broader marketplace. Cycle times measured in years should be a warning sign. This is not a one-off, as many of us on this thread can point to other significant, user-impacting issues that have been around for many years.

            Personally, I feel this particular issue is mischaracterized as a "suggestion", since the rollout of the New Editor broke expected and relied-upon functionality in a variety of ways. How is this not some form of bug?

            I don't want to discourage the transparency – as an agilist, I strongly encourage it. Yet we know that transparency exposes problems that businesses might not have even realized. My intention here is to encourage Atlassian to realize how they might be alienating some of their most ardent supporters, and to take action to shorten the cycle time of significant, user-impacting issues. Thank you.

            Mykenna Cepek added a comment - Hi Arjoon. Thanks for the transparency. Those of us following this issue have a better sense of what to expect here. However, I'd just like to feed back to you some of the "optics" of your response, from the perspective of end-users. A fair rephrasing might be "We know this is a problem, and we have a significant refactoring in progress to address it. Please wait another 18 months." The proposed fix is now targeted for 3+ years after the initial report. Look, we understand that Atlassian can't "fix everything right away". Most of us are in software, we understand the struggles of maintaining mature products with a large user base. It's not easy. We get it. However, please also understand that most of us are used to modern products with shorter cycle times. Atlassian needs to see their lack of agility in the broader marketplace. Cycle times measured in years should be a warning sign. This is not a one-off, as many of us on this thread can point to other significant, user-impacting issues that have been around for many years. Personally, I feel this particular issue is mischaracterized as a "suggestion", since the rollout of the New Editor broke expected and relied-upon functionality in a variety of ways. How is this not some form of bug? I don't want to discourage the transparency – as an agilist, I strongly encourage it. Yet we know that transparency exposes problems that businesses might not have even realized. My intention here is to encourage Atlassian to realize how they might be alienating some of their most ardent supporters, and to take action to shorten the cycle time of significant, user-impacting issues. Thank you.

            Arjoon Som added a comment -

            H Everyone,

            Thank you for raising this issue. Please know that we are cognisant of this deficiency in the current Global Issue create modal. We are also aware that the old editor is only one of the feature gaps that exist between the current Issue Create and the Issue View experiences. We understand that these inconsistencies between two very closely linked experiences are inconvenient, and from the responses on this thread, clearly hamper the productivity of our customers and end-users.

            In response, our team is in the process of revamping the Issue Create experience entirely from scratch to make it faster, more reliable, and to bring the user experience of Issue Create more in line with the new Issue View experience. This means that we will update all fields in the Issue Create modal including the editor, and we will also add more capabilities to make the Issue Create experience better for our customers. This is an already active and ongoing project within Jira. 

            Our current plan is to roll out this new Issue Create experience by mid FY22 but it is subject to change. Until then, we kindly request you to bear with us and to use your current workarounds and processes. We apologize for not being able to resolve your problem related to the editor immediately. We do, however, commit to solving it soon. This ticket will be moved to our team's long-term backlog so that it can be tracked internally by our team. 

            Thanks and regards,
            Arjoon Som
            Product Manager, Jira Cloud

            Arjoon Som added a comment - H Everyone, Thank you for raising this issue. Please know that we are cognisant of this deficiency in the current Global Issue create modal. We are also aware that the old editor is only one of the feature gaps that exist between the current Issue Create and the Issue View experiences. We understand that these inconsistencies between two very closely linked experiences are inconvenient, and from the responses on this thread, clearly hamper the productivity of our customers and end-users. In response, our team is in the process of revamping the Issue Create experience entirely from scratch to make it faster, more reliable, and to bring the user experience of Issue Create more in line with the new Issue View experience. This means that we will update all fields in the Issue Create modal including the editor, and we will also add more capabilities to make the Issue Create experience better for our customers. This is an already active and ongoing project within Jira.  Our current plan is to roll out this new Issue Create experience by mid FY22 but it is subject to change. Until then, we kindly request you to bear with us and to use your current workarounds and processes. We apologize for not being able to resolve your problem related to the editor immediately. We do, however, commit to solving it soon. This ticket will be moved to our team's long-term backlog so that it can be tracked internally by our team.  Thanks and regards, Arjoon Som Product Manager, Jira Cloud

            Atlassian Update - 15 October 2020

            Hi everyone, thank you for your interest surrounding this ticket. We are actively exploring this request, and while we can't share a timeline on when we might deliver a solution, we will keep you updated with our progress.

            Thanks,
            Jira Cloud team

            Michael Tokar added a comment - Atlassian Update - 15 October 2020 Hi everyone, thank you for your interest surrounding this ticket. We are actively exploring this request, and while we can't share a timeline on when we might deliver a solution, we will keep you updated with our progress. Thanks, Jira Cloud team

            My use case:  create an automation rule to add a "checklist" of items into the Description field of a Jira issue. Pretty reasonable end-user request. And all the long-time Jira admins are already shaking their heads...

            Firstly, Jira doesn't support checkboxes; but let's not go down that rabbit hole. Being creative, I decided that emojis would be a fair substitute, with a friendly green checkmark for "Done". (We don't want to install another Jira app just for checkboxes right now.)

            I created a manually-triggered Jira Automation rule to put the user's checklist into the Description of an issue. I used the current (New Editor) emoji markdown for the checkmark and other emojis. And, of course, testing the rule showed no emojis.

            One Jira support ticket (and days) later, I revised my rule to use the Old Editor emoji markdown, and that worked. So now my user has their sort-of checklist. Fine.

            Let's review. Jira doesn't support actual checkboxes. To use emojis as a workaround, I had to use legacy markdown. Someday Atlassian might fix this and switch new issue creation to use the New Editor, and my solution will break (my solution is forced to be brittle). Me happy? Nope.

            Mykenna Cepek added a comment - My use case:  create an automation rule to add a "checklist" of items into the Description field of a Jira issue. Pretty reasonable end-user request. And all the long-time Jira admins are already shaking their heads... Firstly, Jira doesn't support checkboxes; but let's not go down that rabbit hole. Being creative, I decided that emojis would be a fair substitute, with a friendly green checkmark for "Done". (We don't want to install another Jira app just for checkboxes right now.) I created a manually-triggered Jira Automation rule to put the user's checklist into the Description of an issue. I used the current (New Editor) emoji markdown for the checkmark and other emojis. And, of course, testing the rule showed no emojis. One Jira support ticket (and days) later, I revised my rule to use the Old Editor emoji markdown, and that worked. So now my user has their sort-of checklist. Fine. Let's review. Jira doesn't support actual checkboxes. To use emojis as a workaround, I had to use legacy markdown. Someday Atlassian might fix this and switch new issue creation to use the New Editor, and my solution will break (my solution is forced to be brittle). Me happy? Nope.

            Personally, I gave up on this. This was raised just as the new view was released and Atlassian is not willing to do anything about it - for far more than a year now. Sadly, I think this will be one of the issues that will be able to celebrate a few more birthdays. There are even very active issues which are more than 10 years old. To me, it just shows again that Atlassian does not really care. Jira is hard to replace right now, but we're looking at alternatives, because "expensive crappy software" can be replaced with "cheap/free crappy software" (with the option to actually adapt things when working with a free tool)

            Philip Chinery added a comment - Personally, I gave up on this. This was raised just as the new view was released and Atlassian is not willing to do anything about it - for far more than a year now. Sadly, I think this will be one of the issues that will be able to celebrate a few more birthdays. There are even very active issues which are more than 10 years old. To me, it just shows again that Atlassian does not really care. Jira is hard to replace right now, but we're looking at alternatives, because "expensive crappy software" can be replaced with "cheap/free crappy software" (with the option to actually adapt things when working with a free tool)

            Mike Odom added a comment -

            Sorry, I'm slightly cranky about this feature... It kills me that the edit description box on 'Create Issue' vs 'Edit Issue' are different. Why are they different? Why do they have different options? They edit the same data.

            I cannot create a ticket with a description. The Create description text box is garbage. It doesn't support me pasting from Google Docs. It doesn't support me typing things like '*' to create bullet points.

            When I want to create an issue, I must first create the issue with a title and save it, then I must edit the existing issue. I would like to be able to hit 'Create' and then be able to type the title and description in the same window without these extra steps. I've sadly put up with this annoyance for over a year apparently. 

            Mike Odom added a comment - Sorry, I'm slightly cranky about this feature... It kills me that the edit description box on 'Create Issue' vs 'Edit Issue' are different. Why are they different? Why do they have different options? They edit the same data. I cannot create a ticket with a description. The Create description text box is garbage. It doesn't support me pasting from Google Docs. It doesn't support me typing things like '*' to create bullet points. When I want to create an issue, I must first create the issue with a title and save it, then I must edit the existing issue. I would like to be able to hit 'Create' and then be able to type the title and description in the same window without these extra steps. I've sadly put up with this annoyance for over a year apparently. 

            This is weird that the New Issue view doesn't use for Creation dialog. It is a blocker to move everybody to the New Issue view!

            Pavel Zaikin added a comment - This is weird that the New Issue view doesn't use for Creation dialog. It is a blocker to move everybody to the New Issue view!

            I appreciate this fix. Its an abnormal time-killer and also the re-occurrung though to think about the current editor-context is also a very uncomfortable brain load.

            Thomas Kekeisen added a comment - I appreciate this fix. Its an abnormal time-killer and also the re-occurrung though to think about the current editor-context is also a very uncomfortable brain load.

            Please, make issue creation dialog to use new WYSIWYG. It's nonsense that these views are different after a year.

            Pavlo Poliakov added a comment - Please, make issue creation dialog to use new WYSIWYG. It's nonsense that these views are different after a year.

            This leaves me with 3 suboptimal workarounds...

            1. Learn and use the clunky old formatting for new ticket creation.  (no; this is being phased out so why learn it?)
            2. Write the ticket description in a true markdown editor.  Create the ticket, then immediately go back to it and edit the description, pasting in markdown. (if i have to...)
            3. Avoid using description at all and just describe the ticket in the first comment. (no; obvious reasons)

            Please fix this.

            Sidenote: The new UI actually looks and feels a lot better overall, for what it is worth. <3

            Sean Kennedy added a comment - This leaves me with 3 suboptimal workarounds... Learn and use the clunky old formatting for new ticket creation.  (no; this is being phased out so why learn it?) Write the ticket description in a true markdown editor.  Create the ticket, then immediately go back to it and edit the description, pasting in markdown. (if i have to...) Avoid using description at all and just describe the ticket in the first comment. (no; obvious reasons) Please fix this. Sidenote: The new UI actually looks and feels a lot better overall, for what it is worth. <3

            The New Jira View really does seem like a task half done.  It is difficult / embarrassing to engage my clients to adopt Jira with this immediately apparent poor-UX experienced from the start.

            @JiraTeam - can you please advise when this core functionality will be finished?

            Philip Buntine added a comment - The New Jira View really does seem like a task half done.  It is difficult / embarrassing to engage my clients to adopt Jira with this immediately apparent poor-UX experienced from the start. @JiraTeam - can you please advise when this core functionality will be finished?

              dc7c78296a7c Arjoon Som
              lellis2@atlassian.com Belto
              Votes:
              423 Vote for this issue
              Watchers:
              278 Start watching this issue

                Created:
                Updated:
                Resolved: