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 boards, please see Configuring a Board instead.

GreenHopper contexts help streamline the view of your project by filtering and highlighting issues based on preset criteria. You can hide and/or highlight certain issues via a JIRA issue filter or custom criteria.

Contexts are available in the Planning Board, Task Board, Chart Board and Released Board. A different context can be used on each board.

On this page:

Selecting a Context

To select a context,

  1. Log into JIRA.
  2. Click the Agile menu in the top navigation bar.
  3. Select the Planning Board or other board to which this context applies.
    • If you have chosen the Planning Board, select the mode to which this context applies.
  4. Select your desired context from the Context dropdown (next to the Project dropdown). The Board will refresh and the cards displayed will be filtered according to the selected context.

 

You can select a context for each of the following:

  • Planning Board — 'Project Overview' mode
  • Planning Board — 'Version' mode
  • Planning Board — 'Component' mode
  • Planning Board — 'Assignee' mode
  • Chart Board
  • Released Board
  • Task Board
    Your choices for each of these will be remembered.

GreenHopper comes with 2 built-in contexts:

  1. 'On the fly' context — A non-deletable context that will allow all logged-in users to build new contexts (See the 'Creating a New Context' section below). Any changes that a user makes to this context will only persist for the current session and will not be saved.
  2. 'Default' context — A non-deletable context that only people with the 'Administer Projectspermission can edit and that is shared with all users and anonymous users (if your project is public). It is very important to note that editing this context will affect all users that use that context.

 

 

Modifying a Context

You can change the sorting and the filters and highlighting of the selected context via the context dropdown. If you have the 'Administer Projectspermission you can share your context with other users, as well as remove contexts.

To modify a context,

  1. Log into JIRA.
  2. Click the Agile menu in the top navigation bar.
  3. Select the Planning Board or other board to which this context applies.
    • If you have chosen the Planning Board, select the mode to which this context applies.
  4. Select Manage from the Context dropdown (next to the project dropdown). The Edit Context window will display:
    • General tab:
      • Context name — Edit the name of your context.
      • Share — Check this checkbox to share the context with other users. User will then be able to select this context from their context dropdowns. Please note, you must have the 'Administer Projectspermission before you can share a context.
    • Sorting tab — Select a different field by which to sort your context.
    • Filter tab — Edit the filter criteria as described below.
    • Highlight tab — Edit the highlight criteria as described below.
    • Delete — Click this button to delete the context. You must be the creator of the context to delete it. Please note that once you have deleted a context there is no way to restore it. You will need to recreate it manually.

 

Creating a New Context

To create a new context,

  1. Log into JIRA.
  2. Click the Agile menu in the top navigation bar.
  3. Select the Planning Board or other board to which this context applies.
    • If you have chosen the Planning Board, select the mode to which this context applies.
  4. Select New from the Context dropdown (next to the project dropdown). The New Context window will display, with four tabs as shown below.
    • General tab:
      • Context name — Enter a name for your new context.
      • Share — Check this checkbox to share the context with other users. User will then be able to select this context from their context dropdowns. Please note, you must be have the the 'Administer Projectspermission before you can share a context.
    • Sorting tab — Select a field by which to sort the issues in your new context, and whether to sort the field in ascending or descending order.
    • Filter tab — Select one or more existing JIRA issue filters to use to filter your issues. Select None if you only want to use the custom filter settings specified on this page.
      (warning) Note: If you select a JIRA filter, and intend to share this context with other users, make sure that those users have access to the JIRA filter — otherwise this context will show them an empty board.
      In the Specific Criteria filter section, select the fields to filter on. If an existing JIRA filter has been selected, these fields will be filtered on in addition to the selected JIRA filter:
      • Statuses — multi selection
      • Issue Type(s) — multi selection
      • Issue Priorities — multi selection
      • Assignee(s) — single selection
      • Component(s) — multi selection
    • Highlight tab ---The 'Highlight' section emphasises issues in the context that match the specified search query. The highlight search query works identically to the filter(s) described in the previous step.
  5. Click Save and apply to save your changes.

 

 

Screenshot: New Context - 'General' Tab

Screenshot: New Context - 'Sorting' Tab

Screenshot: New Context - 'Filter' Tab

Screenshot: New Context - 'Highlight' Tab

18 Comments

  1. Anonymous

    This explains the mechanics, but doesn't explain why you would want to use contexts or what they are for.  The concept is far too abstract.  Can you give some practical examples of how a context might be used and what they could be called?

    1. Jens Schauder

      I use it for filtering.

      In the Planning Board you have a couple of basic filter otpions, but you can't use a saved search. So I create a context to which you can assign a search and use the search this way.

      One specific use case is to have a list of stories that aren't estimated yet. With my Context 'To be Estimated' based on a saved search I have this list available and can print it as cards as preperation for a meeting.

      I guess more of this stuff is possible since you can define 'highlighting' for a context  ... still needs some exploring

      1. Anonymous

        So I'm trying as well to get my head around this abstract concept, and thought that the suggestion of a "To be Estimated" context for the Planning Board was reasonable. However, the available filters do not include testing whether there is a value in the Story Points field.

        1. Scott Barrett

          You have to create a Jira filter under the issues tab.  You can create an advanced filter using '"Story Points" is EMPTY' to test that the Story Point field is empty.  Then save that as a new filter which can then be used to create and manage your contexts.

  2. Anonymous

    Why does the Rank field not allow anything other than ascending as an option for sorting?

  3. Anonymous

    Context font is way too big. Makes it seem like it as or more important than the Project name it is sitting next to – very user unfriendly to have big "Default" on a page prominently placed. Most will use the default context in any case or at least in the beginning of the project.  I also agree with the posting above this concept has not been explained with clear examples.

  4. Anonymous

    Under "Selecting a Context" I read: "Your choices for each of these will be remembered."

    what does that mean exactly? I feel extremely confused when if I select e.g. "Planning Board" and GreenHopper decides to change my context that I just selected ...

    1. Scott Barrett

      This means that once you select a context for a specific board that context will be used each time you revisit that board until you change your selection.  This allows you to close and reopen a window without having to reselect the context.  It can be a little frustrating if you are trying to work on multiple boards with the same context and you are switching between contexts often.

  5. Anonymous

    Some of my contexts now have asterisks * next to them - and I can't load them.  When I choose one of those contexts, it displays the default context instead.  I have no way of managing those contexts any more - they were created by me and I'm the administrator - how do I get at them, and what is the asterisk all about?

    1. Harald L. Schraut

      I'm having the exact same problem that all of sudden I can't access the contexts any more which were created by myself some months ago. Have you found the cause of the issue or resolved the issue in some way?

      By the way, the asterisk means that the context has been made public and can be accessed by others as well.

      1. Frank Han

        Same problem here. I create a new context, and it works fine. It displays only those issues I have previously created a filter for. Then I switch back to Default and back to my newly created context again, and ... poof! Gone. It only shows the default issues, even though the context name is an option in the drop down. This would be very useful to manage certain issues (e.g. to be estimated as mentioned above) IF ONLY IT WORKED!!!

        Furthermore, when I go to "manage" my context, it doesn't allow me to edit or delete my newly created context. They continue to show in the drop down, but I can't manage them at all. They are now displayed there forever and don't even work!

  6. Anonymous

    hello

    I am a new user. my question is: what is the relation between the filter selected within a context, and the version/assignee selection on the taskborad or planning board page ?

    If my filter includes some fltering on the versions ( i.e all issues for versions 4 and 5 ) - will I see all these issues, or only the ones according to the version selected in the main dropdown ?

    which one will override?

  7. Joshua Bennett

    I have been digging but unable to find if there is some way to have a context copy to/from another Project.  I am building some wallboards for my team and want to use Contexts to filter with "Name's Due Issues" but we have many Projects and don't want to have to rebuild the contexts in each one for each of our developers.

     

    Thoughts?

  8. Anonymous

    Why does sorting in descending order on a numeric field assume that "None" is the highest value and places it at the top?  

  9. Anonymous

    Hi. I have two boards for the same project. Those are boards for two different teams that work on the same project. When I create a Sprin in one of those boards it appears in the other board two. How can I prevent that from happening? I need a single backlog for the projet, but two different boards to organize work.

    Thanks

    1. You may like to try the new Parallel Sprints (you will need to enable this in Labs). It's not exactly what you describe, but may be helpful.

  10. Anonymous

    I can't seem to highlight issues in Unscheduled. It is very strange, as it works in all other versions.

  11. Anonymous

    I can't seem to create a new context in my project and have all the permissions. Is there another place I should check?