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

Feature Request: Make Summary Field more flexible

XMLWordPrintable

    • 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.

      This is a feature request for the ability to re-name the summary field "Summary" field. The key attributes are:

      • To be able to do this without a restart of the server
      • To be able to do this for each Field Configuration Scheme with a different name (each project can call it something different)

      I am aware that you can do this (http://confluence.atlassian.com/display/JIRA/Customizing+text) however, this work-around has the following limitations/issues:

      • Requires an outage
      • Must apply to all projects

      Business benefit:
      We have had several customers who user Jira for internal workflows to re-name the summary field. Each customer would refer to the summary field, as something different (eg Project Name, Summary, High-level overview....etc...). For those that might not be using Jira just for software development, want to be able to re-name that field to other things (specific to their project)

      Related Issues:

            [JRASERVER-15684] Feature Request: Make Summary Field more flexible

            Sherif Mansour added a comment -

            Anton,
            As per my comment I thought it was related to 11965 - however I was being specific as to what requirements I am after. 11965 seems very general. Ill post my comments in there then.
            Sherif

            Sherif Mansour added a comment - Anton, As per my comment I thought it was related to 11965 - however I was being specific as to what requirements I am after. 11965 seems very general. Ill post my comments in there then. Sherif

            AntonA added a comment -

            Hi,

            This issue appears to be a duplicate of JRA-11965 and therefore I would like to resolve it.

            It really helps us to keep the number of issues as small as possible and track requests for the same functinality in one place. Would you be able to let me know the difference between this issue and JRA-11965?

            If the are the same, please vote for JRA-11965 and add yourself as a watcher to it. Also, do not hesitate to add any suggestion as comments to JRA-11965.

            For more information on the way new feature and imrpovement requests are scheduled, please see:
            http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements

            Cheers,
            Anton

            AntonA added a comment - Hi, This issue appears to be a duplicate of JRA-11965 and therefore I would like to resolve it. It really helps us to keep the number of issues as small as possible and track requests for the same functinality in one place. Would you be able to let me know the difference between this issue and JRA-11965 ? If the are the same, please vote for JRA-11965 and add yourself as a watcher to it. Also, do not hesitate to add any suggestion as comments to JRA-11965 . For more information on the way new feature and imrpovement requests are scheduled, please see: http://confluence.atlassian.com/display/DEV/Implementation+of+New+Features+and+Improvements Cheers, Anton

              Unassigned Unassigned
              ded74cd6e43d Sherif Mansour
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: