Our team just started experiencing this bug in our next gen project, any updates on progress?  new view works in dashboards, agile boards, roadmaps, and email notifications but the bell notification for some reason doesnt show options like create a child issue

@Rob Simpson For me it also does not work yet. Also using Jira Cloud.

Got Jira Cloud

It previously happened only when I clicked on a comment notification. Now it works fine. I just tried both the issue link and focused comment links again, with good results. You are using JIRA Cloud @Sebastian Goltz?

@Rob Simpson clicked on a normal notification and not on a focused comment notification or am i wrong? For me its still a problem

Same here, clicking on a comment notification now takes me to the new view. So it sounds like it's fixed. Thanks for the update, Mack Baczynski!

I may be crazy, but clicking on the notifications now takes me to the new view. Is this officially fixed now?

Video

In addition, in our case the Workflow lists only 3 of the 5 states and one if the existing state, so the issue can only be transitioned to half of the possible states (workflow allows transitioning to any state from "All"). If you click on the issue number link at the top of the page, it still displays the old view. But if you Refresh that page, it displays the expected view without any change to the URL.

It seems this works as expected when a user receives a notification of a reaction to a message. Would love to just have that work with a comment as well. 

This really impacts the way customer see's the tool , would really appreciate some workaround , UI should be consistent that way it becomes more user friendly . 

We started using Jira a few months ago. Everywhere users work in the new issue interface. But when they switch to a task from a notification, they fall into a stupor. Everything is incomprehensible to them there, and the focus on comments is a completely optional feature.

When can we expect this to be fixed? I am sooo tired of removing the part of URL, that enforces the old issue view, to get to my task in the UI I am used to work with.

By the way, if this is in Short Term Backlog since 11.10.2019 I really wonder, what does your "Long Term Backlog" look like ...

SHORT TERM BACKLOG
A fix for this issue is required, and will be prioritised in the near future. This is because it’s more severe or pervasive than other issues.

Yeas, would be nice!

For my team and myself it would be way smarter to deactivate the "highlight / jump to mention"-Feature and instead load the new view, without highlighting the comment. The UX this way would be  more consistent.

Nico

Hey Atlassian,

any news here?

Best,
Florian

Hello bugged people,

I want to make clear first, that following mentions are not mentioned in a bad feeling (even i am annoyed).

We experience the same like Mack and others. In my responsibility is to make sure our communication to our clients is seamless and the operation of the Service Desk can be done in a professional way.

So we experience on this Bug following as an Incident with impact to:

1. Client Communication by fault of handling internal comments and client communication. This can't be avoided by human Factor but can be avoided by fixing and closing this bug. Whats actually a hard thing that this bug is open such long.
2. Image impact to our clients on faults happens on point 1. Our Clients may think we are working unprofessional. Sadly i am not allowed to mention on our client while i have to write apologize mails that the software we use just don't close a bug or rolled out a version with this kind of bug. Wasn't it discovered while Testing cause the Notification is one of the core functionality's ?!?
3. The Notification Functionality can not be considered as reliable anymore. Where the pure notification is working, but the action on notification can not be used cause of failure mentioned in point 1 & 2.
4. Based on mentioned previous points, we substitute to use the notification by a third party module to slack. Its kinda insane to tell to your people "jaaaaa, you get a notification, but don't use it! Better use the notification delivered by our slack channel". And Atlassian guys, you don't need to watch the faces of the people while telling it and i honestly feel a shame to tell them like that.
5. Writing Apologize mails costs me kinda time and this Bug forces me to have a higher attention on the Tickets as i wanted.
6. Classification as a Bug: Actually its a wrong and missing implementation to your customer. You should remove the possibility to click on a Link in a notification or deliver the full functionality. I am sure the notification with relation and call the depending Ticket/Entry was part of the development what simple is not delivered.

Finally i would love to discuss this but it doesn't seems like its worth it cause this Bug seems not to be on the Agenda to fix.

As mentioned as response from the Support Ticket i raised:

>>Since this would be a fundamental code change within Atlassian Cloud itself, there wouldn’t be too much we’d be able to do within the scope of this case, and the Dev Teams will provide future updates for the fix in the ticket I linked above.

>>While we'd love to say this will be fixed soon, we're unable to give an estimate for fix just yet. We will be following up with our bug fix team on your behalf for this issue, as they will need to continue to assess the impact and prioritize the issue against our current backlog. If you want to be updated on the progress, please feel free to add yourself as a watcher to the bug report.

As mentioned, this should have be done while rollout the new view and not pushing a wrong or not implemented functionality to cover it as a bug.

Please Atlassian keep and stay you doing something special as far its payed services.

Thank you,

Josef

for what its worth, this functionality would be very useful in adoption of the new view. In general, I feel the new view is simplified and nice, but how are we to expect our users to not respond to their notifications? We immediately lose the benefits of the new view if the way we engaged an issue was through a notification.

@vincent chin: I totally agree. 

mfaiz it's not a matter of pointing to a new issue view. The mechanism for focussed comment doesn't exist in the new issue view yet. It's on the issue side.

Hi there,

Unfortunately this is not a bug. The link you mentioned is a "focussed comment" link from the issue, which is expected to take you to that entity in the page. This is as yet not supported in the new issue view and thus it takes you to the old issue view. In other contexts the link will work, and eventually when that view is migrated over it will take you to the new view as well.

For the moment I'll close the ticket.

Regards,

Oliver