While there are some nice features in the new issue view, I would much rather keep the old issue view. I am constantly switching to the old issue view for several reasons but the MAIN reason is the issue "Edit" button. As a scrum master, I am responsible for ensuring data accuracy to support SFDC system integration, automation, and data-driven reporting. The "Edit" button allows me to efficiently update multiple fields at once and only sends ONE notification to watchers vs. a notification for EACH field update, which is NOT a good user experience for anyone.
Is this multi-field edit functionality going to be available in the new issue view BEFORE removing access to the old issue view?
Atlassian Team members are employees working across the company in a wide variety of roles.
December 21, 2022 edited
@Harold Prestage Thanks for pointing this out! The team has added a lot of features from feedback we've taken about the new issue view, and this is one of them.
@Lucy Peskett You can actually change the issue type of an issue by clicking on the top left. See one of my previous comments for a screenshot.
Atlassian Team members are employees working across the company in a wide variety of roles.
December 21, 2022 edited
Re layout: As someone who sees the pros and cons of both layouts (I like both issue views), I understand the frustration, especially to those who want everything on one screen.
From a development perspective, maintaining two issue views is unsustainable. Even though some of you prefer the old issue view, there are people who dislike it — which is why we made the new issue view in the first place. The problem with keeping the old issue view around is that it can’t be customised, which means it can never work for everyone. The new issue view — even though it might not work for you right now — on the other hand, is built on a code base that’ll allow us to make it more and more customisable as time goes on. Keeping the old issue view is slowing us down from making this new issue view even more customisable.
Put your most important fields in the Description fields section, especially if you want to have your most important information available “at a glance”.
Put your fields in priority order in the list. The higher up your fields are in your configuration, the higher up they’ll be on the issue view.
Hide fields you don’t care about in the More fields section, or under field tabs, especially if your problem is "clutter"
I have been an Atlassian Jira user for many, many years and never liked the new view.
In addition to all of the previous comments about how the old view is better, I would also like to add that I insert a lot of images into my Jiras and like to PrtScn and then Ctrl-v paste the images into the Description and Comments sections. With the old view, I can give the images meaningful filenames and make them thumbnails. Several users in my organization use the new view and the images appear all messed up (either to small so that you cannot see the important details, or to large so that you have to use horizontal scrolling which makes reading anything a pain - especially of you have to scroll way down to access the horizontal scroll bar for long Descriptions/Comments) - to fix this, I go into the old view and use the markup to change the images to thumbnail.
PLEASE "replace in kind" all the useful old view functionality before decommissioning it! PLEASE!
I never use the new view because I cannot find the fields that I need. I automatically switch to the old view. You should consider that even if the new layout is better, people may not want to switch from the old layout with which they are familiar.
This is very disappointing. The old issue view gives us for such user friendly view and operation. You can see what workflow options are available to you and also what the current status of the issue is. Also you can see what the problem is and the expectation. All right there in one place. Also you can easily reassign and forward notes/comments from within the issue. Also you can easily copy&paste screen captures into the issue via ctrl+C / V.
The main reason we use JIRA is to manage issues and this (old) view is what we need and makes life easier for us. The new view is so cumbersome and does not convey all the needed / important issue information. This will just add extra time for everyone to log issues. And then more time to understand/get the information out from them. And I can just see all the problems we're going to have with the developers who need clarity and efficiency. And the new view does not provide either.
Such a big step backwards :-( Please reconsider leaving the 'old' issue view in JIRA.
Completely get that you don't want parallel support two versions, and that you want to focus on the new one - even though I think the volume and directness of community feedback suggests this may be a bit premature...
The benefit you're touting of the new view is that it's adaptable. Could you create a Confluence page somewhere that step by step tells people how to make the new view look like the default old view? Tighten the field spacings, get rid of a bunch of scroll bars, put the important fields front & centre again, etc. This might help ease the transition for a lot of people. The irony here isn't lost on me.
- how to get rid of the WYSIWYG and paste comments in Markdown
- how to prevent things to happen when you are just trying to select some text to copy. No need for those 15 seconds to load a whole mini MS Word when you accidentally click somewhere that is not a button.
As allways, you're doing the things for worst. Hope that you keep the (horrible) current version for many years and stop doing changes only to justify your salary. Thank you for NOTHING.
I'm not a fan of the new view. In the old view, I could click onto a ticket, and all the information would be visible to me. With the new view, the main page contains information which isn't the most important, and I now need to scroll on the right bar to get the information I need. This has added time/clicks needed to get information for me, so would have always used the old view aswell.
@Bryan Ye I hear you: working piece of equipment slows us down, so we will give you not working piece of equipment, and in the future it will work.
It is not the old view which slows you down. It is decisions of your company.
So instead of forcing new view, company should sit with community and find a way to get out of that situation: What are biggest pain points with new view, what are bugs must be addressed before dumping old version. Spend 6 - 12 month polishing SLOWLY new view.
January 2024 success - fast, polished, fixed and functional view.
Sorry, but the new view is awful. The two panes make it difficult to find fields I want to view or use. Some fields are not visible in the new view but are in the old view.
@Bryan Ye I would say whatever you wrote does not make any sense: specially this part: "The new issue view — even though it might not work for you right now — on the other hand, is built on a code base that’ll allow us to make it more and more customisable as time goes on." How many bugs (ones your team accepted as a bug) has been reported for new view ? Could you bring numbers in ?
How much time passed , how many of those bugs has been fixed please provide a number!
If your code base was really the one you wrote then you had enough time to fix most of the bugs.
@Attila Varga (and anyone else looking for labels, including myself)
I was able to figure out how to add Labels to the view. This assumes you're starting from the new view.
Go to the Configure Fields with the gear icon link at the bottom right of the page.
If Labels is available in any of the sections, it can be moved to the appropriate place and you're done. Otherwise, continue on. I used the browser's find on page search to verify.
In the paragraph at the top of the page, follow the screen configure link. For me, it's the second link, labeled "Default Screen (migrated)".
At the bottom of the page, use the Select Field drop down to select Labels. It's not clear how to actually add it, sometimes, especially when you have a lot of fields (I do), so it may be easier to add a new "tab" and do it there. ( @Bryan Ye: this is cumbersome and could use at least a button to actually save it).
If you added the field from another "tab", it can be dragged to whatever tab you want.
You should be able to go back to the Configure Fields page and add Labels to whichever section you want.
You can also use this to add other missing fields. I also added Sprint, which works better than the legacy view we had on our really old version, since you can directly add the issue to the sprint rather than linking to the agile backlog.
@Bryan Ye, @Ahmud Auleear — I've been following all the comments here and working with the new view since we migrated to the cloud last week. The biggest problem that I've found is that while I think everything is available (if only after jumping through hoops) to the view, it's not generally discoverable.
I think you could assuage most of the complaints I've seen (except the UI design aspects, those cannot be solved easily for all people) by having an easy to use migrate feature (maybe available in the "Take a Tour", and probably in the configuration) that will pull in all of the fields that are visible in the legacy view and put them on the new view. Maybe not where it is in the legacy view, but put all of them there, doing all the back end configuration stuff for you. This would allow users to quickly get back into business and still have all the old fields, but still have everything very configurable.
I don't know your architecture, but to me, a full time web developer, it seems like this would be a relatively simple feature to add that could make a lot of people happy.
It's clear that @Ahmud Auleear wants to force this change with about 10 days of notice and without addressing serious issues.
Most people are out on holiday and the remainder of us struggling with the prospect of massive change to our work ecosystem. May i suggest resolving the issues this way?
@James Pillar - that's a good idea. I've tried that in the past and received a response which was basically "thanks for contacting us, we are always interested in feedback, we are doing our best to make JIRA better" (i.e. we're not going to change anything).
However, perhaps if we had the same message coming from multiple people.....
Perhaps you could suggest the wording of the response, and then allow individuals to add additional information at the end?
@John Rocha I just sent a link to this thread and ask if they had read the communities concerns. My issue is a rather small but, I don't like being ignored. If I can't use the basic 'New View' how can I even bring up other issues i may have? I made it a rule to express my concern once a week over the last year and to every available section of their team. I never received any feedback and the issues have never been addressed.
255 comments