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

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

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a bug
    • Icon: Medium Medium
    • None
    • 6.1.1
    • None

      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.

              Unassigned Unassigned
              f8d09390e557 SYSGO GmbH
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: