The procedural code for moving an issue can be found in the Jira source code - if you have a licence, you can download it and have a look (no sharing code with people though) But, I would take a close look at what you are proposing - try manually moving an issue from one project to another, when the two projects have totally different sets of issue types, fields and workflows. You'll find Jira asking you a LOT of questions, and you're going to have to code to answer all of them automatically.
Thanks. ok, will check the code. Actually, if you can suggest something for the below scenario: I have a workflow for one project in which i have added a custom status as "Move". I want whenever there is a transition from a status to this "Move" status in the ticket, the particular issue/ticket should open up a "Move Issue"screen; a "move issue" screen which is there in JIRA or if i can create my own "move" screen which can move that issue to another project. Please help.
There is no way to trigger a screen from a workflow like that. You can create your own "move" operation with a plugin, but you'll have to do the same checks and prompts that the current "move" process goes through, so I'm not sure it's really worth re-inventing the wheel on that one. I suspect your best bet might be a simple human approach 1. Change your process so that you don't need to move the issues 2. Save a filter for "issues in move status" and task a human to regularly check it and move the issues returned by it
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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