-
Suggestion
-
Resolution: Won't Fix
-
None
-
None
Currently the rapid board implementation does not support all features the classic board does. Thus we decided not to use it at the moment.
Therefore we need a switch to either select the Classic or Rapid Board which can be set by the admin only.
- is related to
-
JSWSERVER-6475 As a project manager, I need a solution to release management, therefore I'd like to have a way to promote the Classic Boards back to the main Agile menu, so that I don't have to train people on where to go find them.
- Closed
-
JSWSERVER-6753 As a JIRA system admin I want to decide, if my users see GreenHopper Classic, RapidBoard or both in the JIRA UI
- Closed
[JSWSERVER-6160] Implement an Agile Board switch
Workflow | Original: JAC Suggestion Workflow [ 3067409 ] | New: JAC Suggestion Workflow 3 [ 3661569 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: Confluence Workflow - Public Facing v4 [ 2621388 ] | New: JAC Suggestion Workflow [ 3067409 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2319909 ] | New: Confluence Workflow - Public Facing v4 [ 2621388 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 2039627 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2319909 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028138 ] | New: JIRA PM Feature Request Workflow v2 [ 2039627 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 [ 737138 ] | New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028138 ] |
Workflow | Original: GreenHopper Kanban Workflow v2 [ 435699 ] | New: JIRA PM Feature Request Workflow v2 [ 737138 ] |
Issue Type | Original: Story [ 16 ] | New: Suggestion [ 10000 ] |
Priority | Original: Major [ 3 ] | |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Resolution | New: Won't Fix [ 2 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |