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

Allow an issue to co-exist in a ServiceDesk project and a non-ServiceDesk project

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Low Engagement
    • None
    • API and Integrations
    • 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.

      We would like to be able to use ServiceDesk as follows. At our company, we have a SD to field any and all internal IT requests. Some issues require developer support. We have various non-SD, product-related projects in the same JIRA.

      Right now, we must clone + move the SD issue into the non-SD project, and manually transfer comments and changes to the SD issue for any real-time updates. Then, when done, we can can move the ticket back to the SD desk, but now have two tickets with no native merge option.

      We are considering getting the merge plugin, but ideally, there should be a way to have a ticket exist in two projects at once.

            [JSDSERVER-2112] Allow an issue to co-exist in a ServiceDesk project and a non-ServiceDesk project

            Alex Cooksey made changes -
            Resolution Original: Won't Do [ 10000 ] New: Low Engagement [ 10300 ]
            Status Original: Closed [ 6 ] New: Closed [ 6 ]
            Charlie Marriott made changes -
            Resolution New: Won't Do [ 10000 ]
            Status Original: Gathering Interest [ 11772 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3012815 ] New: JAC Suggestion Workflow 3 [ 3647568 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2663850 ] New: JAC Suggestion Workflow [ 3012815 ]
            Gosia Kowalska made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 394756 ]
            Owen made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2322404 ] New: Confluence Workflow - Public Facing v4 [ 2663850 ]
            Status Original: Open [ 1 ] New: Gathering Interest [ 11772 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 2052719 ] New: JSD Suggestion Workflow - TEMP [ 2322404 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow - TEMP [ 2048855 ] New: JSD Suggestion Workflow [ 2052719 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Suggestion Workflow [ 1280420 ] New: JSD Suggestion Workflow - TEMP [ 2048855 ]
            jonah (Inactive) made changes -
            Description Original: We would like to be able to use ServiceDesk as follows. At our company, we have a SD to field any and all internal IT requests. Some issues require developer support. We have various non-SD, product-related projects in the same JIRA.

            Right now, we must clone + move the SD issue into the non-SD project, and manually transfer comments and changes to the SD issue for any real-time updates. Then, when done, we can can move the ticket back to the SD desk, but now have two tickets with no native merge option.

            We are considering getting the merge plugin, but ideally, there should be a way to have a ticket exist in two projects at once.             		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-2112].
              {panel}

            We would like to be able to use ServiceDesk as follows. At our company, we have a SD to field any and all internal IT requests. Some issues require developer support. We have various non-SD, product-related projects in the same JIRA.

            Right now, we must clone + move the SD issue into the non-SD project, and manually transfer comments and changes to the SD issue for any real-time updates. Then, when done, we can can move the ticket back to the SD desk, but now have two tickets with no native merge option.

            We are considering getting the merge plugin, but ideally, there should be a way to have a ticket exist in two projects at once.

              Unassigned Unassigned
              5b24b717d52b Robert Reed
              Votes:
              5 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: