Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-41733

Populate Epic Name with Summary when Bulk Edit Issues

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Bulk Operations
    • None
    • 7
    • 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.

    Description

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

      At the moment, if users Bulk Edit an issue to be an Epic, the Epic Name will be blank but in Plan Mode, it will appear as unlabelled-<issue key>. If you edit the issue after bulk editing, you will be required to enter a new Epic Name for it.

      For example, if the issue is TEST-1 and TEST-2, bulk editing these issues to an Epic will cause the Plan Mode to show the Epic Name as unlabelled-TEST-1 and unlabbelled-TEST-2.

      It would be better if the Epic Name could be automatically populated with the Summary, instead of just unlabelled- as it will be more relevant. This way, users might not have to rename all the Epics individually.

      Attachments

        Issue Links

          relates to

          Suggestion - JRACLOUD-41733 Populate Epic Name with Summary when Bulk Edit Issues

          • Gathering Interest

          Activity

            People

              Unassigned Unassigned
              ywoo Yit Wei
              Votes:
              47 Vote for this issue
              Watchers:
              21 Start watching this issue

              Dates

                Created:
                Updated: