Transitioning all Jira Cloud users to the new issue view

[Julia Foden]

Inactive users are not shown as such in the new issue view. When will this bug be fixed JRACLOUD-74382 ? Why is it not a child issue of JRACLOUD-70555 with the other new issue view bugs?

[Dmitry Astapkovich _Colined_]

And yet another question about spacing:

[Matthew Canham]

@Peter Fjelsten, currently JRACLOUD-70942 and JRACLOUD-72556 are two improvements that we plan on bringing back to the new issue view shortly after we transition to the new issue view.

@Rob Horan, that is correct. The "Edit screen" will remain as it is today, even after transitioning to the new issue view. We will be updating documentation to make it clear why there are separate view and edit screens and looking longer-term we will improve the full configuration experience.

@Ricardo Gomez & @Jeanne Howe, thank you for your comments. We are actively working on tidying up the JRACLOUD to give you more clarity on what will be coming before the transition and which improvement will come shortly after. Of the remaining subtasks onJRACLOUD-70555 that are still open, are there any in particular that are blocking your move to the new issue view?

@Mark Thompson, we have a team ready to help you with any Server End of Sale questions and you can reach them through support.

@Dmitry Astapkovich _Colined_, thanks for your detailed descriptions and screenshots. I've passed these on to our design team. Below is a screenshot of what time tracking looks like when moved to the left hand side. We expect to start rolling this out next week so you should have the chance to try it for yourself shortly.

@Greg D, thanks for your comment. We appreciate your support as we make this transition and your frequent candid feedback about what we're doing. You are correct that the modern stack that the new issue view is built upon will allow us to increase cycle times and take advantage of the latest technologies being built around Atlassian. The modernization of the create issue screen is currently underway, we are treating this work separate to the transition to the new issue view. We're working really hard internally to close the key feature parity gaps to enable everyone to make a smooth transition over to the new issue view. From that point onwards we'll continue to optimize and improve the new issue view.

@Julia Foden, thank you for getting in touch. JRACLOUD-74233 is something that we plan on working on shortly after transitioning to the new issue view. I'd be really interested to hear how this feature may be blocking your adoption of the new issue view and what your use case for it is? Regarding JRACLOUD-74382, thank you for pointing out that this could be a subtask of JRACLOUD-70555, this bug is in our team's backlog but is not currently a priority prior to transitioning to the new issue view.

@edgymitten, thanks for your comment. Keep an eye out for the upcoming changes to the new issue view. With the return of field tabs and the ability to move fields anywhere on an issue you should have the control that you require. In the new issue view layout configuration you are able drag fields into the "Hidden fields" section so that they do not show on the issue view.

Regarding the edit screen, your view and edit screens in your configuration are used to determine what is shown on the new issue view and which fields are editable. As part of your transition to the new issue view you may want to look at moving these fields that you were previously "hiding" in the edit screen into tabs on the view screen or into a group (coming soon).

[Stefan Höltker]

We recently migrated from jira server to cloud.

One of the biggest problems was as Drew Cottwell sais the shared issue layouts https://jira.atlassian.com/browse/JRACLOUD-71630

This is a nogo for us !

I can understand that you dont want to support two ways of presenting tickets, but u cant just force the user to use the other one when the new one dont support the full features of the old one !

[Frank Jimenez]

u buggin' matthew

[Dmitry Astapkovich _Colined_]

@Matthew Canham

Thanks for yet another update!

Here's my feedback on the Time Tracking section:

[Dmitry Astapkovich _Colined_]

And yet another thing that bugs me for long-long time: can we please-please-please have task/story icon on the header for sub-task?

[Jeanne Howe]

@Matthew Canham You asked "Of the remaining subtasks onJRACLOUD-70555 that are still open, are there any in particular that are blocking your move to the new issue view?"

ALL. OF. THEM. 

There are 96 unresolved BUGS on the ticket.

Your plan is to resolve 23 of them before we are force-fed this.... (insert your word here, mine are not suitable for publication).

This leaves 73 unresolved BUGS. And let's not kid ourselves, these are BUGS.

Add in the 8 issues resolved as "Won't Do" or "Wont Fix" and that number goes up to 81.

This doesn't even begin to address the issues that have been submitted as "Standard" issues and not sub-tasks of JRACLOUD-70555

[Yann JOUAN]

Please, just let us be able to create a linked ticket as easyly as it was with the old view

[Caroline Bartle]

@Yann JOUAN You can create a linked issue Jira Service Management and Jira Core projects in the new issue view.

To do this, click on "Link issue":

Then under the "linked issues" module, you'll see the option to "Create linked issue":

[Yann JOUAN]

@Caroline Bartle thx :)

[Nick]

Being able to quickly assign points, assign sprints, link stories, etc with the "." shortcut was the only thing that made the extremely slow and clunky UI somewhat palatable. I don't look forward to the new view, tried it again last week and quickly changed back.

[Marc Zampetti]

I agree with many others here that until ALL of the outstanding issues with the new issue view are resolved and available, and ALL of the existing functionality, including support from plugins, works in the new issue view, removing the option to continue to use the existing, not broken, working "classic issue view" is just poor customer support.

All it makes me do is spend time figuring out how to move away from Atlassian products as quick as possible.

So please update this plan and confirm that my business won't be impacted by this forced change until you have provided a solution that meets ALL of the needs that I currently have, which to be clear again, is an issue view that provides all of the same functionality as the existing view in terms of controlling layout, provides access to all functionality, and is supported by all plugins, or at least those plugins with a usage count of at least 10 customers.

[Mark Thompson]

@Marc Zampetti - hit the nail on the head.  Some larger organizations have both cloud and server implementations.  Needing to move from server to cloud and not having all the functional behavior of classic makes it easier to justify moving off Jira.  

[Ricardo Gomes]

With so many deficiencies and so many gaps to fulfill in Jira in terms of features or existing feature improvements that should be provided by Jira BUT are provided by other vendors in the form of add-ons, Atlassian decided to waste so much time on a new view that most people don't want. What a waste!

If you use Jira heavily, you know what I'm talking about here... It's annoying to see the number of basic features and improvements that Jira DOES NOT provide that are supplied by all kinds of vendors through add-ons which are, of course, paid.

Now, if you were to provide a new view that is totally customizable (I'm talking about a new "view" - i.e. UI/UX improvements - not the removal of actual functionality, which is actually what's happening here), then this change could be acceptable).

But instead, what you are doing is to make people swallow these horrible changes. I've never seen so much effort put into such a project failure like this one.

What a bad decision, Atlassian! Adding a crappy new view at the cost of breaking the heart of your customers by taking away the most precious value you added along the years (and the reason why you are where you are today) - high level of customization.

[Sheila]

@Matthew Canham  This is absolutely the worst news I've heard in a long time.  The new view is terrible and is missing some very key features and functionality that the current version has.  

You need to listen to your users and rethink this decision.  You need to read the comments from the vast majority of the users here and listen to what they are saying.  As the Product Manager it's your job to stand up for and represent the user community and not just push ahead with things that seem cool or interesting but are completely useless in reality.

There are so many issues with the next gen of Jira that I don't even know where to begin to list them all.  I don't know who was consulted on these changes but I suggest you revisit the entire approach.

I will be seriously investigating other options for our company to replace Atlassian all together just based on this decision.  

[Al]

@Caroline BartleI was using this, but haven't seen this link for months now.

This is what I see after clicking the "Link issue" button in tasks, sub-tasks, etc.. Any idea?

[Caroline Bartle]

Hi @Al - that's really unexpected.

The permission for creating linked issues is tied to the "linked issues" permission so the fact that you can see the linked issues module means that you have that permission. That applies to both Jira Service Management and Jira Core (not JSW, where this feature doesn't exist).

I'm sorry, I haven't been able to reproduce this problem, so I'd suggest raising a support ticket https://support.atlassian.com/contact/#/

[Temur Khalilov]

Hi, its very interesting. 

[Michael Green]

Suggestion: Make better use of the screen real estate - there's no need to have swathes of white space on the left and right.

[Mariusz Wroblewski]

Very disappointing news. I already tried to introduce new layout in my organisation twice and it got to the point where I'm asked to find another solution which would provide me similar EDIT screen we used to have because this new one is like a bag of mess. It simply doesn't fit out client onboarding process no matter how hard i tried to change it.

I'm trying to follow new UI trends but this is some kind of a new level of geekyness which my teams find hard to approve. I don't even mention management people who hate useless changes.

[Jane Kidney-Hermelin]

I am fairly new to JIRA and trying to learn how to use it more effectively for my team.  I am already not able to figure out many aspects of JIRA, I'm wondering how this will make it even more confusing.  Maybe it's time to look for a simpler product to tract development and testing. 

[Greg D]

Maybe since I believe that I went through all the stages of grief with this change, I feel the need to attempt to offer some ideas to others.  And I think when the tabs come back to the screens with the new groups, everyone will be a lot happier.

Dmitry, if you just click on that Time Tracking bar (or down in the "Work Log" tab) you can easily log work and edit logged time (to me, it is way more streamlined... the old time tracking screen is terrible and now you can put the field wherever you want along with having the tab at the bottom... and it includes subtasks now).  You and Michael are definitely correct about there being a lot of unneeded whitespace on wider screens, but I'm hoping that they will worry about the functional changes to bring this to feature parity first (and it looks like they are starting to knock those out, which is good).

For the people that use edit screens (Mariusz and others), we would previously do that too.  Instead, you can keep those fields off of the screen all together and use transition screens in your workflow (build transitions for when you need to edit things that should be restricted..... the nice thing about this is that you can actually control the permissions on who can do it... e.g. only Administrators can execute the transition and so they are the only ones who can edit the fields.... then you could choose to have them hidden or view-only on the issue screen)... you can also have fields hidden for users, but editable for API interactions now.  I was hoping that actual field-level security would come at some point too, but probably not.

Jane, the NextGen projects were built with you in mind, but they do strip Jira of a ton of power.  You will find that Jira is amazing because of its ability to be customized (there is a ton that you can do and Classic projects are much much better).  In fact, most of the outrage that you see here is because the newer changes have been reducing the ability to customize in favor of a simpler setup.  The learning curve can be steep at the very beginning, but it is worth it (as long as Atlassian fixes these things that we have been hollering about and moves on to introducing valuable features, haha).

[Greg D]

For whitespace I did notice that zooming in your browser actually fills the right and left space now (I think in the past it was maintaining that).  So it actually works really nicely if you want less whitespace.

[Rob Horan]

@Greg Dthe problem with your approach to the edit screen is you're assuming the value needs to be hidden, when for many the idea is to have a value entered at issue creation that can never be edited afterwards, but will still be visible.

As for zooming in on the browser, won't that affect all browser content?  Also, won't that make icons and menus appear larger as well? 

I'm not trying to pick your suggestions apart but if Atlassian is really going to put us all on a journey to the Cloud they need to make people want to reach that destination before they get a connecting flight to a different cloud.