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).

You can flag issues in GreenHopper to indicate that they require attention. Your project administrator needs to have set up a flagging field for your project before you can flag issues. A flagging field is essentially a JIRA custom field that you configure from GreenHopper.

(info) Please note: flagging an issue in GreenHopper does not change the issue's priority in JIRA, nor its relationship to other issues.

To flag an issue in GreenHopper Classic,

  1. Log into JIRA.
  2. Navigate to either the Classic Planning Board, Classic Task Board or Classic Chart Board:
    • Select Agile > Classic in the top navigation bar. Then select Classic Planning Board from the drop-down below the project name.
      or
    • Select Agile > Classic in the top navigation bar. Then select Classic Task Board from the drop-down below the project name.
      or
    • Select Agile > Classic in the top navigation bar. Then select Classic Chart Board from the drop-down below the project name.
  3. Select your project from the project dropdown in the top navigation bar, if it is not already selected.
  4. Find the issue that you wish to flag.
  5. Open the 'Actions' drop-down menu for the card by clicking the icon (which will appear when you hover over the Issue Type or Priority icons).
  6. Select Flag from the drop-down menu. The issue will display a (warning) symbol against it when you view issues as 'Summaries' or as a 'List' (the symbol will be at the end of the row when viewing issues as a list).
  7. If you want to unflag the issue, simply open the 'Actions' drop-down menu for the card and select Unflag.

 

Screenshot: Flagging an issue in GreenHopper

  • No labels

8 Comments

  1. Anonymous

    Jun 10, 2010

    I can't see the Action "drop-down" for each issue in the "Planning Board".  I only see the issue-type-icon infront of the issue-id-link. I am using GreenHopper 4.4. What am I missing?

  2. Anonymous

    Aug 27, 2010

    If you double click on the issue type icon, it opens a larger card and then I get a menu on the top right corner where I can flag the issue.

    It's not always easy to do it but it seem to work that way. It just did for me, perhaps it can work for you too.

  3. Anonymous

    Jan 30, 2011

    Can we set the system up where if an issue is flagged, an email notification gets sent out?  Example, if an issue is blocked, I want to send an email to the Scrum master.

  4. Anonymous

    Feb 25, 2011

    I'm trying to set up flagging in my project.

    I have administrator rights, and using the flags works perfectly for me.

    The people with developer rights does not have "edit issue" permissions (they are changing issue information in the step screens), and they are not able to set flags.

    Is there any other way that setting general "edit issue" permissions for all developers to get the flagging function to work for them?

  5. Anonymous

    Aug 30, 2011

    Hi,

    It is possible to have multiple type of flags, like block, security issue, etc?

    Thanks

    1. Nicholas Muldoon [Atlassian]

      Aug 31, 2011

      Hello,

      Please keep an eye on GHS-2268, a story that covers this feature.

      Thank you,
      Nicholas

  6. Anonymous

    Aug 28, 2012

    Hi!,

    is it possible to flag an issue in the new rapid board?

    Thanks,

    Sabrina

    1. Kim Poulsen

      Sept 11, 2012

      It is indeed possible. I have played around with card coloring based on a JQL like this

      flagged="Impediment"

      and that seems to work. Now I just need to figure out how to make flagging fast (would be nice with a ". flag issue" command) and how to clear any flags automatically once the issue is closed to get around irrelevant statuses on closed issues.



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.