-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Configuration for the Flagged field doesn't seem to be provided for Rapid Boards (Scrum/Kanban). Being able to configure the Flagged Field in the deprecated Classic Boards, posed a couple of advantages:
- Users could configure different types of Flags (as suited for their usecases)
- From the board configuration, it is easy to determine in which field the flag for issues are stored in JIRA.
- Although the flagged field is not Locked by default, if it was deleted, admins could easily create and configure a new one etc.
Unfortunately, because this field is still unlocked by default, Rapid board users:
- Would often delete it and then wonder where all their Rapid Board Flags are being stored.
- Also, users who had been using their own/custom Flagged fields in Classic boards, before migrating to Rapid boards are prone to be even more confused about this because there is no longer an easy way to determine where this Issue flag data is stored like there was in the Classic Board Configuration Screen and Project Template configuration for classic boards.
This 'Flagging issues' feature should be configurable to some extent atleast in Rapid Boards as well
- duplicates
-
- Gathering Interest
[JSWSERVER-9969] Configuration of Flagged Field in Rapid Boards
| Workflow | Original: JAC Suggestion Workflow [ 3068009 ] | New: JAC Suggestion Workflow 3 [ 3661861 ] |
| Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Confluence Workflow - Public Facing v4 [ 2623416 ] | New: JAC Suggestion Workflow [ 3068009 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2324063 ] | New: Confluence Workflow - Public Facing v4 [ 2623416 ] |
| Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2044871 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2324063 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2033231 ] | New: JIRA PM Feature Request Workflow v2 [ 2044871 ] |
| Workflow | Original: JIRA PM Feature Request Workflow v2 [ 736127 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2033231 ] |
| Workflow | Original: GreenHopper Kanban Workflow v2 [ 562443 ] | New: JIRA PM Feature Request Workflow v2 [ 736127 ] |
| Issue Type | Original: Story [ 16 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Minor [ 4 ] | |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Resolution | New: Duplicate [ 3 ] | |
| Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
| Description |
Original:
Configuration for the Flagged field doesn't seem to be provided for Rapid Boards (Scrum/Kanban). Being able to configure the Flagged Field in the deprecated Classic Boards, posed a couple of advantages:
# Users could configure different types of Flags (as suited for their usecases) # From the board configuration, it is easy to determine in which field the flag for issues are stored in JIRA. # Although the flagged field is not Locked by default, if it was deleted, admins could easily create and configure a new one etc. Unfortunately, because this field is still unlocked by default, Rapid board users: # Would often delete it and then wonder where all their Rapid Board Flags are being stored. # Also, users who had been using their own/custom Flagged fields in Classic boards, before migrating to Rapid boards are prone to be even more confused about this because there is no longer an easy way to determine where this Issue flag data is stored like there was in the Classic Board Configuration Screen and Project Template configuration for classic boards. |
New:
Configuration for the Flagged field doesn't seem to be provided for Rapid Boards (Scrum/Kanban). Being able to configure the Flagged Field in the deprecated Classic Boards, posed a couple of advantages:
# Users could configure different types of Flags (as suited for their usecases) # From the board configuration, it is easy to determine in which field the flag for issues are stored in JIRA. # Although the flagged field is not Locked by default, if it was deleted, admins could easily create and configure a new one etc. Unfortunately, because this field is still unlocked by default, Rapid board users: # Would often delete it and then wonder where all their Rapid Board Flags are being stored. # Also, users who had been using their own/custom Flagged fields in Classic boards, before migrating to Rapid boards are prone to be even more confused about this because there is no longer an easy way to determine where this Issue flag data is stored like there was in the Classic Board Configuration Screen and Project Template configuration for classic boards. This 'Flagging issues' feature should be configurable to some extent atleast in Rapid Boards as well |