Atlassian Team members are employees working across the company in a wide variety of roles.
October 29, 2023 edited
Hi @theigor - we've consolidated on this behaviour as it will allow you to see the history of how issues are carried across versions, and what version they get released in.
If you do not want this, you can drop the selected issues into the "Issues without version" card in the version panel - which will clear the versions; and then you can add those issues to a specific version.
Apologies that the change in behaviour here will cause you extra effort. Thanks for the feedback
Atlassian Team members are employees working across the company in a wide variety of roles.
October 29, 2023 edited
Hi @VINCENT DUPONT - we're bringing labels to the board over the next few days. After that, we do plan to make more filters available but I don't have an ETA on that. Thanks
Atlassian Team members are employees working across the company in a wide variety of roles.
October 29, 2023 edited
Hi @Dave Todaro - check out the View Settings top right of the page. We've just rolled this out and although it's still reasonably limited - we hope to build it out further over time. Thanks
Hi @Eoin, it seems that with the new version an important functionality has been lost. With the previous version, when you created a task a modal appeared at the bottom left and you had the option to add it directly to the current active Sprint. Now the modal only includes the general information. Thank you very much.
Why is the default EPIC selection not unselecting other EPICs? It's soooooo annoying. I have to keep scrolling through my list of EPICs to see which other EPIC is selected and then de-select it... Absolutely awful UX
At least give me a keyboard shortcut or something so I can, for example, select and de-select others with a ctrl+click...
You regressed a feature without giving me a way to get the previous functionality back!
Atlassian Team members are employees working across the company in a wide variety of roles.
October 30, 2023 edited
Hi @Tom HT - thanks for the feedback. We made the decision to align the behaviour of the epic panel with the filter bar for consistency purposes. Apologies for this change in behaviour for you.
Story points in Kanban: If I add my story points to display my Kanban backlog tickets, it puts the value on a new line, loads of real estate and makes the backlog just a wash of white dead space. (TBH, this is what it always did) If I look at my Scrum board backlog, showing the story points means that they are neatly tucked between status and priority - same horizontal line, neat and visibly tidy. Far easier to work with.
Why can't I have the same neat/tidy/helpful/non-real-estate wasting layout on my Kanban board as well as my Scrum board?
Feels like an oversight to deploy this simple functionality to Scrum and not Kanban - what's the point of an integrated system that allows me to work with/in both methodologies if they don't get the same user-supportive functionalities :-(
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
In a board with multiple projects, some project have a status label behind the title, but most do not. I can't find any documentation on this. Why are those labels there, can we give overall statuses to projects now, if so where do we do that?
@Eoin regarding the dropping onto versions regression - taking tickets and dropping them onto issues without a version and then onto the version you want is an OK short term workaround - thanks for the idea, but in general, it's a big hack. This seems like it should be a personal or project setting whether dropping an issue onto a version should augment with the version or replace. Thanks!
@Eoin I agree with @Vik 's comment above - the Kanban story points have always added bulk to the board and backlog. Since your team is making enhancements in this space, any chance this change could be added as well? I know Story Points are typically used in Scrum, but I find several Kanban teams like to use them too.
@Eoin - in the new Enhanced Backlog view, we have lost the ability to see 'remaining' hours when filtering the backlog (which is fundamental for planning sprints) — The 'Estimate' hours for the filter now show at the top of the grouping, but the 'Remaining' hours are missing — The totals for the grouping at the bottom now don't take into account the filter (as they did in the old view).
Is there any way we can show the 'Remaining' hours for the filter?
Atlassian Team members are employees working across the company in a wide variety of roles.
November 1, 2023 edited
Hi @Siobhan Flynn@Vik thanks for the suggestion. I know it's not ideal for you right now but in the long term we do want to make a true grid format available in the backlog. I can't commit to a date unfortunately. Thanks again
Atlassian Team members are employees working across the company in a wide variety of roles.
November 1, 2023 edited
Hi @Dennis Kuscu Looking at your image - I think your admin might have renamed "epic" to "project". And the status you see is from the project issue. Happy for you email me direct eryan@atlassian.com if that doesn't answer your questions and if you want to share another image. Thanks
@Eoin This new "feature" breaks the keyboard shortcuts J and K in all major browsers. Prior to this update thats working great moving through issues and transitioning to different status. Now after an issue is moved it moves through issues in the new column I just transitioned the issue to instead of remaining on the column I am in. I am terrified now that this new default is being forced on us. This is a major break for our workflow and I would consider a deal breaker issue for us. My next step is to open support. I have left feedback several times and its still broken. Please fix J and K.
468 comments