-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
16
-
2
-
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
Currently it is not possible to move an issue from one project in JIRA to another project using the rest api. Please add the ability to move an issue between projects to the rest api.
- duplicates
-
JRASERVER-71343 Add REST endpoint to "move" issues
- Gathering Interest
- relates to
-
JRACLOUD-61359 Please add the ability to move an issue between projects to the rest api.
- Gathering Interest
- Testing discovered
-
JRASERVER-71292 Jira allows illegal edit (issue type) through /rest/api/2/issue/<ISSUE-KEY>
-
- Closed
-
We are using a tool called TaskTop which connects our incident ticket system(s) (BMC Remedy. HP Quality Center) with our Jira environment. It picks up Remedy or QC 'tickets' and uses the Jira API to create a new Jira story or bug on the team's project. Then as the status changes in JIRA, the status also changes in Remedy.
The issue we are having is sometimes tickets get assigned to the wrong group. So when they are reassigned in Remedy, TaskTop can't move the card to the other Jira project, it has to create a new one leaving an orphan card on a completely unrelated team's Jira board. Without the REST command being enabled in JIRA, there's no way to resolve this issue.