Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-2268

As a reporter, I would like to be able to flag an issue with multiple types of flag

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • None
    • 19
    • 4
    • Hide
      Atlassian Status as at 07 December 2015

      Thanks for your feedback and comments, the JIRA team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com

      We understand that this is a significant issue for many of you, however we cannot provide any guidance at this time as to when, or if, we'll be implementing it.

      Kind regards,
      Martin
      JIRA Software

      Show
      Atlassian Status as at 07 December 2015 Thanks for your feedback and comments, the JIRA team is working hard to improve the product and we are aware of the many requests here on jira.atlassian.com We understand that this is a significant issue for many of you, however we cannot provide any guidance at this time as to when, or if, we'll be implementing it. Kind regards, Martin JIRA Software
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Is some departments we use the flagging feature to emphasise urgent which cannot wait to be prioritized before next planning meeting. Together with context, this gives the unplanned/planned issues velocity as well.

      But then we need to use other ways to track impeded tasks (status or priority field). But I like the way the flagging field highlights the issue on Planning Board and Task Board.

      Of course, everything of this can be solved, but it is not very neat and intuitive. I don't like to use the status for impediment, becuse it is not really a workflow status (You would need to be able to reach impeded from all status etc.). Priority is a bit lost after GH introduction, since ranking is the real priority. Priority has kinda become severity, even though you cannot change the name.

      Would you consider to improve the it feature to support multiple values, maybe even combined with multiple colored flag marker?

            [JSWSERVER-2268] As a reporter, I would like to be able to flag an issue with multiple types of flag

            Hi all, does anyone know of an equivalent feature request for Jira Cloud? And if so could you please share/link with this one? I could only find JSWCLOUD-21694 Allow changing the value for the field Flagged, which seems to be much more recent.

            Ivan Shtanichev added a comment - Hi all, does anyone know of an equivalent feature request for Jira Cloud? And if so could you please share/link with this one? I could only find  JSWCLOUD-21694 Allow changing the value for the field Flagged , which seems to be much more recent.

            Paul Taylor added a comment - - edited

            we have the same request and this is 6 years since the original request in this thread. we need a visual way to indicate particular types of impediment, sure we can use a field inside the ticket and maybe change the colour of the ticket, but we already use ticket colour to re-enforce the priority of a ticket because as someone said it is quite weak at attracting our teams attention to it

            Paul Taylor added a comment - - edited we have the same request and this is 6 years since the original request in this thread. we need a visual way to indicate particular types of impediment, sure we can use a field inside the ticket and maybe change the colour of the ticket, but we already use ticket colour to re-enforce the priority of a ticket because as someone said it is quite weak at attracting our teams attention to it

            +1
            We have currently the same request for our teams. It would improve their priority management which would be really usefull. 

            Adrien Pham added a comment - +1 We have currently the same request for our teams. It would improve their priority management which would be really usefull. 

            This feature would very much be appreciated. Atlassian did add the "Add Flag and add Comment" feature to the right click context sensitive menu to the cards on boards, which helps to speed up the flow, but a comment is still unstructured data and we'd like to be able to create dashboards with specific types of impediments (as there are different people tackling different types of impediments)

            Ronald van Rij added a comment - This feature would very much be appreciated. Atlassian did add the "Add Flag and add Comment" feature to the right click context sensitive menu to the cards on boards, which helps to speed up the flow, but a comment is still unstructured data and we'd like to be able to create dashboards with specific types of impediments (as there are different people tackling different types of impediments)

            Andy Cleff added a comment - - edited

            +1 as well.

            I see that JIRA's flagged field appears to allow multiple options:

             

            Has anyone tried adding more than the single "impediment"?

            Andy Cleff added a comment - - edited +1 as well. I see that JIRA's flagged field appears to allow multiple options:   Has anyone tried adding more than the single "impediment"?

            +1 as this would also greatly impact our ability to properly signal items.

            Kyle McMahon added a comment - +1 as this would also greatly impact our ability to properly signal items.

            mike added a comment -

            +1 for this big time. Would be really great for our team.

            mike added a comment - +1 for this big time. Would be really great for our team.

            KarenH added a comment -

            Agree flagged field could be improved by adding single select feature that each client configures to track types of blockers or reasons for blockers. This would help not only teams but entire organizations understand where they have the most opportunities for improvements and reduce blocker types. for example. Hope you just do something that 1) keeps the flag visible when someone adds it, but then enables a team to select a reason or type. This aspect should be configurable by the Jira Admin team for each client. Also, this should be editable in the details screen on the right side of the board, so teams don't have to open up the issue type to edit or select the reasons.

            KarenH added a comment - Agree flagged field could be improved by adding single select feature that each client configures to track types of blockers or reasons for blockers. This would help not only teams but entire organizations understand where they have the most opportunities for improvements and reduce blocker types. for example. Hope you just do something that 1) keeps the flag visible when someone adds it, but then enables a team to select a reason or type. This aspect should be configurable by the Jira Admin team for each client. Also, this should be editable in the details screen on the right side of the board, so teams don't have to open up the issue type to edit or select the reasons.

            +1 - I am looking for this

            Mike Scott added a comment - +1 - I am looking for this

            Toni Z added a comment -

            We have multiple groups which cross projects. There can be bi-directional dependencies. Configurable flags would be helpful in identifying and filtering these issues.
            Links are OK, but, not easily seen on the boards.
            Example:

            • Flag 1 - Group A depends on Group B to finish this
            • Flag 2 - Group C depends on Group A to finish this

            Toni Z added a comment - We have multiple groups which cross projects. There can be bi-directional dependencies. Configurable flags would be helpful in identifying and filtering these issues. Links are OK, but, not easily seen on the boards. Example: Flag 1 - Group A depends on Group B to finish this Flag 2 - Group C depends on Group A to finish this

              Unassigned Unassigned
              8057ebe7-b8ce-4524-9d73-b488c8fa9035 Deleted Account (Inactive)
              Votes:
              202 Vote for this issue
              Watchers:
              101 Start watching this issue

                Created:
                Updated: