nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Delete completed sprint from an cloned issue using Jira automation (Web request)

Eliyahu Klein --CNTR

Hi,

When I clone a specific issue, it duplicates along with the active sprint and the list of closed sprints. I don't want this because it affects my reports and disrupts the history.

Therefore, I'm trying to create an automation that deletes the list of closed sprints after cloning. Even though I set the Sprint field to "Null" and only enter the value of the active sprint, it still keeps the issue in the previous sprints (as shown in the image).

Is there a function in automation that deletes the sprint history?
If I need to use a Web request, how do I set it up correctly? All the results I get are Bad request 400.

Thanks

Screenshot 2024-12-12 134109.png Screenshot 2024-12-12 133419.png Screenshot 2024-12-12 133230.png

Accepted answers

Bill Sheboy

Hi @Eliyahu Klein --CNTR

I do not believe that is possible with an automation rule after the issue has been cloned.

In my experience, there are only three ways not to keep (or to clear) the Sprint field and its history for a cloned issue:

When the issue is cloned using an automation rule, include the Sprint field as empty in the action so the current value and history are not copied
When the issue is cloned manually using the UX's Clone issue feature, do not select the option to copy the Sprint field values
After the issue is cloned, use the Bulk Edit feature to clear the field and history information

Kind regards,
Bill

Luka Hummel - codefortynine

Hi @Eliyahu Klein --CNTR

To manage the cloning of issues while avoiding the duplication of completed sprints in your workflow, you could consider our app Deep Clone for Jira. This app offers advanced cloning capabilities that can help you handle this scenario effectively.

With Deep Clone, you can fully customize what fields and values to clone, including excluding or clearing the Sprint field.

2024-12-13 13-11.png

All comments

Bill Sheboy

Hi @Eliyahu Klein --CNTR

I do not believe that is possible with an automation rule after the issue has been cloned.

In my experience, there are only three ways not to keep (or to clear) the Sprint field and its history for a cloned issue:

When the issue is cloned using an automation rule, include the Sprint field as empty in the action so the current value and history are not copied
When the issue is cloned manually using the UX's Clone issue feature, do not select the option to copy the Sprint field values
After the issue is cloned, use the Bulk Edit feature to clear the field and history information

Kind regards,
Bill

Luka Hummel - codefortynine

Hi @Eliyahu Klein --CNTR

With Deep Clone, you can fully customize what fields and values to clone, including excluding or clearing the Sprint field.

2024-12-13 13-11.png

Eliyahu Klein --CNTR

Hi Luka,

Actually, I was looking for a way to do this without using plugins.
Anyway, thanks for the suggestion. If I see that there is no other option, maybe this could still be a possible option.

Thank you!

Eliyahu Klein --CNTR

Hi Bill,

Thanks for your response
I understand that the usual methods don't allow for this action.
Do you know if using the "Web request" function (by automation) might be a viable option?
If so, do you have any ideas on how to build the basic structure of the request?

Eliyahu Klein --CNTR

@Luka Hummel - codefortynine Upon further thought, if I don't select the "Sprint" field, it won't copy the current value either, right?
Is there a way to copy only the "Active Sprint" without the history? From the image you sent, it seems the answer is no.

Bill Sheboy

I believe the basic, REST API endpoint for issue edit may only update the Sprint field and does not clear the history.

You could experiment with the newer bulk-edit endpoint to see if will clear the history, although I hypothesize it will not: the primary idea of issue history is it is immutable, and if the endpoints could tamper with that, history would be unreliable.

You could also investigate if a Forge app (built by you) could do this.

Luka Hummel - codefortynine

Hi @Eliyahu Klein --CNTR

Deep Clone can only clone active and future sprints. Completed sprints are ignored.

You can read more here.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud