If I have an issue opened in full screen how can I move it to the board for the project? I know I can do this from the backlog view by clicking on the context menu but I want to be able to do this from the issue view without switching to the backlog.
This is not the most helpful response. In the next gen project it clearly says "move to" as you can see in the attached screenshot (regardless of what is technically going on with containers). How can I move an issue from the issue view and not from the backlog view?
Yes, Atlassian have dumbed-down some things with Next-gen and used misleading phrases like "move to board". The issue view does not have any context of a board, because a board is a view, not a container.
To "move to board" from an issue view, you need to edit the issue, changing the data on it so that it matches what the board is selecting.
A board is a view of issues, you can filter that view and see the items in their status columns but getting an issue to appear on the board is the problem.
In next-gen projects if you use the backlog feature you can't make an issue appear on the board until you drag it/use the menus to "move" it from the backlog to the board on the backlog screen. The problem appears to be that the board only "selects" things that have been transitioned on this screen (or added directly on the board itself) but that status on the issue is not reflected in the issue UI. None of the other statuses (eg in progress/done) make it appear on the board without going through the backlog screen.
The board settings in the project are also simplistic so there is nothing we can change here.
It's harder than it should be to get an issue in progress. The following is a realistic flow for getting an issue in progress:
* Create the issue
* Navigate to the Issue page, try to get it onto the workboard
* Navigate to the Aggregate Issues page, try to get it onto the workboard
* Remember that the only place to get to the issue onto the workboard is actually from the Backlog page
* Navigate to the Backlog page
* Look for the issue
* Try to use Command + F browser keyboard shortcut, discover that Command + F triggers a popup
* Press Escape to close the popup, discover that escape doesn't close the popup
* Click the page to close the popup, clicking the page doesn't close the popup
* Click OK to close the popup
* Remember that the issue will be at the bottom of the Backlog page
* Try to use Command + Down Arrow browser keyboard shortcut, discover that Command + Down Arrow doesn't work
* Scroll to the bottom of the backlog page
* Click the triple dots menu
* Select the MOVE TO > Board menu item
* Navigate back to the Workboard
* Change the issue to In Progress
The workflow should be:
* Create the issue
* Click the issue
* Click the triple dots on the issue
* Select MOVE TO > Board
* Change the issue to In Progress
You should be able to move the issue to and from the backlog and workboard whenever viewing the Issue page, Aggregate Issues page, Backlog page, or Workboard page. Standard browser keyboard shortcuts like Command + F and Command + Down/Up should not be overloaded. Popups should be used minimally, pressing escape or clicking away from popups should close them.
I don't follow. Moving something to the board seems pretty appropriate terminology, unlike the "Move" feature that is used for more than just moving a ticket between projects. But I can appreciate the conflict.
I don't understand what you mean by "look at what the boards are selecting, then edit the issue to match."
I would love to understand what you are saying if this improves the current workflow.
Boards do not contain issues, they are a selection of issues, based on a filter. This is often "project = X" but could be anything (some boards have fixed filters you can't get to)
This make the word "move to board" completely inappropriate as a description of what you need to do to make an issue drop off one board and appear on another - you need to edit the issue to change what ever it is the boards are looking at to select the issue.
I suspect you do not mean "move to the board", I think you mean "take something out of the backlog (which is actually part of a board, defined by the same selection filter) and start progress on it by placing it in the first column on the active sprint/kanban board". That needs you to edit (probably transition) the issue.
When you are in a next-gen project there is only one Board. When you are on the Backlog page you can click the ellipsis menu of the issue and select "Move to Board" or if it is already on the board "Move to Backlog." So this seems pretty appropriate description of what we are talking about since this is how the feature actually works.
The premise of this conversation is about how to achieve this same functionality from the issue view instead of having to add the extra steps of going back to the Backlog page and searching for the ticket.
>Or forget the idea of "move" as it's not right, and just look at what the boards are selecting, then edit the issue to match.
>>You can't edit the issue to put it on the board. That's is the key problem.
This is exactly right, the point isn't the fact that I'm using "move" right or wrong, the point is: How does one quickly get an issue shown on the workboard? @Nic Brough _Adaptavist_ I understand the point you're making about the board being a filter of the issues; however, the problem is it doesn't make sense to remember to go to the Backlog page to get the Issue shown on the Workboard page. It makes sense to manipulate the Issue's position to and from Backlog and Workboard from any of the 3 pages: Backlog, Workboard, and Issue pages.
Yes, sorry, I over-egg that one. The point is not that "move" is right or wrong, it's an attempt to help people see what it is doing behind-the-scenes. Also the point that the backlog *is* the board, just a different view. In Scrum, the board is a different view of the issues at the top of the backlog, inside the sprint.
It's okay, and is useful to add insight into the underlying reasons for the structure of the issues, backlog, and workboard pages. However, even though in theory the workboard and backlog are just different views of one big list of issues, in practice they are links in a side menu that one needs to click into and the ellipsis menu available on an issue is inconsistent and incomplete depending on the page one is on. This leads to a confusing and asymmetric flow to expose an issue on the workboard or backlog and then move on to getting work done. It would be better if one could freely and easily "get a new issue in progress" or "kick an issue back to the backlog".
Getting an issue in progress now feels like I have to sift through our entire backlog every time I create a quick one point story just to get the thing in progress and surfaced on my workboard. It's frustrating and slow to scroll to the bottom of the backlog to find the one ellipsis that lands the thing on the workboard. We should be able to manage the lifecycle of an issue from the actual issue page and not need to navigate to different pages.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events