-
Bug
-
Resolution: Not a bug
-
Medium
-
None
-
6.1.1
-
None
-
6.01
-
It is unacceptable that different boards use different information to get the connection between stories and Epics:
- the classic boards use a custom field
- the rapid boards use an issue link
The request is to update the classic boards in GH6 to use the same link as the rapid boards.
GHS-6828 (https://jira.atlassian.com/browse/GHS-6828) can be regarded only as a first step to bring things together.
The update procedure would then be the following:
- Update GH
- Find that the Epics in the classic boards are not connected to their stories
- Call the maintenance procedure from
GHS-6828
... and have consistent data.
Having to call the Maintenance procedure from GHS-6828 regularly and manually is not an option to users which need to use both board versions:
- A change in the rapid boards would be overwritten
- A change in the classic boards would not take immediate effect on the rapid boards
- Using only one type of board is not acceptable.
- details
-
JSWSERVER-6754 As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements
- Closed