[JSWSERVER-6754] As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements

Type: Suggestion
Resolution: Tracked Elsewhere
Fix Version/s: None
Component/s: AgileBoard
Labels:
- affects-server

Feedback Policy:

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.

NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

From docens of requests and comments concerning Rapid Board deficiencies on this web site - and from various discussions with other JIRA stakeholders and other customers, I know that this is a very serious issue.

The Rapid Board has moved out of labs way to early for many customers.

This request is meant to gather the MUST HAVE requirements that would make us customers wanting to move to the Rapid Board.

Dear Atlassian, please see this request as a chance to make Rapid Board a really big success. This request is an offer to give our best support to achieve that common goal.

Thank you.

- - Sort By Name
  - Sort By Date
  - Ascending
  - Descending
  - Thumbnails
  - List

Great core values!.jpg
106 kB
04/Dec/2012 12:56 PM
screenshot-1.jpg
114 kB
07/Mar/2013 3:03 PM

is detailed by

JSWSERVER-7349 As a user, I expect and request that all boards use the same information for the epic-story-task hierarchy.

Closed

JSWSERVER-3474 As a Rapid Board user I would like to configure the detail view for an issue

Closed

JSWSERVER-3922 As a user, I would like to configure the cards displayed in the rapid board

Closed

JSWSERVER-5035 As a JIRA/GH administrator, I would like to be able to specify who is allowed to create and start a sprint independently from the "Administer Projects" JIRA permission

Closed

JSWSERVER-5117 Greenhopper non-working days are ignored in Rapid Views

Closed

JSWSERVER-5345 Add GreenHopper gadgets to the dashboard that tie to the Rapid Board

Closed

JSWSERVER-5678 As a user, I would like to set up a Version Hierarchy on the new board

Closed

JSWSERVER-6020 As a scrum planner I would like the ability to reorder sprints

Closed

JSWSERVER-6626 As a JIRA system admin I want to decide, if the GreenHopper UI supports Epics or not

Closed

JSWSERVER-6677 As a JIRA system admin I want to decide, if the GreenHopper UI supports "Simplified Workflows" or not

Closed

JSWSERVER-6714 As a Rapid Board user i would like a compact UI displaying as many cards as the classic board can

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-6789 Please remove message "The Classic boards are no longer being actively improved ..."

Closed

JSWSERVER-7446 View on board function not available for Classic Board Greenhopper

Closed

JSWSERVER-7467 As a rapid board user, able to rank sub-task in Plan mode

Closed

JSWSERVER-8003 Epic in Two Dimensional Filter Statistics

Closed

JSWSERVER-9587 Add the ability to specify multiple board administrators so other users can change the configuration (delegated admin)

Closed

JSWSERVER-5200 As a user, I would like to be able to change the size of cards on the Rapid Board

Gathering Interest

JSWSERVER-6790 As a Scrum Master I would like to use a predefined template for my Agile Board

Gathering Interest

JSWSERVER-13138 Sum estimates from sub-tasks in user stories

Gathering Interest

JSWSERVER-9167 Provide ability to automatically sum estimates from sub-tasks in user stories

Future Consideration

JSWSERVER-3681 Ability to have cell (column and swimlane) min/max constraints

Not Being Considered

JSWSERVER-9554 Customisable panels in Agile Backlog

Not Being Considered

relates to

JSWCLOUD-6754 As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements

Closed

JSWSERVER-6828 As a Classic user I would like my epic-issue relationships migrated for use on the new boards

Closed

mentioned in: Page Loading...; Page Loading...; Wiki Page Loading...

(18 is detailed by, 2 relates to, 3 mentioned in)

Form Name

Katherine Yabut made changes - 19/Sep/2019 5:59 AM

Workflow	Original: JAC Suggestion Workflow [ 3065346 ]	New: JAC Suggestion Workflow 3 [ 3663571 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

Owen made changes - 21/Nov/2018 7:01 AM

Workflow

Original: Confluence Workflow - Public Facing v4 [ 2623171 ]

New: JAC Suggestion Workflow [ 3065346 ]

Rainer Mueck made changes - 30/May/2018 10:36 AM

Link

New: This issue is detailed by JSWSERVER-9554 [ JSWSERVER-9554 ]

Rachel Lin (Inactive) made changes - 08/Feb/2018 7:06 AM

Workflow	Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2323303 ]	New: Confluence Workflow - Public Facing v4 [ 2623171 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

Katherine Yabut made changes - 22/Jun/2017 5:54 AM

Workflow

Original: JIRA PM Feature Request Workflow v2 [ 2041451 ]

New: JIRA PM Feature Request Workflow v2 - TEMP [ 2323303 ]

Katherine Yabut made changes - 31/May/2017 12:05 AM

Workflow

Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2032770 ]

New: JIRA PM Feature Request Workflow v2 [ 2041451 ]

Katherine Yabut made changes - 30/May/2017 11:54 PM

Workflow

Original: JIRA PM Feature Request Workflow v2 [ 736949 ]

New: JIRA PM Feature Request Workflow v2 - TEMP [ 2032770 ]

jonah (Inactive) made changes - 02/Apr/2017 11:58 AM

Description

Original: From docens of requests and comments concerning Rapid Board deficiencies on this web site - and from various discussions with other JIRA stakeholders and other customers, I know that this is a very serious issue.

The Rapid Board has moved out of labs way to early for many customers.

This request is meant to gather the MUST HAVE requirements that would make us customers wanting to move to the Rapid Board.

Dear Atlassian, please see this request as a chance to make Rapid Board a really big success. This request is an offer to give our best support to achieve that common goal.

Thank you.

New: {panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Software Server*. Using *JIRA Software Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSWCLOUD-6754].
{panel}

From docens of requests and comments concerning Rapid Board deficiencies on this web site - and from various discussions with other JIRA stakeholders and other customers, I know that this is a very serious issue.

The Rapid Board has moved out of labs way to early for many customers.

This request is meant to gather the MUST HAVE requirements that would make us customers wanting to move to the Rapid Board.

Dear Atlassian, please see this request as a chance to make Rapid Board a really big success. This request is an offer to give our best support to achieve that common goal.

Thank you.

jonah (Inactive) made changes - 02/Apr/2017 11:58 AM

Link

New: This issue relates to ~~JSWCLOUD-6754~~ [ ~~JSWCLOUD-6754~~ ]

Confluence Escalation Bot (Inactive) made changes - 20/Feb/2017 4:48 AM

Labels

New: affects-server

Assignee:: Unassigned

Reporter:: rainer mueck

Votes:: 142 Vote for this issue

Watchers:: 102 Start watching this issue

Created:: 23/Nov/2012 2:08 PM

Updated:: 19/Sep/2019 5:59 AM

Resolved:: 01/Jul/2014 4:52 AM

Details

Description

Attachments

Attachments

Issue Links

Forms

Activity

People

Dates

Backbone Issue Sync