My main answer would be what @Jack Brickey said already.
But I'd want to question the rationale for doing it. Scrum is not a suitable framework for handling support requests. If a support request leads you down a route that requires work from a development team rather than a support team to deal with it, then the best option is to create new items for the developers to track through their processes, not try to jam the request into their to do list and confuse the requestor with your development processes.
There's a good reason JSM has a function for "created linked issue in a dev project"
Hi @Prasad Bhardwaj , I agree with @Nic Brough _Adaptavist_ here, connecting OPS (Jira Service Management) and DEV (Jira Software) happens through issue links and automation, not by moving a JSM issue into a JSW project.
If you have a customer request for a change in JSM and analysis/development/testing/release is necessary, then this request is 'developed' in JSW.
So a Change in JSM leads to a Epic/Story/Task in JSW. The relation is an issue link.
If you are using a Company managed software project then you could edit the underlined filter for the scrum board to include specific issues from your JSM project. You will need to be able to uniquely identify the JSM issues. Maybe by label or status or something. With that said have you considered creating a linked issue in your JSW project instead?
👋 Hi there Jira Community! A few months ago we shared with you plans around renaming epics in your company-managed projects. As part of these changes, we highlighted upcoming changes to epics on...
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