Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-1042

Service Desk Text Field Renderer should not inherit Default Field Configuration

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Low Engagement
    • None
    • Global Configuration
    • None
    • 1
    • We collect Jira Service Desk 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 Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.

      Currently, when a new Service Desk project is created, a new Field Configuration will be generated for it. It seems that, however, the renderers of text fields such as Comment, Description, Log Work will follow the renderers of the corresponding fields in JIRA's Default Field Configuration.

      This causes confusion if the renderers of those fields are set to Default Text Renderer in the Default Field Configuration, which causes the wiki markup to stop working in the Service Desk project until administrators check and edit the renderers manually for the fields.

      It's suggested that a dedicated Field Configuration of a new Service Desk project should not inherit the current settings in the Default Field Configuration. It should be a copy of the original Default Field Configuration.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              vdung Andy Nguyen (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Backbone Issue Sync