Transitioning all Jira Cloud users to the new issue view

[Jetalkumar Desai]

Is Atlassian filing for bankruptcy or selling their company? All the new direction and changes implemented is moving that direction. 

1. They lost passion for product development

2. They sell tool for manage project and implement best practices but they don't follow any.

3. They have worst engineering team without vision and quality in mind.

4. They are lead by leaders, who does not have vision or visibility into next phase.

Thanks

[Markus Troeszter]

Please listen to the folks, the new design has massive flaws and should not be released, at leased let us still choose between old and new one.

The new design has too much whitespace, every function is hidden behind some kind of button or menu. everyone in my team needs twice as much clicks for the same action as in the old view.
And on old screen, you have 90% of all informations VISIBLE!
In the new one there is too much whitespace, everythings hidden or you have to scroll.

Jira is a WORKING TOOL, not a WEBSITE, this is a huge difference!

A working tool does not need a fancy and clean layout, it need to be fast, you need all infos visible and it should be less clicks to proceed the workflow.

time = money
hidden infos = more chance of getting missed and will lead into more wasted time = more wasted money

[Matt Lane]

@Markus Troeszter  I tend to agree with a lot of those points. Sometimes with software systems and interfaces it feels like UX overhaul is just for UX overhaul sake, even if designers have the best intentions and product owners have the grandest of plans. If something works for people, it just... well... works. Here is hoping the ship gets righted - and the best possible balance is struck going forward.

[Jeff Kaemmerling]

Hi - I'm struggling with the new view because when we've turned it on to experiment with New View, the description field disappeared and I'm not clear on where to edit the schema or layout to make sure the Description field shows up in new issue view.

Please let me know.

[Mark Thompson]

@Jeff Kaemmerling open a ticket and click the configure button on the lower right corner or go to issue layout in project settings.  

Check for your field there.  Anything not there at the top of the config window you'll see the scheme that needs to be updated to show it.

[Mark Thompson]

Removed - I was a very unhappy admin when I posted this

[Mark Thompson]

@Matthew Canham - I think I've worked around every issue for the new view.  I got an email indicating that we would eventually be able to block messages from Atlassian on new view upgrade and force our users to the new view early.

I thought this was implemented already but can't find a reference to it.  Is this available?  I think now that I made UI changes on my end that we can use it.  I want them to try it out so we can get workarounds or fixes for any issues but not seeing how I can turn it on/off globally on my end.  

[Mark Thompson]

I also like to know if the "Where is my field?" feature is gone in the new view.  I use that all the time.  Losing that would be a serious blow to my productivity.  Don't really want to hear we don't need it in the new view.  I just used it to fix a problem with the new view by going back to the old view.

[Nicholas Starinsky]

New issue view is horrible. @Matthew Canham , something that worked for 15+ years is being replaced with a beta product. Can't share issue views across projects, ugly bar on top to attach files and some third party apps' attachments. Right panel taking away real estate from center view where description and custom fields used to go, customizing issue view is not available in Service Desk project, monochrome look for custom issue view tabs, missing Where is my field? button, etc. Renewal for 600 users us up in July. If we were to switch to another product, new issue view would be the reason.

[Greg D]

@Mark Thompson it is at the very top of. your global issue settings:  <instance-name>.atlassian.net/secure/admin/new-issue-view-transition

I lost that spot before since it is not in the . Admin menu that I use to navigate everywhere and I had to retrace my steps.

@Nicholas Starinsky not sure if you have looked recently, but they have the tabs back that are honoring your schemes and you can actually put every field everywhere now (left and right).  It is better than before because you can control every field (system fields, date fields, user fields... you can put them all anywhere now).  I do agree that we should have better control of where the apps clutter up the screen (I just reach out to those apps and suggest how they should fix their junk since they control that... or maybe delete the app that you don't like if you don't need it).  Hopefully soon they will launch those extra groupings to use on the right side that will be extra snazzy to be able to collapse sections. It will be better for a lot of you when they integrate the screen schemes into the issue layout again (so you don't have to edit each issue type in each project... I heard they were prototyping that)..... but I'm just taking the time to go through each of our hundreds of issue types in the many projects and fine-tuning them all since there is a path forward.  It was definitely horrible at first, and there is still work to do for sure, but it's much better now and it is my preferred view. It definitely is far prettier (and I think that was my main complaint at first.. that it just looked nice for people with no custom fields and took away a lot of features).  Once they finish, they will be able to work on other desperately needed features and implement them into the better back-end infrastructure that this brings... but I'm sure I'll be complaining at the things that they decide to attack first, haha.

Figured I would respond since us Admins are the fast guns in this game.  Hopefully it helps.

[Mark Thompson]

@Greg D - thank you!  Exactly what I was looking for.  By the way I bet you would likely think it is funny if I told you who told me it wasn't implemented.  Not mentioning don't want to get anyone in trouble.

[Rob Horan]

Now that tabs and looping transitions are back can we please deprecate the 'your work' page and bring dashboards back as landing pages?

[Kristine Gerasimenko]

Hello everybody!

Are you facing the same inconvenience of absence of fast buttons to close the issue? Would you be so kind to go and VOTE for this request to bring back this feature in the new Jira Issue view JRACLOUD-75577 - Statuses to be shown as buttons instead of a unique drop-down button list 

Thank you in advance! Let's make Jira great again!

[Kristine Gerasimenko]

Guys! If any of these tickets matter to you, could you please vote for them. 
Wiki Style Renderer does not work for custom Single Line Text fields
Updating jira.table.cols.subtasks in Advanced Settings has no effect on the Old Issue View
Configuring the info to show when viewing sub-tasks in a table does not reflect in the new issue view
Date picker for "Due Date" field does not show option "Today"

Subtask in new issue view cannot be edited from the parent issue 

Thank you in advance!

[Jack Hunter [HeroCoders]]

I recently noticed that I could not apply comment visibility after the comment was posted. 

I had to switch to the old view. 

[Rob Horan]

@Kristine Gerasimenkoresolved date should be there.   Per the ticket you linked:

Atlassian Update - 4 March 2021

Hi everyone,

The resolved date and time is now available in the new issue view. You can see this below the created and updated date and time. Clicking on these dates will switch between absolute and relative time. We will also be releasing the ability to edit the resolution field shortly - this is tracked via https://jira.atlassian.com/browse/JRACLOUD-69556

Kind regards,

Atlassian

You might want to check the others.

[Kristine Gerasimenko]

Thank you, @Rob Horan 

[Tushar Somkuwar]

We have customized our JIRA projects by adding multiple custom fields while creating JIRA issue and have also automated the JIRA ticket creation by integrating it with AWS cloud watch with the help of lambda function.

So is this upgrade going to affect our current JIRA projects and all our customization will be lost please confirm on this.

Your answer will be a great help to us

[Darryl Lee]

Wait. Is it already March 31?

Why am I missing "See the old view" on 2/3 instances that I administer?

In both cases, I'm only seeing this [...] option:

NEW JIRA ISSUE VIEW

Find out more

Very odd. I've checked:

Personal Settings:

New Issue View: ON

New issue view transition Settings for site:

Move all users to the new issue view: OFF

I even had a bookmarklet that reloaded the page with ?oldIssueView=true appended to the URL, and that fails as well on 2/3 instances.

I know our days are numbered, but I wanted to point out another issue - about overly-long Multiselect Options getting truncated: https://jira.atlassian.com/browse/JRACLOUD-76124

[Svante Jacobsen]

We have still not been able to test/work with the new issue view because of bugs and missing functionality and we are still using the old one until they are fixed. It's getting very close to your transition deadline and I have not seen the least of actions on the issues raised for 1½-2 years now. Are you releasing the . (dot) menu with issue time logging and editing just the day before? You are not giving us much time to adapt.

[Mark Thompson]

@Svante Jacobsen - contact Atlassian support and ask to be put on the hold back list if your implementation isn't going to work until you get fixes.  

the .(dot) menu has been brought by my team as well.

[Greg D]

@Darryl Lee not sure if this is the root cause of your issue, but I have noticed that if you access an issue from a filter and it has the query parameter of ?filter=123 at the end of the URL, you cannot toggle back to old view from the action menu (that function is missing).

For some reason any time you have any additional query parameters in the URL of an issue, it causes some bugs (sometimes you cannot scroll down, you cannot click back to old view, sometimes other functionality is missing).  To be sure, I always just click the issue key link at the top (and it launches it in a new, fresh tab without the parameters).  Hopefully that helps.

[Michael Woffenden]

As we approach the end of March and the supposed (I dearly hope not!) end of the old (wonderful) issue view to be replaced by the new (dreadful) issue view, I heartily agree with many others.

"Give the customer the freedom of choice, don't force it upon us." Well said.

It's also been noted that Atlassian in fact does NOT use their own cloud Jira. If Atlassian were forced to use the cloud version (still terribly bad IMHO) they would wake up quickly and smell the coffee.

I have today spent a couple of hours with the old and new issue view side by side trying to get the NIV even close to the beautiful simplicity that we have with the old view. It was impossible to do so given the primitive nature of the new issue view and the inability to properly customize it. After the excercise I was exhausted and frustrated.

End users simply must be given the choice to use the old (fantastic) issue view and not be forced onto the new (pathetic) issue view.

What's so bad about that simple choice, Atlassian?

[Charlie Misonne]

I hope we can get the created date on a more visible place in the near future.

Please vote on JRACLOUD-70098 

[Jason Gainor]

After reading the high-level issue: https://jira.atlassian.com/browse/JRACLOUD-70555.

The comments being made in the issue are the same as they have been for the past two years and there is a consensus of:

• Reduce scrolling of new issue view - (First brought up June 2019 and no resolution yet) 
  • Fields with no change from the default are now displayed all the time. This change in behavior creates issues with 2-3 scroll wheel movements to get get to a field that was once visible without scrolling. 
  • There are a few issues related to scrolling linked to JRACLOUD-70555
    • This might solve most scrolling issues by hiding empty custom fields: https://jira.atlassian.com/browse/JRACLOUD-2997
    • Closed won't fix: https://jira.atlassian.com/browse/JRACLOUD-75181
    • Closed won't fix: https://jira.atlassian.com/browse/JRACLOUD-72098
• Reduce clicks of new issue view - (specifically allow ease of visibility of Zendesk tickets - First brought up June 2019 and no resolution yet)
  • Zendesk has moved to the right side and you need to scroll and expand a field all to find that there aren't any tickets. This integration and tickets were once visible without either action.
  • Scrolling, reading, precision clicking, and waiting for a transition is too long for something that is essential to some user's only interactions with the platform. 
  • I don't see any linked issues related to excessive clicking but would love to be corrected.

With these regressions (yes, regressions) in behavior, I forsee a switch to just using the API and making my own UI or strictly using a CLI for JIRA in my future. 

Like @Markus Troeszter said above:

Jira is a WORKING TOOL, not a WEBSITE, this is a huge difference!

time = money
hidden infos = more chance of getting missed and will lead into more wasted time = more wasted money

For now, I will be using Requestly to append the query param to every issue URL to get the old view until it is disabled.