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

As a JIRA User, I'd like to set the Request Type while Creating an Issue

XMLWordPrintable

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

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

      Problem Definition

      Currently, in order to have JIRA Service Desk's Request Type set for issues created through JIRA itself, the user must manually edit the issue after it is created, which causes both confusion and frustration:

      Suggested Solution

      The Request Type field should be made visible when creating an issue as well.

          Form Name

            [JSDSERVER-1754] As a JIRA User, I'd like to set the Request Type while Creating an Issue

            Divyanshi made changes -
            Remote Link Original: This issue links to "JSDS-564 (JIRA Server (Bulldog))" [ 285672 ] New: This issue links to "JSMDC-564 (JIRA Server (Bulldog))" [ 285672 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011879 ] New: JAC Suggestion Workflow 3 [ 3649471 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665352 ] New: JAC Suggestion Workflow [ 3011879 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2325951 ] New: Confluence Workflow - Public Facing v4 [ 2665352 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053933 ] New: JSD Suggestion Workflow - TEMP [ 2325951 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2049199 ] New: JSD Suggestion Workflow [ 2053933 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279810 ] New: JSD Suggestion Workflow - TEMP [ 2049199 ]
            Matthew McMahon (Inactive) made changes -
            Remote Link New: This issue links to "JSDS-564 (JIRA Server (Bulldog))" [ 285672 ]
            jonah (Inactive) made changes -
            Description Original: h3. Problem Definition
            Currently, in order to have JIRA Service Desk's *Request Type* set for issues created through JIRA itself, the user must manually edit the issue *after* it is created, which causes both confusion and frustration:
            - JSD-830
            - JSD-1445

            h3. Suggested Solution
            The *Request Type* field should be made visible when creating an issue as well.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-1754].
              {panel}

            h3. Problem Definition
            Currently, in order to have JIRA Service Desk's *Request Type* set for issues created through JIRA itself, the user must manually edit the issue *after* it is created, which causes both confusion and frustration:
            - JSD-830
            - JSD-1445

            h3. Suggested Solution
            The *Request Type* field should be made visible when creating an issue as well.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-1754 [ JSDCLOUD-1754 ]

              Unassigned Unassigned
              mfernandes@atlassian.com Matheus Fernandes
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: