Looking for a way to set up the company "Portal" to allow entry of issues into a Sofware project OR to allow an easy transition from a service-desk issue into a software project.
Best practices for getting the issue from company user over to a developer without a middle-man re-typing the issue into the dev project.
This is a bit of a bug-bear in JIRA Service Desk.
The problem is that you absolutely do *not* want to move an issue from a Service Desk into a Software project. If you do that, it looks to the customer like you have deleted their JSD request, which is, at best, confusing, and at worst, looks rude and ignorant!
There is no simple fix for this without add-ons, but the later versions of JSD do have options for "create issue in other project from this request" for the Agents to hit when they need it - this clones most of the issue into the target project and links them together. It's not fully automated (as in updates in dev don't flow into the JSD and vice versa), but it's moving that way.
As Nic stated moving JSD ticket to JSW is a bad idea. That said, this question comes up very often and I hope that Atlassian comes up with a slick implementation some day. For now I have copied and pasted in my response to this question from last week below.
>>> snip <<<
....You may want to read my response to the following topic for more on this - https://community.atlassian.com/t5/JIRA-Service-Desk-questions/How-to-create-a-JIRA-issue-from-a-Ser...
The Jira Service Desk marketing team is working on a guide to help new Atlassian customers switch from email to JSD and we'd love to hear from you! Please share: - What made you realize that i...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs