Documentation for GreenHopper 6.2.x. Documentation for earlier versions of GreenHopper is [available too].

(info) Note that this page only applies if you are using the Classic Boards (which are no longer being actively developed; read more).
If you are using the new board, please see Configuring Columns.

 

"Kanban is an agile development methodology that aims to assist you in visualising the workflow, limiting the work in progress and measuring lead time for your projects" (Kanban vs Scrum — Henrik Kniberg, 3rd April 2009).

GreenHopper allows you to set multiple constraints on each of the Task Board columns so that your team can easily visualise and monitor the progress of your workflow:

  • If a column exceeds one of its allocated constraints (i.e. by assigning/modifying issues such that their total in this column exceeds the column's specified maximum), the column will be highlighted in red.
  • If a column falls below a minimum for one of its allocated constraints (i.e. by assigning/modifying issues such that their total in this column falls below the column's specified minimum), the column will be highlighted in yellow.

To add constraints to a Task Board column and remove them,

  1. Log into JIRA.
  2. Select Agile > Classic in the top navigation bar. Then select Classic Task Board from the drop-down below the project name.
  3. Select your project from the project dropdown (top left of the Task Board above the 'Task Board' dropdown), if it is not already selected. The Task Board will refresh with information for your project.
  4. Click the View menu and select the Compact (Kanban) option.
  5. Locate the column that you want to add constraints to and click the icon at the top right of this column to open the column's configuration menu.
    (info) The configuration menu icon appears when you hover your mouse pointer over the top right of the column.
  6. Select the Column Constraints option and the 'Statistics' dialog box for this column opens. The default constraint is:
    • Standard Issue Count — the number of 'standard' issues (i.e. excluding sub-task issues ) that may belong to a given column at the same time.
      (info) There may be other constraints if your administrator has set them up.
  7. Click the Edit link for the relevant constraint and:
    • To add maximum or minimum limits to this constraint, enter the maximum or minimum values (or both) into the Capacity field.
      For example, if your business practices specify that no more than five issues should be present in any particular column or any one time, you would specify 'Max'=5 in each column. In practice, it is not normally required to specify any constraints on the last (right-most) column.
    • To remove maximum or minimum limits from this constraint, clear their values in either the maximum or minimum (or both) of the Capacity field.
      (warning) Be aware that you should not set these values to '0' as the value '0' itself is a constraint.
  8. Click the Update link to save your changes.
  9. Repeat steps 7 and 8 for each constraint you wish to modify.
  10. Click the Close button on the 'Statistics' dialog box to save all your changes. The Task Board will be refreshed with the column constraint updates applied.

(info) Please note the following information about column constraint highlights on the task board:

  • If a column's constraints have:
    • been exceeded, the column will be highlighted in red, with a triangular arrow at the top right of the column (see example below)
      (info) Clicking this triangular arrow opens the 'Statistics' dialog box for this column
    • fallen below capacity, the column will be highlighted in yellow, with a triangular arrow at the top left of the column (see example below).
  • If two or more of a column's constraints have been exceeded or have fallen below capacity, these will be indicated in a description at the top of the column (see example below).
  • If one or more of a column's constraints have been exceeded and any other of its constraints have fallen below capacity, the column will only indicate the constraints which have been been exceeded.

 


Screenshot: The task board showing the 'Standard Issue Count' constraint on the first column being exceeded


Screenshot: The Task Board showing the 'Standard Issue Count' constraint on the second column falling behind capacity

Screenshot: The Task Board showing the 'Standard Issue Count' constraints being exceeded on the first column and falling behind capacity on the second column


Screenshot: Section of the Task Board showing a column with two constraints being exceeded

  • No labels

14 Comments

  1. Anonymous

    Are constraints applied by context or are they project wide?

    1. Hello,

      They are project wide. If you are looking for constraints by context you may wish to explore the Rapid Board.

      Thank you.
      Nicholas

  2. Anonymous

    What are the minimum rights i need to set the column constraints for a specific project and version?

  3. Is there a way to set constraints for sub tasks as well (total)? Or any plan on adding support for that?

    Reason for asking is that our tasks ("stories") are sometimes epic and hence broken down with sub tasks.
    If not then any other way of handling related/"bulk of" tasks? 

    (solved in RapidBoard as bundled in GH 5.8 and above)

  4. Anonymous

    Hi,

     

    where I can set the individual column constrain (in my case excl. sub task)?

    The docu says above "There may be other constraints if your administrator has set them up. (Standard Issue Count was introduced in GreenHopper 4.2.1.)"

    But where I can set it as admin?

    The constraint drop down only shows NONE and Issue Count.

     

    thanks in advance

    alex

     

  5. Anonymous

    How to share constraint between multiple columns?

    I'd like have one constraint limiting number of issues in active development. The active development consists three columns: In Development, Ready for Test and In Testing.

    Is this possible?

     

  6. Where can I tweak the colors used for column constraints? Color blind guy here.

    1. Sorry Matt, not customisable at this time. Could I ask you to please log an issue in the GHS project?

       

      1.   GHS-5518 - Getting issue details... STATUS  created

  7. Is there a way I can change the constraints for different swimlanes? I want to have the expedited lane not count toward the limit so those can be worked on without worry no matter the wip amount. 

    1. Two contexts perhaps, one that includes expedited issues, one that doesn't?

  8. user-40563

    Is there a way I can get an alert email when a column breaks a limit (i.e., goes below the Min or above the Max)?  It would be nice if I got an alert when a board breaks a limit without having to check each board from time to time.

  9. Could I limit the "Column max " but by user? For example that one user can't have more than 2 tasks in progress at the same time.

  10. It seems that the only kind of constrained that was originally considered was the number of issues, which obviously ignores their complexity. 

    I  order resolved this I raise  GHS-12120 - Getting issue details... STATUS  feature request for being able to specify which numeric field to use when calculating the constraint. Instead of having a count(*) we should have sum(field).