Quite often the wrong epic is assigned to a story. I don't see how I can easily change the epic in the new view. Right now, I go to Old View and easily remove and/or change the epic assigned.
Please solve most bugs/issues before even considering removing the Old View. Removal of the markdown edit mode will cause extreme pain. We have dozens upon dozens of templates that staff paste in and modify to open tickets quickly. This will no longer be possible, from what I can tell.
One of the features I like in the old view is the ability to see the list of watchers. I can't see how to do that in the new view. Please advise if this feature exists or consider adding it back in.
Why wouldnt you just give people the option for both, you're literally not listening to the customers. The new view is awful for certain things and I have a Chrome Extension automatically redirect me to the old view URL action every time. Please don't remove the old view!!!!!! Please! there are many unaddressed forums complaining about the new view. This seems like a top down decision from some product manager who is making the decision for all of us what their UI preference looks like.
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 you are going to remove the ?oldIssueView=True suffixing to Jira urls can you please, please provide us with a way to access the underlying WIKI formatted text?
Use case is this... We use other product wiki's for capturing knowledge (that is often developed while working in Jira cards). Those other product wiki's are not as smart as Atlassian, in that they do not support rich text pasting, with clever paste to Wiki Formatting....
As such, when we copy text from our Jira descriptions and other rich text fields, we lose hyperlinks, headings and other basic formatting. Having the ability to paste rich text and get WIKI formatted results is a HUGE timesaver.
I'm sure many of us would be super grateful if we can retain Wiki Markup functionality. In fact, as per the other posts, there are many good reasons for keeping the oldIssueView=True option.
I too would much rather you kept the oldIssueView option. If you still feel compelled to remove the oldIssueView, could you at least provide us users with a longer period before retiring, so the Atlassian team can work through the valid reasons we all use it for! Retiring the oldIssueView so quickly would be a miss and would hurt many of us.
Requesting the postponement of this... indefinitely.
Please instead create a way to make the old view the default view.
There is just so much more you can do with the old view.
Specifically, dot-command shortcuts. The new view is significantly more limited and power users that do not like to leave the keyboard in favor for the mouse will not be happy.
Another issue with the WYSIWYG editor: as I’m typing if I enter “/” in the line the editor may randomly delete it, and possibly other characters that follow. This seems to have something to do with a pop-up window that’s triggered by typing the “/” character.
We are migrating in January and February from data center and using the old view will help us to test - it is really hard to test with an unfamiliar view. This is not great timing for us. It would be better if you waited until the majority of people have migrated to Cloud.
The old view is more intuitive and user friendly than the new view. The old view offers a larger 'description' panel and layout.
Expanding the 'Details' right frame tool bar to access the 'Assignee', 'Reporter, 'Watchers' in the new view is available for use, but the 'Dates' are missing.
In the new view, the order of the comments are in newest to oldest and its best to reverse that to understand the complete history, oldest to newest like in the old view.
In the new view, images within the description are cut-off and not formatted correctly. Even if I reduce the right frame to make the middle frame larger, its difficult to see the complete images.
The new view reviewed access to many of the fields we have and we no longer are able to see them. We need access to the old view to utilize these fields still.
Not everyone uses Jira for the same purposes and in the same way. Why are you ignoring users' request to keep the previous view if that works BETTER for some users and for the purposes that THEY use Jira? Why is this a problem, and why are you not providing FLEXIBILITY? Why are you trying to force users to use Jira the way that YOU want instead of allowing them to use it as THEY NEED? That seems like a very dictatorial way of doing things and making things more incovenient for some users. Please allow BOTH views so that the users can use what is most useful for their needs and the way that THEY use Jira! Jira is an advanced enough tool that this is not a problem to do. "Tools" such as Jira are available to assist the work flow, NOT to hinder it.
The new view brings a lot on unnecessary additional clicks. The old view gave direct access to our git integration. All branches for an issue are directly shown. Now you need additional Clicks to open the git integration, to be able to execute the options that the integration offers.
Same as with the quick filters. It would be nice if the Quickfilters in a Board would allways be visible. I know collapsing automatically happens if a certain number of filters exist. But if they are expanded they are all visible. So it would be nice to have the configurable
The new view will bring a lot of comments and problems here! Many still use the OLD view and do not comment on the new one because they do not have time to leave useless comments or check the shortcomings of the NEW! ...there are really a lot of shortcomings, missing functions, lack of space....!!!
"We know that the new issue view isn’t everyone’s preferred option, but our goal is to make it so." Nothing says customer first like trying to force people to like something that isn't useful.
Even worse, in the new view, that spaghetti path is not stable, If I add a new custom field to the view, then that path will change.
This makes it impossible to perform automated testing of our Business Rules, using Selenium for instance.
I can still write automated tests using the REST API, but long experience has taught me that what Jira does vis the REST API, and what Jira does via the user interface are not 100% consistent.
Or has that changed now in cloud? Is the REST interface and the GUI now 100% the same. Might be that I am behind the curve on a solved issue?ThanksAndrew.
If the old view is going away, can we please fix the issue where after you hit a certain amount of attachments, you cannot see them in the new view? This will be a devastating blow to my organization
255 comments