Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-20405

Allow to manage Epic name and summary independently in Portfolio

XMLWordPrintable

    • 1
    • 2
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Currently, Portfolio does not offer separate fields to represent an Agile Epic's name and summary, both fields are represented by the Epic title in Portfolio.

      Current behaviour:
      When applying updates to linked Projects and and enabling summary syncing, the title configured in Portfolio is set to summary and name of the linked Agile Epic. The same goes for automatic two-way synchronization of summaries between JIRA and Portfolio. Changing either Epic name or summary in JIRA will propagate the new value to Portfolio. Changing the title in Portfolio will set Epic name and summary in JIRA.

      Desired behaviour:
      Portofolio provides a separate field for the Epic name (e.g., in the details page of a backlog item) and maps the title to the Epic summary. This way, the two fields could be synced independently and a change to the Epic title in Portfolio would then not unexpectedly overwrite the Epic name in JIRA.

              Unassigned Unassigned
              akavelar Albert Kavelar
              Votes:
              22 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: