Index
[Downloads (PDF, HTML & XML formats)]
[Other versions]
Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].
Work mode is where you transition your cards (issues) through a series of columns (statuses).
To access a board in Work mode:
Screenshot: a Kanban board in 'Work' mode (click to enlarge)
In Work mode you can:
Note:
column constraints apply to the total number of issues in a column, regardless of whether some issues are currently hidden because a Quick Filter is in use.
swimlanes can be based on criteria of your choice. Swimlane issue counts are affected by Quick Filters, that is, issues hidden by a Quick Filter will be excluded from the swimlane count.
Press "-" to expand/collapse all swimlanes.
for Kanban boards, you can specify a Work sub-filter, which refines the issues returned by your board's filter (see Configuring Filters). By default this sub-filter includes issues with no fix version or unreleased fix versions. So when the Release link is used to release a Kanban version, the completed issue will no longer be shown in the Done column.
On this page:
Related pages:
A Quick Filter refines the collection of issues displayed on your board. Quick Filters appear immediately below the board name in Work mode and Plan mode. Click a Quick Filter to apply it (click it again to turn it off). By default your board includes two Quick Filters: If any custom Quick Filters have been configured for your board, they will appear next to Only My Issues and Recently Updated.
32 Comments
Anonymous
Hi, I was just wondering why resolved issues are marked with strikethrough - they guys I am working with use resolved to mean ready for test and to strike it through looks like its done - is there anyway to change this?
Joel Robinson
You could configure the columns to include a Resolved/Ready For Test column or you could keep resolved issues in the In Progress column which is what I've done. It doesn't resolve the strikethrough font issue but would create a better distinction between Resolved and Closed issues.
Anonymous
That is what we do. We have Open, In Dev, In QA, Wtg Release where In Dev and In QA both mean In Progress, but whose queue the issue is in. Only until is passes QA do we set the Resolution to Resolved/Completed and it is in Wtg Release. But, Resolved for us means it has passed QA and is wtg deployment.
JMTyler
Unfortunately, it's not possible. Currently, the strikethrough style is closely coupled with the Resolution field.
There is a JIRA ticket for them to improve this feature and allow administrators to define exactly when to show the strikethrough - based on any chosen Resolution, any chosen Status... whatever we want. I suggest you login to Atlassian's own JIRA instance and vote on the issue, if you ever want to see this feature improved.
Karie Kelly
There is a tip that states to use - to expand/collapse all swimlanes. I could collapse all using -, but that doesn't work for expand. Nor does +. What keyboard shortcut do we use for expand all?
Rosie Jameson [Atlassian]
"-" should work for both expand all and collapse all. Can you please contact http://support.atlassian.com ?
Rogério R. Alcântara
I need to put the board on a monitor in the room for everyone to see.
Is there any way to get refresh automatically?
shaymandel
You can use Mozilla as the browser, with the ReloadEvery addon: https://addons.mozilla.org/en-us/firefox/addon/reloadevery/
Anonymous
Is there a way to change how the Assignee is displayed? Currently it is a thumbnail picture, but we want to use names instead. I can hover the mouse over the picture, but we don't use pictures at all so the thumbnail isn't useful at all for us.
Anonymous
I second this request. Does anyone have insight into this?
Kev Roberts
At the moment our scrum task board is showing the original estimate for each task. Is there a way to change this to show the remaining estimate please? This would help me getter a better overall impression of where we are in terms of delivering each sprint.
Joel Robinson
Same here. The minute I switched our team over to this board, I got several emails from the team asking about why the remaining time doesn't show up on the cards in the Work view.
troy
we have 2 or 3 status in our workflow.i.e for eg.if there is a column "To Do" in the work mode of the task board then it has status "ready for development" , "in Development" and "ready to resolved".In the adjacent column "Resolved" there is a status "work done".
Is it possible to drag a task from the "to do" column with the status "ready for deployment" and drop it directly to the "Resolved" column.When i do this would the status keep traversing from "ready for deployment" to "in development" to.......etc......to "work done".
Kindly note that we are using the latest scrum boards and not the classic ones.
Anonymous
Can someone comment on why there are separate sections? For example, in the Kanban sample, there are 2 sections: Expedite and Everything Else.
It appears that issues with subtasks are put in separate sections. Is that true? It's a little annoying since I don't really want to have issues separated out based on whether it has a subtask. Is there a way to not make issues with subtasks go into a separate section? Somehow make it all a single list?
Also, how do you name each section? For example, the Scrum example has the name of the issue as the section but the Kanban example has named sections.
Rosie Jameson [Atlassian]
You can configure these sections to suit your needs — please see Configuring Swimlanes
Pavel Bulanov
Is there a way to somehow visually see bugs under relevant user-stories in Work Mode? So far on the board I can only see User Story with all its own sub-tasks. If they all are done I don't know if US can be completed - as there might be some (major) defects to the US which prevents me from completing it, while I won't see it on the work mode. Is there a workaround to this?
Rosie Jameson [Atlassian]
In future, Epics will likely be visible in Work mode, which may be helpful for you. You may like to watch/vote/comment on GHS-6426 - Getting issue details... STATUS .
Anonymous
In 6.1.1 using the scrum "plan" mode you can drag and drop a story to its related epic. How can you do that in the Kanban board?
Rosie Jameson [Atlassian]
Sorry, epics only apply to Scrum boards.
Anonymous
Thank you!
Anonymous
We are using stories and subtasks for our iterations. In scrum "work" mode subtasks are shown below their parent story. Is it possible to show the "story owner" (issue reporter) within the swim lane as it is possible in classic mode?
Rosie Jameson [Atlassian]
Hi, you may like to watch/vote/comment on GHS-3922 - Getting issue details... STATUS
Anonymous
Hi,
I've realized in Scrum board, work mode you cant transition tasks with drag and drop, yo have to go to "More Actions" in detail view or go to issues navigator to edit the task and changes its state. Is there any way of doing this inside Greenhopper as it happens with subtasks?
Thanks in advance
Anonymous
+1
Anonymous
I have never had issues dragging and dropping from one column to another in the scrum board. Make sure that your columns are configured with the statuses that the transitions are associated with. For example, if you go from Open to In Progress but you really move it from Open to In Dev, if In Dev is not a status mapped to the column In Progress, it won't allow you to transition it.
Alison Hughes
Please could we have an option to view a sprint that is not yet Opened. There is often a time delay in the sprint planning process so that developers are working on items from a planned sprint.
Rosie Jameson [Atlassian]
You may want to enable Parallel Sprints? (Please see GreenHopper Labs)
Alison Hughes
Yes - this has relieved a lot of the pressure after we started using this last month, but we don't want to start the sprint until it is absolutely agreed for management reporting reasons. I think this comes down to when a sprint is tagged on the issue as being a part of a sprint. We find it quite tricky to see how much work each developer has got in the planning stage ( we allocate work on a developer by developer basis assome tasks can only go to certain people ) , tagging it earlier would mean that we can do some complex searchs and reporting in JIRA instead of having to rely on the more limited schedule planning within greenhopper.
Olga Tenenika
Hi - a couple of questions for the Work tab, Scrum board:
Rosie Jameson [Atlassian]
Hi Olga, you may like to log requests for these features at https://jira.atlassian.com/browse/GHS
Lars Polling
Is it possible to add a field to the items in work mode? Now only the description field is available.
Rosie Jameson [Atlassian]
You may like to watch/vote/comment on GHS-3922 - Getting issue details... STATUS