Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-330

JIRA Portfolio overwrites Epic Name when synchronizing with JIRA Agile

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Answered
    • Icon: Low Low
    • None
    • None
    • None
    • None

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

      When issues are imported into JIRA Portfolio that include Epics, the title of the Epic is written from the summary of the Epic. When a synchronization is done from JIRA Portfolio back to the JIRA Agile, the imported portfolio epic title overwrites the epic name.

      Expected Behavior
      When the synchronization happens JIRA Portfolio should not be overwriting the Epic name with the portfolio epic title.

          Form Name

            [JPOSERVER-330] JIRA Portfolio overwrites Epic Name when synchronizing with JIRA Agile

            Albert Kavelar added a comment - - edited

            Hello mlavender,

            you are right, currently, Portfolio sets both, Epic name and Epic summary to the epic title configured in Portfolio. Some customers may want to keep the Epic name in sync while others prefer to use the Epic summary, or even both. As of today, Portfolio only provides one field for managing the name of an Epic, i.e., JIRA Epic name and summary are mapped to the same field in Portfolio.

            This also goes for syncing from JIRA to Portfolio - if you turn on summary synchronization for Epics (Plan > Configure > Synchronization) and change the name of a linked Epic in JIRA, the title in Portfolio will be set to the new name. If you change the summary of this Epic in JIRA, the title of the epic in Portfolio will be set to the new summary.

            I created a suggestion for allowing to manage Epic name and Epic summary independently which then also allows to update them independently and closed this issue.

            Best regards,
            Albert

            Albert Kavelar added a comment - - edited Hello mlavender , you are right, currently, Portfolio sets both, Epic name and Epic summary to the epic title configured in Portfolio. Some customers may want to keep the Epic name in sync while others prefer to use the Epic summary, or even both. As of today, Portfolio only provides one field for managing the name of an Epic, i.e., JIRA Epic name and summary are mapped to the same field in Portfolio. This also goes for syncing from JIRA to Portfolio - if you turn on summary synchronization for Epics (Plan > Configure > Synchronization) and change the name of a linked Epic in JIRA, the title in Portfolio will be set to the new name. If you change the summary of this Epic in JIRA, the title of the epic in Portfolio will be set to the new summary. I created a suggestion for allowing to manage Epic name and Epic summary independently which then also allows to update them independently and closed this issue. Best regards, Albert

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

                Created:
                Updated:
                Resolved:
                Archived: