I needed to fix the date for a work log entry this morning. I'd never noticed this until now, the dates on the 'New View' use the backwards USA format. What?! While that's no big-deal, it does show a lack of fundamental in this UI. :-(
In follow-up to William's comment above, this indeed problematic: I have my account preferences set to English US because I work in an international team, but I am based in the Netherlands (and Dutch). The US way of writing dates (month first) is very confusing for me. The date and time formats should be a separate preference. At least you should have the option to go with an ISO 8601-like format: yyyy-MM-dd hh:mm and a 24 hour clock.
This is a big problem; please listen to your customers and keep this. The old view is the only way to enter markdown. This is absolutely critical for working around shortcomings in the new editor which have been present for years. As one example, without the old view, there is no way to easily copy in a table of data. Within the new editor, you're only recourse is to copy each cell value individually. Goodbye, efficiency.
I really hate the new issues view, even after I tried to get used to it.
We know that the new issue view isn’t everyone’s preferred option, but our goal is to make it so.
Seriously? What about listening to customer feedback instead of treading them like children.
You cannot maintain two view because you are a small company with not much technical staff? Ok, then keep the OLD ONE as requested by so many of your customers.
It's good :) Atlassian is finally making a decision on the new/old issue view. The only point I had and still have is the ability to Rank to Top/Bottom which is very useful and I still use in the old view.
Sad :( to see Rank to Top/Bottom being disabed, without any improvement for it in the last couple of years Atlassian was working on this. I will have to rank issues to top or bottom from the Backlog view, which is cumbersome.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
As a customer waiting for Atlassian to resolve issues that block our migration to Cloud, these kinds of posts are frustrating.
At the time of this comment (over a month after Ahmud's post):
75 of the 241 sub-tasks (30%) in JRACLOUD-70555 are not yet closed. From a customer perspective it does not seem finished.
ALL of the blocking issues that prevent our migration to Cloud are in the 'New View' - relating to how migrated content is (poorly) rendered. Multiple Atlassian people have suggested we keep our Jira Server instance running so we can use it as a reference to read old description/comment text where formatting is not supported in Jira Cloud.
It seems to me the best way to convince your user community that you are doing a great job would be to either retain and improve the 'classic' view (many people prefer it), and/or hurry up work to resolve the many remaining problems in the 'New View'.
I don't quite understand why you are removing the old view. We've recently imported a number of projects into Jira Cloud and the old view option is useful in checking fields have imported correctly.
Why is the old view the only place you can change the type of Jira item. Please, please, please don't take away this view without making it editable on the new view.
While I am largely ambivilent on the "new view" layout itself, I find the new WYSIWYG editor infuriatingly limited (as yet, it's some way off being functionally complete) and so I am frequently forced back to using the old editor to correct the markup. The old non-wysiwyg editor makes this kind of work easy and, until the new WYSIWYG editor fills this functionality gap, I can't do without it.
i.e. being able to edit the underlying markup of the text fields is essential.
So, how does one access the "old" editor functionality from the "new" view?
Sad to hear that my company had no option but to move to the cloud based JIRA/CONFLUENCE. The new UI is a disaster on both platforms. Can't even use simple markup. JIRA flow is a total mess. You should keep with what works, the old UI works.
Email to "aauleear@atlassian.com" bounced back for me. Perhaps the intro on this page should be updated.
Other than this, I do have the following inquiry:
Before JIRA went to the cloud, there was an export to EXCEL feature that exported exactly the columns as in the view. When I use the export now after JIRA migrated to the cloud, I don’t see the same behaviour. I have extra columns and I see ID columns when I’m expecting description instead (ie. Sprint, Epic). Is there a way for me to create my own custom export template and it be available from the menu bar?
For those who have specific suggestions or how to improve the new issue view,comment and vote for it here(each specific suggestion is a subtask). If it’s not here, lodge a suggestion.
No we cannot move to this new topic as that other issue does not address some critical topics like text or markdown mode going away. That issue has been ignored.
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
If a lot of customers customers give serious product feedback after certain product decisions are communicated and are not happy with the improvements then a new FAQ article is created that explains that it's not that bad by ignoring the technical issues and limitations.
Remembers me on the old iPhone 4 antenna topic: "You're holding it wrong" :)
255 comments