Hi,
we're using a customized worfklow for one of our processes. It's is a workflow for subtasks of another issuetype. Within this workflow one can trigger a transition, that clone the current issue (Scriptrunner follow-up function), changes the issuetype (of this specific issue - this subtask) to another on. This newly created issue isn't a subtask anymore (due to internal demands to implemt it that way). This leads to the problem, that the newly created issues are linked to the subtask but not to the parent. Is there any way to solve this?
Kind regards
Condition for the Scriptrunner action:
additional actions:
Can't i just "save" the parent id and link the parent to the newly created issue as doAfterCreate action "relates to"?
FYI: Parent = Audit, Subtask = Finding, Clone from Finding = Action (to fix the Finding) which isn't visible on the Audit (Parent).
Hi @Maik Pomp
To solve your issue, you could consider using our app Deep Clone for Jira, which allows for cloning issues with customizable settings, including preserving parent-child relationships. With it, you can ensure that the newly created issues retain the links to the original parent issue. This could be set up to work during your workflow transitions with a Deep Clone post function, maintaining clarity between subtasks and parents, even after cloning.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.