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

Copy-to-Development workflow

XMLWordPrintable

    • 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

      We've setup a dedicated service desk project, so we can have the issue types, workflows and so forth setup to suit/match the service desk workflow.

      If an issue gets pushed across to the developer team, we then have a choice: Do we move the issue (and lose the tracking, SLAs etc in the service desk) or clone it and then move it (which "wastes" an ID and leaves gaps in the issue numbering).

      Suggested Solution

      It would be nice to have a simple "Send to Developers" or "Copy to Project" workflow which creates a duplicate of the issue in the (specified) developer project, and automatically links the service desk project issue to the developer project issue.

      That would mean you can have a single helpdesk project for triaging issues, and the development team the flexibility to play around with the issue without impacting the SD team and metrics.

        1. 3-11-2016 1-46-59 PM.jpg
          19 kB
          William Penman

          Form Name

            [JSDSERVER-792] Copy-to-Development workflow

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3011809 ] New: JAC Suggestion Workflow 3 [ 3649412 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2665238 ] New: JAC Suggestion Workflow [ 3011809 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2324428 ] New: Confluence Workflow - Public Facing v4 [ 2665238 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2053479 ] New: JSD Suggestion Workflow - TEMP [ 2324428 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048595 ] New: JSD Suggestion Workflow [ 2053479 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1279712 ] New: JSD Suggestion Workflow - TEMP [ 2048595 ]
            jonah (Inactive) made changes -
            Description Original: h3. Problem Definition

            We've setup a dedicated service desk project, so we can have the issue types, workflows and so forth setup to suit/match the service desk workflow.

            If an issue gets pushed across to the developer team, we then have a choice: Do we move the issue (and lose the tracking, SLAs etc in the service desk) or clone it and then move it (which "wastes" an ID and leaves gaps in the issue numbering).


            h3. Suggested Solution

            It would be nice to have a simple "Send to Developers" or "Copy to Project" workflow which creates a duplicate of the issue in the (specified) developer project, and automatically links the service desk project issue to the developer project issue.

            That would mean you can have a single helpdesk project for triaging issues, and the development team the flexibility to play around with the issue without impacting the SD team and metrics.             		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-792].
              {panel}

            h3. Problem Definition

            We've setup a dedicated service desk project, so we can have the issue types, workflows and so forth setup to suit/match the service desk workflow.

            If an issue gets pushed across to the developer team, we then have a choice: Do we move the issue (and lose the tracking, SLAs etc in the service desk) or clone it and then move it (which "wastes" an ID and leaves gaps in the issue numbering).


            h3. Suggested Solution

            It would be nice to have a simple "Send to Developers" or "Copy to Project" workflow which creates a duplicate of the issue in the (specified) developer project, and automatically links the service desk project issue to the developer project issue.

            That would mean you can have a single helpdesk project for triaging issues, and the development team the flexibility to play around with the issue without impacting the SD team and metrics.
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-792 [ JSDCLOUD-792 ]
            Confluence Escalation Bot (Inactive) made changes -
            Labels Original: rv sdt New: affects-cloud rv sdt
            Marty (Inactive) made changes -
            Component/s New: API and Integrations [ 35993 ]
            Component/s Original: JIRA Integration [ 35890 ]

              Unassigned Unassigned
              975b20805ae4 Andy Fleming
              Votes:
              38 Vote for this issue
              Watchers:
              29 Start watching this issue

                Created:
                Updated:
                Resolved: