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

Option for Epic Name to Sync with Issue Summary

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Answered
    • None
    • None
    • None
    • 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.

      User would like to have an configuration option for Epic Name to synchronize with the issue summary. Thus, it would help kept the Epic Name in sync with summary and avoid wrong naming confusion from users.

            [JSWSERVER-11128] Option for Epic Name to Sync with Issue Summary

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3067401 ] New: JAC Suggestion Workflow 3 [ 3661565 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2621346 ] New: JAC Suggestion Workflow [ 3067401 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2319799 ] New: Confluence Workflow - Public Facing v4 [ 2621346 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2039579 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2319799 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2028086 ] New: JIRA PM Feature Request Workflow v2 [ 2039579 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 735844 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2028086 ]

            Christopher Busch added a comment -

            The Epic name should naturally default to the Summary at the very least. Using "unlabelled" was never a good idea and makes the product look slap-dash.  Software developers should look at themselves as crafts persons who build quality products.

            Users do not want to click on things.  Users do not want to type. So please find ways to remove clicks and typing as much as possible.  This should be ingrained into the UX design mindset and upheld by everyone on the team. This could be a side effect of having too short of a sprint cycle as that can encourage corner cutting and lower quality work.

            Christopher Busch added a comment - The Epic name should naturally default to the Summary at the very least. Using "unlabelled" was never a good idea and makes the product look slap-dash.  Software developers should look at themselves as crafts persons who build quality products. Users do not want to click on things.  Users do not want to type. So please find ways to remove clicks and typing as much as possible.  This should be ingrained into the UX design mindset and upheld by everyone on the team. This could be a side effect of having too short of a sprint cycle as that can encourage corner cutting and lower quality work.
            Martin (Inactive) made changes -
            Workflow Original: GreenHopper Kanban Workflow v2 [ 725030 ] New: JIRA PM Feature Request Workflow v2 [ 735844 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Minor [ 4 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Michael Tokar made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Michael Tokar added a comment -

            Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time.

            Regards,
            JIRA Agile Team

            Michael Tokar added a comment - Many thanks for reporting this issue, however this is not something we plan to add to JIRA Agile at this time. Regards, JIRA Agile Team

              Unassigned Unassigned
              yen@atlassian.com TeckEn (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: