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

You need a board so that you can view and work with issues in GreenHopper. A board displays issues from one or more projects. You can either use a board that someone else has created, or create a new board for yourself. You can create as many boards as you like.

There are two types of boards:

  • Scrum boards are for teams that plan their work in sprints.
  • Kanban boards are for teams that focus on managing and constraining their work-in-progress. Because work is not planned in advance using discrete time periods or versions, Kanban boards are visible in Work mode but not in Plan mode.

(tick) Before you begin, please note that you will need the JIRA 'Create Shared Objects' global permission before you can create a board. If you don't have this permission you can still create a board, but it will not be visible to other people as its filter will not be shared.

You can either copy an existing board, or create a completely new one.

Creating a Completely New Board

  1. Log into JIRA.
    (info) If you are on the GreenHopper Getting Started page, simply click either Create a new board or Create a new project and board, then select (or create) a project, type the name of your new board — and you're done! Otherwise, please continue:
  2. Select Agile > Manage Boards from the top navigation bar.
  3. Select Create from the Tools ('cog') menu at the top-right of the page.
  4. Either:
    • To create a Scrum board:

      • Click Select Scrum on the Presets tab (see Screenshot 1 below). You will be prompted to enter the name of your new board, select the project(s) you wish to view, and select what type of workflow to use (Simplified Workflow is recommended).
        (info) This will create a preconfigured Scrum board containing all the issues in your chosen project(s). Your Scrum board will have a JIRA filter with the following query:

        project = "[YOUR PROJECT(S)]" ORDER BY Rank ASC

        or:

    • To create a Kanban board:

      • Click Select Kanban on the Presets tab (see Screenshot 1 below). You will be prompted to enter the name of your new board, select the project(s) you wish to view, and select what type of workflow to use (Simplified Workflow is recommended).
        (info) This will create a preconfigured Kanban board containing all the issues in your chosen project(s) that do not belong to a released version (see the JIRA documentation on Managing Versions). Your Kanban board will have a JIRA filter with the following query:

        project = "[YOUR PROJECT(S)]" AND (fixVersion in unreleasedVersions() OR fixVersion is EMPTY) ORDER BY Rank ASC

        or:

    • To create a Kanban board that is based on a query of your own choosing:
      (info) Before you can do this, you must have access to at least one saved JIRA filter (either your own filter, or one that someone else has shared with you). If you don't, first create and save a new filter in JIRA (you may want to see the documentation on issue filters and JQL).
      • Click the Advanced tab (see Screenshot 2 below).
      • 'Saved Filter' — Select the issue filter to be used by this board (see some examples below).
        (info) If a colleague has not shared their saved filter with you, that filter will not be available for you to choose in this field.
      • 'Shares' shows which groups or projects roles have access to the currently selected saved filter. Your new board will be available to all users who have access to your chosen filter.
      • Click the 'Edit Filter' link if you wish to alter the JIRA filter's query. (You will only be able to do this if you are the owner of the JIRA filter. If you are not, then the owner's name will be shown instead of the 'Edit Filter' link.)

(info) Note that you cannot change the board type after creation (that is, a Scrum board cannot become a Kanban board, and vice versa).

On this page:

Related pages:

Congratulations — you have created a new board!

Your new board will be shown. At the top is a link that you may want to send to other people so that they can use your board.

Next steps:

Screenshot 1: Create a new board using Presets

Screenshot 2: Create a new board using the 'Advanced' tab

Some example JQL you might wish to use for your Saved Filter:

  • Select all issues which are Unscheduled or in an Unreleased Fix Version:

    project = GHS AND (fixVersion in unreleasedVersions() or fixVersion is empty

  • Select all issues you are interested in:

    (assignee = currentUser() or reporter = currentUser()) AND (fixVersion in unreleasedVersions() or fixVersion is empty)

  • Show all issues that you have participated in and have been updated in the last week. (info) This requires the JIRA Toolkit add-on.

    updatedDate > -7d AND Participants = currentUser()

  • Select all issues for a team (using a Label custom field named 'Team')

    (team = ateam or team = dreamteam or team = engineroom) AND (fixVersion in unreleasedVersions() or fixVersion is empty)

  • Only select my bugs for a bugfix team

    project = GHS AND team = bugfix AND issuetype = bug AND (fixVersion in unreleasedVersions() or fixVersion is empty)

  • Try fixVersion = earliestUnreleasedVersion(PROJECT KEY) to see all issues in the next Fix Version to be released:

    fixVersion = earliestUnreleasedVersion(PROJECT KEY)

(info) Refer to the JIRA documentation for your detailed JQL reference.

Let your imagination run wild and please comment below with your best JQL suggestions to help us learn what you are looking for.

Copying an Existing Board

If you would like to create a board that is similar to one you are already using, you can simply create a copy.

(info) Your new board will be based on the same JIRA issue filter as the original board. You will be the owner of the new board, but not necessarily of the filter, so you may not be able to edit the filter. However, once your new board is created, you can easily choose a different filter (e.g. to view a different project) — see Configuring Filters.

To copy a board:

  1. Select Agile > Manage Boards from the top navigation bar.
    .
  2. The Manage Boards screen will be displayed. Click the Copy link corresponding to the board of interest.

(tick) Alternatively, to quickly create a copy of the board you are currently viewing, simply select Copy from the Tools (cog) menu at the top right of the screen.


Next steps:

  • The configuration screen for your new board will be displayed. If you wish to make any changes, see Configuring Filters.
  • To start using your new board right away, click Use board at the top of the screen. See Using a Board.

42 Comments

  1. Vegard Vaage

    Some features I'd like to see on the Scrum rapid view plan tab:

    • Quick filter support  for the items that are not currently planned for the next sprint (below the blue line). This should be the same filters that are defined for the "work" tab). This means that I can quickly show issues from for instance one specific project and drag the issues I want into the sprint
    • Larger fonts for the issue title  when using the projector view (via the z key). These are currently smaller than the issue Id, which makes them hard to read.
    • Ability to set capacity for the planned sprint in story points, similar to the way it works on the old Scrum planning board.

  2. Anonymous

    Hi,

    Is the Scrum version of the Rapid Board assuming that there is only one agile team per JIRA project? 

    How should different agile teams sharing the same project should be planning their iteration.

    Eg. 1) Agile team 1 create their Rapid Board using Project A.

              They plan their iteration and start the sprint.

           2) Agile team 2 create their Rapid Board using Project A.

              How can they add issue to the sprint? 

    I am not sure, how this Scrum board can be used in the context of multiple agile team per project.

    Thanks for the information.

     

    1. Lukas Birn

      We have the same problem. This is a huge show stopper for us. We had to go back to the Kanban board because of this lacking functionality. Or is there a way how to do it?

    2. Anonymous

      Try this

      1. Create components that will represent "Agile Team 1" and "Agile Team 2"
      2. Assign all the backlog items to both the teams (a JIRA issue can have more than one Component against it)
      3. When creating a Rapid Board drop the "project = <<>>" and instead have for the Team 1's board the query as "component = "Agile Team1" and for team 2 "component = "Agile Team 2"
      4. Now there will be 2 Rapid boards both using different jql.
      5. You can now start a Sprint on both the Rapid Boards.
      6. The drawback of the above method is that both the teams can see what is the current Active Sprint (since their items still have the component names). You can remove that once you move the back log item into an active sprint by updating the issue to contain only one Component.

      Hope this helps and not too confusing (smile)

    3. Rosie Jameson [Atlassian]

      You may like to try the new Parallel Sprints feature (currently in Labs)

  3. Anonymous

    Do I need to change my JIRA issues to stories for the story point and time estimates to work? How then to track bug vs. new improvement vs. task?

    1. Rosie Jameson [Atlassian]

      You are right, the Story Points field is by default only available to issues of type "Story". But you can make the Story Points field available to other issue types as described here.

  4. Helmich Douma

    How can I set a restriction to users who can Create and/or Copy a Rapid board? users who don't have the JIRA 'Create Shared Objects' global permission can still copy a board (and create a mess)

    1. Rosie Jameson [Atlassian]

      We are looking into this. Please watch GHS-5400 - Getting issue details... STATUS  – thank you

       

  5. Anonymous

    Is it possible to toggle between different Versions within a project on the board? We keep multiple sections of our backlog using versions to represent different customers. However, features for any customer can be pulled into the same sprint. 

    1. Rosie Jameson [Atlassian]

      You may want to try using Quick Filters for this?

      1. A. Gilles

        Thanks for the suggestion. It seems as though using the Quick Filters also filters the issues in the Sprint, is that the case? If so, this makes it difficult to use as once you filter for the Version we are interested in, all of the issues in the sprint disappear.

         

        Thanks

  6. Stuart Wilson

    Is is possible to change the view of the items on the Scrum Board? A user has asked me whether we could add the "Original Estimate" field to the view of each item on the board but I can't figure out how to do this or whether it is possible.

    1. Rosie Jameson [Atlassian]

      At this time you can only add text fields, but other types of fields will be supported in the near future. Please watch Configuring the Issue Detail View

  7. Wayne Ingram

    It is possible to assign sub tasks to sprints? Currently my backlog is only showing Task level items?

  8. Anonymous

    Is it possible to show names of  assigned users on the cards in the scrum board?

  9. Anonymous

    Now that we've upgraded, how do we migrate our Classic Taskboards & backlogs to the new Boards to take advantage of the better features? Can find no imformation on migration of Boards. We'd be going from Classic to a Scrum Board. We also want to take our backlogs with us. Ty!

  10. Parth

    As an admin I need to control who can create boards, This way boards are more organised.

    For example

    People can create test boards and push same issue into multiple sprints as they want.

    1. Laszlo Kremer

      We need a separate permission for that. People are welcome to create shared objects like filters, but they shouldn't be able creating boards The board list can easily get messy with all the Copy of .. boards just because users accidentally click on the copy menuitem.

       

      The captcha is really annoying. I start not like commenting here as it means additional minutes of captchaing.

  11. Anonymous

    I created a new board using the default settings, why it's not showing all the issues. It seems like it has limit on # of issues it can display in the backlog section

     

  12. Anonymous

    When I started my board, I selected Kanban, but we will be using Scrum instead. The directions say you change it later. Although I've tried to change it to be Scrum, the Plan link is grayed out.

    1. Rosie Jameson [Atlassian]

      Hi, sorry but you cannot change the board type. I've moved the note about this higher up the page, and reworded it slightly.

  13. Anonymous

    How do I add or change the columns on my board? For example I want to add a column for Review. Also how are blocked stories visualized?

     

  14. Dimi

    Hi,

    is it possible to create a template for new Greenhopper boards (like it was for classic) ?

    It is a big overhead to customize all filters, columns, etc. for every new projekt.

    Thank´s

     

     

    1. Rosie Jameson [Atlassian]

      You may find it helpful to copy an existing board?

  15. Anonymous

    Is it possible for multiple users to modify the same rapid board, or can only the owner of the board modify it?

    1. Rosie Jameson [Atlassian]

      At this time, only the owner. Please see the comments on Configuring a Board for related discussion and issues.

  16. Anonymous

    Does anyone know how to add the "Assigned To" to display on the planning board? We would like to be able to see what stories are assigned to which developer. We just upgraded to greenhopper 6.1

  17. Anonymous

    When creating a new board, how can I set the system to apply the Greenhopper Simplified Workflow to it off the bat instead of me needing to change it after the fact and perform a bunch of cleanup?  Or, might this be on a project level?

     

    The issue I have is that after simplifying the workflow using the button, I still have all of the old workflow's status in there.  WHat I want to start with is simply To Do, In Progress, and Done - and have the workflow be correct to resolve items when being marked as done.

  18. Anonymous

    after creating a new board I noticed that when I work from the board options that some of the issues have the issue number with a line thru the text like they are crossed off.  for examples CRT-500  even though the issue has not been completed. if you click on the issue number it does not appear to have been crossed out.  it only displays that way in the work board.  how can this be resolved

    1. Rosie Jameson [Atlassian]

      Issues that have had their Resolution field set are automatically shown in strikethrough text throughout JIRA and Greenhopper. Please contact http://support.atlassian.com if this seems inconsistent with the behaviour on your board.

  19. Anonymous

    I'm trying to understand how rapid boards relate to workflows.  If we are using a workflow that has been modified from the default workflow, then we create a board against that project, should the board represent the workflow?  If not, should we modify the board to reflect the new workflow?

    1. Rosie Jameson [Atlassian]

      You will need to modify the columns to make sure that each of your workflow statuses is mapped to a column – please see Configuring Columns

  20. Anonymous

    On the Planning board I can only see Tasks, but not sub-tasks under the tasks.  How do I make them viewable in the Planning board?

    Also:

    In the planning board, I would like to see Tasks that do not have story points associated with them directly, to sum up the story points of the child tasks and display it for the parent with a sigma appended to indicate it's a summation.

  21. Edwin Stol

    When you plan the Tasks in a sprint, the sub-tasks will 'automagically' be planned in the same sprint as well.
    if you do not want that, you should convert them to an issue.

    The summation is something that's on the roadmap, i believe.

  22. Anonymous

    How do I migrate an existing backlog to a Scrum Board?  When I create a board for this using a pre-existing filter (we use the fix version of "backlog" to filter which tickets are in the backlog) and use the existing filter, the board automatically puts me in  "work mode" and I'm unable to navigate to "plan mode". I need to be able to migrate our backlog to a board in "plan mode" so I can prioritize the work there and create sprints around it.  Help?

    1. Rosie Jameson [Atlassian]

      It sounds like you may have created a Kanban board instead of a Scrum board. Can you please contact http://support.atlassian.com ?

  23. Anonymous

    I created a scrum board with issues from multiple projects. Some of these issues are also tracked in kanban boards within other projects. When issue is resolved, it immediately drops off my agile board but can be seen in other boards within it's project. How do I ensure that issues remain on my board when resolved without having to move the issues to my project?

  24. cathy waters

    We have a JIRA project that has issues in a Kanban Board. A colleague want's to trial using the same project and issues in a Scrum Board. When we create the Scrum Board with an identical filter no issues show up in it, even though the filter when viewed in Issue Navigator contains several Issues. I've followed the directions in " Some issues not showing in plan or work mode of the board, " but the workaround doesn't seem to apply (we already had no limit). Is there anything else we can do, shy of deleting the existing Kanban Boards?

    1. Rosie Jameson [Atlassian]

      You may need to double-check your column mappings.

      If that doesn't help, can you please contact http://support.atlassian.com ?

  25. Tom Haraldsen

    How do I copy a board without rearranging the swimlanes?

  26. Amy Balmain

    I've created a filter with Order by rank asc and I still get asked when I create the board to Add Rank.  I don't understand why.

     

    Project = "XXXX" and assignee = "xxxx" and labels = xxxx order by rank asc
    Ranking is disabled, as the Filter Query is not ordered by Rank



Log a request with our support team.



Raise an issue for our developers.



See answers from the community.



Tweet, blog and update our documentation.

Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.