Step 3 is where I'm looking for help. Move doesn't work, b/c it moves it out of the Service Desk. Linking is helpful, but then you have to go create the Bug and enter everything manually. I looked at seeing if a workflow transaction (through post functions) could create an issue, but didn't see that option.
There are several plugin that can provide a "Clone" or "Create and Link" and help with step 3.
In step 4 the Support Analyst will be able to see it.
For 5 , if you want some type of automatism you can use:
Has these three Post functions for workflows:
Perform Transitions In Linked Issues
Perform Transitions In Linked Issues Whith Issue Type
Perform Sub Task Transition Y
That may help you on that (you will need to set as parameter the transitionId that you want to be preformed in "original service desk Jira")
Are there any options when we use the Cloud Version of JIRA Service Desk? We can fully integrate between Salesforce and JIRA but we cannot integrate between JIRA Service Desk and JIRA.
I have the same question as Colin, and would also like to ask if there is a way to this in service desk without buying plugins?
I was under the impression that the whole point of using atlassian jira and service desk together was to have that integration. Do I really need to pay for service desk, pay for jira and then pay again for getting them to work together?
I'm in the same situation than Colin et Andreas.
Now, manually in service desk, I create a new linked issue in a jira project. Then this new issue have his life in Jira. And when the issue is closed I return back in service desk to close the ticket.
It's painful, but I have not found anything better yet
We're small. We currently use ZenDesk for ongoing customer support.
We recently started using Jira for project management/Scrum.
Need a way to get the ongoing customer requests better integrated with our larger project work, and maintaning both systems is too much overhead, especially the necessity to create duplicate issues for everything client's subit, in order to see that work in sprints, and schedule it with the correct prioritization amongst a lot of other competing tasks.
Was hoping that by moving the Support side from ZD to JSD, we'd be able to leverage our existing JiraSW workflow with sprints and boards, and be able to keep clients in the loop right from the same issues the Devs are working on. But now I'm seeing we'd still need to create duplicate issues in JSW for the things clients are reporting via JSD. I appreciate Luis and Jack's advice on automation above and below, but was really hoping to be able to avoid all this. Might not be the magic bullet we were hoping for. Will keep looking at these and other products.
Out of the box today in Cloud you can create a linked issue from the JSD issue. The degree of success in duplicating field statuses is dependent on a partially on the current SW and the alignment of the configuration between the JSD and JSW product in question. All of the default fields will be duplicated but if there are differences in workflows then some manual effort is required. You can add automation that will resolve the JSD ticket when the JSW ticket is resolved.
What you cannot do (AFAIK) is to have the comments in the JSW ticket automatically added to the JSD ticket directing them to either internal or public.
I use this method in my world and the only thing that is missing for me is to have the JSW comment entered when resolving JSD ticket placed automatically into the JSD ticket as Internal. This would allow the JSD agent to provide more meaningful response on the resolution more easily. However, they can do so simply by reviewing the comment in the JSW ticket and then rewording for customer consumption. This last piece is key since you generally do not want to communicate publically all that is said internally. Today, using the aforementioned automation, i place a canned response into the JSW ticket based upon the Resolution reason (Done, Won't Do, Can't Duplicate, etc.) chosen in JSW.
Hi Jack - I am new to JIRA and have read all the documentation. We have server/licenses for software, service deska and core.
what I would like to do is have service desk utilize and internal customer facing to create tickets replacing our internal ticket system.
I would like to link the SD tickets to SW so we PM's can manage the tickets via boards/SCRUM/Agile for reporting and tracking.
we do not plan to send communication back to SD from SW.
all communication to customers will come from SD via the SD agents.
Is there an automated way to LINK tickets that come into SD to SW so we do not have to LINK each ticket individaully?
"Out of the cloud" means that nothing must be added or configured in order for that functionnality to work, right?
I cannot seem to find how you do that. A customer raised a ticket in project A on JSD.
I want to make an issue on project B on JSW that clones basic fields of the ticket open on project A: how? I can't seem to find this button/link/function...
Thank you for help :)
I have a similar query as we are just looking at getting both Service Desk and JIRA - If a Service Desk ticket is changed to Dev (JIRA) for general development- can it be closed, and then JIRA deals with it (I guess like a clone) then it wont show as an outstanding Service Desk item or effect SLAs
the one thing to consider here is that it is generally industry practice to not close a customer request until development is complete. It is easy enough, and what i have done, to create a DEV status that the JSD issue is transitioned into when the JSW task is opened. You can then edit the SLA to pause when in the status.
More and more people are building their careers with Atlassian, and we want you to be at the front of this wave! Important Dates Start the free Certification Prep Course by 30 June 2019 (earlier ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events