-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
None
-
8
-
As per the discussion items below, we would like to be able to change the parent of a sub-task via the REST API which currently cannot be done. It seems that more than one customer would like this feature.
- https://community.atlassian.com/t5/Jira-questions/Can-I-change-the-parent-field-of-sub-task-in-Jira-via-REST-API/qaq-p/750954
- https://community.atlassian.com/t5/Answers-Developer-Questions/Can-I-change-sub-task-parent-using-REST/qaq-p/466646
[JRASERVER-68763] REST API: Allow changing the parent of a sub-task via the REST API
@onkar kumar, this fix for the Cloud version you mention, can you provide a link?
If fix for this is now available in the cloud then what is the reason to restrain this on server version ?
This is a significant gap in functionality when automating Jira operations. Please consider fixing it.
Our team has also got a use case for this. It would be great if this can be brought up to the server version.
Hi, we also have a use case for this, external CI systems tag deliveries with specific Jira key so it's possible to track their progress but to maintain traceability these issues need to be moved instead of closing/cloning to maintain their unique key.
This issue has already been solved for Cloud https://jira.atlassian.com/browse/JRACLOUD-75890 despite having half as much interest, since a solution already exist there maybe it wouldn't take much work to port it to server?
Hi Team, colleagues! Is there any possible workaround to change the parent? In fact we do not need to move issue, but just change one field which is parent_id.
And as it was said by 482ea045f338
That said, the only reason I was looking to do it via the API is because it's super cumbersome in the UI...
It looks like we just need to go on https://jira.atlassian.com/secure/MoveSubTaskParent!default.jspa?id=29485 to see the final step and push this final button automatically to achive theresult
Because after this the thing is done!
Would be usefull in order to synchronize repositories.
I'm always surprised when a functionality is available through the IHM but not through the API.
Is it for security reasons ?
I'm quite surprised that the Jira API doesn't allow this. That's the whole point of an API – to be able to write scripts to help you get your work done faster. Frustrating that Jira wouldn't support this in 2020.
Is this feature available in server version?