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

Imported epics use 'epic summary' rather than 'epic name'.

XMLWordPrintable

    • 3
    • 2
    • 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 Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.

      When I import a list of epics, they show up in the list in Portfolio using the 'epic summary' field instead of the 'epic name'. It should use the 'epic name' as it fits more easily within the Initiatives list.

            [JSWSERVER-25092] Imported epics use 'epic summary' rather than 'epic name'.

            Aakrity Tibrewal added a comment -

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Andrew Simpson added a comment -

            It's not just imported Epics. I've created Epics today using the latest version Cloud Premium. It comes with Roadmap as an intergrated feature and Epics appear there using Summary description as well. Annoying.

            Andrew Simpson added a comment - It's not just imported Epics. I've created Epics today using the latest version Cloud Premium. It comes with Roadmap as an intergrated feature and Epics appear there using Summary description as well. Annoying.

            Deleted Account (Inactive) added a comment -

            +1

            The point of an Epic Name is to have a short title by which we can identify it - much easier when looking at the roadmap, for example. Currently, I'm having to rewrite the summary to put the Epic name at the beginning so that I don't have to drag the column width across the screen to see what it's about.

            Deleted Account (Inactive) added a comment - +1 The point of an Epic Name is to have a short title by which we can identify it - much easier when looking at the roadmap, for example. Currently, I'm having to rewrite the summary to put the Epic name at the beginning so that I don't have to drag the column width across the screen to see what it's about.

            Subbu Yeleswarapu added a comment -

            +1 

            It would be consistent to use "Epic Name" field in both Jira boards and plans.

            Subbu Yeleswarapu added a comment - +1  It would be consistent to use "Epic Name" field in both Jira boards and plans.

            Eric Bobo added a comment -

            Yes, this would be preferred. Not sure why it was created with summary instead of name

            Eric Bobo added a comment - Yes, this would be preferred. Not sure why it was created with summary instead of name

            Benjamin Riley added a comment -

            I would just like to say this is still a requested feature, or improvement request.

            Benjamin Riley added a comment - I would just like to say this is still a requested feature, or improvement request.

            Johannes Waldheim added a comment -

            I am as well interested as it makes Portfolio useless for me.

            I have to report using the plan and this is not possible...

            Communication shall be overall and this is not communicable to send a link to Jira to my CEO.

             

            Johannes Waldheim added a comment - I am as well interested as it makes Portfolio useless for me. I have to report using the plan and this is not possible... Communication shall be overall and this is not communicable to send a link to Jira to my CEO.  

            Kyle Tully added a comment -

            Totally agree with the above.

            Kyle Tully added a comment - Totally agree with the above.

            Joel Feldman added a comment -

            Can we have an update on where this sits on the Atlassian priorities?   There are obviously quite a few large customers that find this very impactful.  There is pretty much no doubt from any of the voters that this is a bug, not a feature request. 

            Joel Feldman added a comment - Can we have an update on where this sits on the Atlassian priorities?   There are obviously quite a few large customers that find this very impactful.  There is pretty much no doubt from any of the voters that this is a bug, not a feature request. 

            Motti Friedman added a comment -

            Agree and strengthen all comments above. This is a very annoying bug of the tool. Epic Name is the only interesting tag for an epic.

            Motti Friedman added a comment - Agree and strengthen all comments above. This is a very annoying bug of the tool. Epic Name is the only interesting tag for an epic.

              Unassigned Unassigned
              akavelar Albert Kavelar
              Votes:
              112 Vote for this issue
              Watchers:
              49 Start watching this issue

                Created:
                Updated: