Atlassian Team members are employees working across the company in a wide variety of roles.
October 19, 2023 edited
Hi @Christopher Martin - yes, if not resolve already it should be soon as it's rolling out at the moment. Let us know if you still have this issue in a few days. Thanks
Atlassian Team members are employees working across the company in a wide variety of roles.
October 19, 2023 edited
Hi @Jeff Murray - yes, we've removed some of the embedded View pages links on the backlog. We found the usage of these links to be extremely low and opted to remove them from the screen. We apologise for the inconvenience this will cause you. We do have the Pages feature now, and we will be looking at how we improve the sprints experience further in the coming year. Thanks for the message
Atlassian Team members are employees working across the company in a wide variety of roles.
October 19, 2023 edited
Hi @Danny Z Thanks for the message. Can you raise a support ticket for this? We want to get more clarity on the specific cases where load times have slowed and support will be able to look into your instance (with your approval). Thank you!
All this looks amazing and promising, but will this issue be fixed before the enhancement applies automatically? We have a lot of transitions with attachment validation and no one wants to go across all boards and turn that feature off.
Most things are nice - BUT: The estimatation view per person has changed significantly. Are you aware of this?
In the new view - that looks the same as the old one and apparently should display the same information - only Stories are counted. Bugs and Tasks, even if they have an estimated time, are not included.
In consider this a heavy bug. We usually add sub tasks in our sprint plannings and estimate the required time in hours (additionally to the story points). During the planning (creating the sprint backlog) we should have a quick way to see how much time is planned for the whole sprint.
See this one from our current sprint: All I did was changing the backlog view from the "old" to the "new experience".
The popping on and popping off of card fields as I scroll the board causes my cards to jusmp about and my client is having fits about it. I told them to turn off "enhance my board".
If I modify card fields it's because I want to see them, always.
I have noticed that when using a quick filter, the following message is displayed (see attached), even when the filter meets the conditions Can you please explain why?
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2023 edited
Hi @Jens Hassler - this is a slip on our part. We've turned off this specific change and will fix it before continuing rollout. We were out to 1% so appreciate the quick feedback on it. Thanks
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2023 edited
Hi @William Wilson - the board can have up to 5000 issues. Keen to hear feedback from customers with big boards as we should be seeing better performance for the majority of users that fall into this bucket. Thanks
As @Shane McLachlan mentioned - that's a huge deal to not be able to use basic ctrl+f to find a card on the page.
@Eoin can you confirm that it is gonna be fixed before the forced rollout to every site? Coz if it is not fixed I don't want to have that enhanced version enabled on my board. Thanks!
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2023 edited
Hi @Orly Dahan - is the issue in a status that hasn't been mapped to the board? Or no longer part of the board filter? You may need to raise a support ticket if you're unsure of these as it may be down to the configuration, and our support team can help you diagnose the problem as you can give them access to your instance. Thanks
Atlassian Team members are employees working across the company in a wide variety of roles.
October 22, 2023 edited
Hi @Shane McLachlan@Rus the browser ctrl-f function will no longer work on the new board in the same way as the old board. You will need to use the search box on the left side of the filter bar. We're rolling out a fix to ensure the scroll position is maintained on clearing the filters which will be out fully in the next few days (it's out to 10% of people as of now). Keen to hear your feedback on this approach when you get to try it out. Thanks.
@Eoin honestly this is completely unacceptable. There are certain "basic" things that one expects from a website, and using ctrl+f for searching is one of them. To me it is the same as if you would decide to create a separate button for ctrl+c to copy text and ctrl+v to paste it. Simply unnecessary and complicates the interaction with the board significantly. I don't want to use the search box to search on the page. I want to use ctrl+f as I would use on any other website.
I honestly cannot imagine this going thru the entire dev\prod planning lifecycle without anyone noticing. So how someone actually decided that it is a "good idea" to not have ctrl+f working on a board is beyond me.
@Eoin - typo on my part. I meant 5000 initially. And, since you know what the issue limitations are and have been, and you could clearly see that I was asking if that limitation has been increased at all, your answer is ingenuine. We need to be able to view more issues on our boards than that. As do many many many others.
I keep seeing comments about "performance improvements". When will your product perform well enough to be able to see the same number of issues and have the same functionality that I had on server?
5000 issues is not enough. We have dozens of projects, with tens of dozens of boards where MOST have over 5,000 issues, and this limitation has functionally broken our ability to manage sprints in Jira effectively, creating upwards of 2 months of additional development work for us, trying to re-engineer how we work with Jira.
At this point, it would have paid for itself twice over just to have gone to another platform, based on how dramatically our ability to do work in Jira changed from Server to Cloud.
And at the very least, it would be nice to have a tangible explanation for why I can't open a board in Jira with more than 5000 issues, and not have it be a generic answer of "reasons" or "computing power".
I'd like to see an honest answer. One that explains the limitations of the backend you chose and why you can't pull select data, and instead, have to pull the ENTIRE DATABASE to then parse the database information, and then present it... which is why it's so taxing. At least, that's my understanding, knowing what tools you are using to do all the work. If I'm wrong.. please.. correct me.
---
To anyone reading that is thinking about migrating to cloud. Don't. Look for something else. We're being charged not only for the number of users we have in production, but also on our sandbox, which we were told would not be the case. They continue to move core features into the marketplace. The newest iteration of cloud billing of "actions" seems to be impacting existing companies. And at this point, we keep hearing about performance improvements, but we still can't open a scrum board with more than 5000 issues in it. In 2023. Atlassian doesn't have the computing power to allow it's users to view more than 5000 issues. And Atlassian really doesn't 'appear' to care. The corporate offices have become overwhelmed with greed.
There is a Bug with the new Kanban Board. a search (ctrl + F) would be applied only on the front (the part of the board you see on the screen), and not the whole board. Plz check this. Thanks.
468 comments