• Type: Suggestion
• Resolution: Fixed
• Component/s: Forge and Connect
• Labels:

  • affects-cloud
  • rv
  • sdt

1. 

   3-11-2016 1-46-59 PM.jpg

   19 kB

   11/Mar/2016 7:49 PM

[JSDCLOUD-792] Copy-to-Development workflow

Katherine Yabut made changes - 19/Sep/2019 6:09 AM

Workflow	Original: JAC Suggestion Workflow [ 3443941 ]	New: JAC Suggestion Workflow 3 [ 3697078 ]
Status	Original: RESOLVED [ 5 ]	New: Closed [ 6 ]

Monique Khairuliana (Inactive) made changes - 26/Aug/2019 3:01 AM

Workflow	Original: JSD Suggestion Workflow - TEMP [ 2320100 ]	New: JAC Suggestion Workflow [ 3443941 ]
Status	Original: Closed [ 6 ]	New: Resolved [ 5 ]

Katherine Yabut made changes - 22/Jun/2017 5:53 AM

Workflow

Original: JSD Suggestion Workflow [ 2050377 ]

New: JSD Suggestion Workflow - TEMP [ 2320100 ]

Amogh Sarda (Inactive) made changes - 22/Jun/2017 5:25 AM

Remote Link

New: This issue links to "Page (Extranet)" [ 300461 ]

Katherine Yabut made changes - 31/May/2017 12:28 AM

Workflow

Original: JSD Suggestion Workflow - TEMP [ 2046207 ]

New: JSD Suggestion Workflow [ 2050377 ]

Katherine Yabut made changes - 31/May/2017 12:24 AM

Workflow

Original: JSD Suggestion Workflow [ 1872018 ]

New: JSD Suggestion Workflow - TEMP [ 2046207 ]

jonah (Inactive) made changes - 02/Apr/2017 11:42 AM

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 Cloud*. Using *JIRA Service Desk Server*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDSERVER-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 - 02/Apr/2017 11:42 AM

Link

New: This issue is related to JSDSERVER-792 [ JSDSERVER-792 ]

vkharisma made changes - 02/Apr/2017 12:24 AM

Project Import

New: Sun Apr 02 00:24:18 UTC 2017 [ 1491092658763 ]

Confluence Escalation Bot (Inactive) made changes - 16/Mar/2017 4:32 AM

Labels

Original: rv sdt

New: affects-cloud rv sdt

Load more older events