Transitioning all Jira Cloud users to the new issue view

[Richard Wright]

Hi,

I see that "Related Projects" is listed as "Coming Soon". Is there an ETA for that? I couldn't find it in JRACLOUD-70555.

Thanks

[Jack Hunter [HeroCoders]]

@Matthew Canham,

Here is the New Issue View feedback from our Issue Checklist app's user:

I always need to click on "open checklist" to see my list, this is just ****ing ridicioulus.
Cant you push Jira to stop making such bad design decisions?
We need to see all checkpoints without always clicking this damn button.
And on left side, they are just too way far down below....

So, basically, they complain about apps integration in New Issue View and the fact that:

• The glance module is always collapsed (no way to pin it / keep it visible)
• The content module vertical position cannot be controlled

Both of these things were doable in Old Issue View. 

Feature request for the second bullet: https://ecosystem.atlassian.net/browse/ACJIRA-1561

Fun fact: Atlassian introduced collapsed by default Glance to improve page loading performance (so apps do not load straight away), but the app Glance content is loaded straight-away even if Glance stays collapsed and never opened 🙊

Cheers,
Jack

[Elizabeth Wimmer]

Adding my voice to all those upset about the forced transition to the new view on 31 March 2021. Should be left open as an option until parity is reached.

[Markus Troeszter]

Dont make us always do more clicks for the same process!
We need the checklist open and visible on the right side as its important to our workflow.
If its default always hidden, important notices and infos are just going to be overlooked and forgotten.

New designs should make things easier and more user-friendly, not other way round...

[Markus Troeszter]

More Issues with the new view:
- the slider/list for attachements is not really helpful. the actual version displays ALL of the attachement, now i have to slide or click through pages if there are more attachements. its a step backwards in usability
- why do i have to click on "view 4 more fields" on the right panel? another click more to see all infos i need! 
- to record time, there is no option any more to enter 1,5h for example, i always have to write 1h 30m

[Barrett Cope]

If keyboard shortcuts are not addressed by the time the new issue view is forced I will start shopping for other solutions. https://jira.atlassian.com/browse/JRACLOUD-69876

[Ben Garcia]

Welcome to the business version of Cyberpunk 2077.

[Andrew Fleming]

Hi all,

Not sure if this limitation has been covered here, but this is our biggest obstacle to moving to the new version. We use epics for laying out project work that crosses multiple Jira spaces.

Old version (note how I can choose which space those child tickets should be in):

New version (this option has been lost, and so all child tickets end up in the same space as the parent):

This is a really big deal for us, hoping there's a workaround that produces the same outcome.

Thanks,

Andrew

[Greg D]

Hey @Andrew Fleming we do the same thing with Epics that have issues from different projects all of the time.  It seems like New Issue View was originally built with the idea that you would be in a NextGen project and everything is siloed in that project.  If you just use the "Create" button at the top and make sure you have the "Epic Link" field on your applicable create screens, you can pick an Epic from any project:

You can do the same thing by just creating issues without an Epic and editing that Epic field on the full issue screen at any time later too.

Another trick is that you can "Created linked issue" off of an existing issue in the Epic and it will copy all fields with a value that are shared between the two issues that are on the create screen (they can even be optional in the field configuration which unfortunately do not show while creating... but works for this).  You can just click the "x" to clear the issue link if you just want the field values and didn't want them linked:

This is also handy for a lot of other use-cases.

[Rob Horan]

I just became aware of a bug that IMHO is an absolute blocker.  See https://jira.atlassian.com/browse/JRACLOUD-72667

If you create a transition from any status back to itself it will not appear in the workflow. 

This functionality is ABSOLUTELY CRITICAL - is there an ETA on the fix?

[Greg D]

Hey @Rob Horan I agree.  That one is really annoying and is one of the reasons that I switch back to Old View a lot.  That sub-task is In Progress and so Atlassian had said all of those sub-tasks on JRACLOUD-70555 that are in progress will be fixed before March 31st (not sure of a timeline besides that)

For me, the top reasons that I switch back to Old View are that I need to execute one of those transitions, I need to use an existing attachment in a comment, I want to make sure an image in a comment is not huge in a Jira email so I need thumbnail format, I need to quickly paste a date/time into a field, I need to find something recent in the issue history or old in the comments, or I need to quickly find a populated field value and cannot remember where it lives on the screen.  I think they are bringing the tabs back really, really soon from what I hear and then hopefully those others that are In Progress launch in the next couple of weeks so that we can be in a much better place and know what we are working with.

[Rob Horan]

I'm designing a workflow and need something far sooner than March 31st.  (like... Monday)

[Mark Thompson]

Tabs are coming back?  Basically what you are saying is Atlassian is making me do a crapload of work to update all my projects to work without tabs so they can bring them back.  That is a total waste of my time.  This update was not well thought out.

[Kerri Simpson]

@Matthew Canham is there any update on the old view please as we are moving closer to the new view being implemented?

(Matthew Canham ATLASSIAN TEAM Oct 06, 2020

@Kerri Simpson, thank you for clarifying. We have a team that is beginning to look into introducing remote issue links. I'll keep you posted over on JRACLOUD-74599 and will have this rolled out prior to transitioning all users over to the new issue view.)

[Ramon Alonso Soto]

It's hard to believe that the UX of "glances" is expected to be better than the tabs. Tabs allowed us to move between pre-grouped fields with a single click without loosing the general field focus on the top side of the view. Now with "glances" we have to click go watch into the glance and click back to see again the general view of all the glances. It forces the user to be moving back and forth, it's significantly worse when you deal with complex issue types where the content must be grouped and managed appropriately. 

I wish if the "old issue view" layout would be still available in a kind of "new issue view" tab layout. 

[Jac Dennington]

I too am getting VERY nervous about the forced change.  Our views are permanently on 'old' so we can see extensive custom fields under tabs.  I'm not seeing that in the new view yet and it will make a high profile project virtually unusable.  The 'project' is managing all the demand for strategic change across our organisation.  Tabs organise custom fields into  request, proposal and governance views, about 20 fields per tab.  Take away tabs => instant need to move off Jira as the mangling of field orders and views makes the database of 800 requests unusable.

[Clemens Martin]

Please stick to the old view. I hate the new one!

How can someone change the interface to such an unusable design...

[Rob Horan]

Had a team meeting with a customer and the consensus was that the loss of tabs was a serious blow against Jira Cloud.  

[Tomáš Vrabec]

Dear Atlassian,

why are your doing this?

Don't take this comment as the hatespeech, I always wanted to make you a better company, user-focused helping to your customers. I was community leader for almost 4 years. Made a dozens of offline sessions in four cities. 

Lets skip your server-kill decision. 

I have 8 cloud customers. Sized from 15 to 500 user. 

No-one. If you want the number its 0, no-one likes the new issue view. 

You made a tool. Customers likes the tool. Customers likes the UX, likes the UI. The tool suites theirs needs. Why are you doing this? Did you realized, that you are literally taking away the tool they like?

Customers doesn't care about your backend and architecture you are obviously rebuilding. 

Customers (admins and users) are working with front end. We are working 10+ years with something. And now, you are taking this away.

Please, share this comment inside the company. Please, share this with Mike and Scott.

And please, start responding to us!

We are the guys, who are giving you the money, for your food, mortgage, cars etc.

Warm Regards,

Tomáš Vrabec, Atlassian Solution Architect

[Sergey vc]

@Tomáš Vrabec  Perhaps all of us (haters of these innovations) aren't the target audience 🤷‍♂️ So there are the other guys who will are giving money.

[Dana Frost]

I feel for Atlassian.  This is a tough one. I think the main issue is this kind of "big bang" change.  It would have been easier to make small changes over time than making this huge change all at once.  But I also see much of the new view is related to an underlying change in the architecture which may be an improvement (for some) going forward.  These kid of changes are always a struggle. 

[Mark Thompson]

It would be less tough for Atlassian if they had a migration tool instead of forcing the work on Admins.  That isn't going to make any friends.  I've spent weeks updating my projects for the new view so it is seamless for my team.

I would suggest every admin do the following:

1.  Set yourself to the new view

2. Open a ticket in your project

3. Click the configure button in the lower right hand corner of the display

4. Update your field positions so that highly used fields are visible (this is pretty easy to figure out).

5. Add fields from other tabs using the link to the existing configuration link at the top of the page in #4.

Atlassian didn't make this easy.  Each project and ticket type needs to be updated manually because the configuration can't be shared.  This will allow you to try the new view early and see what people squawk about.  The new view does allow easier editing of fields but if you have lots of projects it is going to take some time to get the field positions updated.  Waiting until March 31 to start configuring isn't going to go well for you.

[Jeanne Howe]

@Dana Frost This is a tough one. But it should have been tough for Atlassian, not their customers. Here, in my opinion, is what they did:

• Push out half baked changes
• Expected customers to QE the changes
• Expected customers to submit Bugs
• Ignore customer comments/requests/needs
• Continue to push out half baked changes
• Expect customers to accept the lesser functionality and poor quality/design in March 2021

[Ricardo Gomes]

Can we be brutally honest here -

For starters, what pisses people off is the fact that the new "view" has nothing to do with just a view! 

Have you thought about that? Atlassian wouldn't make such a big move and actually walk backward with something so buggy, messy, chaotic, and unplanned if it wasn't for a very good reason - which we (as users) might actually not know for real.

To me, there's an underlying reason behind all these changes that are tightly connected with architecture or performance issues they could no longer sustain with the old view.

It's clearly not a usability improvement or view enhancement project. They're significantly changing the way they architecture their application, and we're paying the price.

Of course, there are visual changes but most of them are being contested and complained about, not to say hated by most people. 

Honestly, a project with a focus on improvement, usability, and client satisfaction, would never go this route. This is something else, folks...

[Tomáš Vrabec]

Totally agree @Ricardo Gomes - there is something huge behind. Some big mistakes were made years ago and with current view there is no way how to solve them.

Thats what I wrote few posts above. They are not changing the product. They are trying to migrate customers from old Jira to new Jira. But they are very different. And customers want the old one ...