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; } } }

How to switch a task from one sprint to another according to the editing time

unknown

I need to switch a task automatically from one sprint to another depending on the last edit date. I'm new to jira and I'm not sure how to automate this process.

ex.: I need task 1 to move from A to B within X time, but when in B it can go to C in Y time.
A, B and C are sprints and X and Y different time periods to consider in automating the change.

Accepted answers

Trudy P Claspill

Hello @[deleted]

Welcome to the Atlassian community!

Are these all active sprints running in parallel?

Typically an issue is assigned to a sprint when the commitment is made to complete the work of that issue within that sprint. It remains in the sprint until the sprint ends. If the work is not completed, then the issue is either moved to another sprint or moved to the backlog.

Can you provide more information about your scenario? What problem are you trying to solve by moving issues from one sprint to another based on when the issue was edited?

All comments

Trudy P Claspill

Hello @[deleted]

Welcome to the Atlassian community!

Are these all active sprints running in parallel?

Can you provide more information about your scenario? What problem are you trying to solve by moving issues from one sprint to another based on when the issue was edited?

unknown

Thank you for replying!

They are not sprints running in parallel.

The idea of having this change is to organize the period before a sprint, which is currently not happening in an organized or periodic way. In general, the sprint that is taking place will not suffer from such an alteration, since it follows the logic of one.

Trudy P Claspill

I think I am still not really grasping your use case. Are you trying to automate sprint planning?

Can you provide a detailed example with fake issue IDs and sprint names, and Last Updated dates to walk us through how you would expect this to work?

unknown

Of course, I can detail better. I apologize for not being clear earlier.

You are correct in understanding to organize sprint planning, but it is also to remove old and de-prioritized items.

Currently the area that will take care of organizing the jira is under construction, therefore, the current period of the company has a planning organization and jira backlog somewhat messy and dirty with items that should no longer be developed for various reasons.

The idea is to be able to move items from one sprint (which is not and will not be active) to another to be able to organize the sprint planning according to some criteria.

An example would be moving from sprint ID 10 title '10 - design' to sprint ID 13 title '13 - dev' if 30 days pass after the last task update. (names, id and time all fictitious)

Welcome!

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

Quick Links

Find more posts tagged with

jira-service-desk-cloud

sprint

automation

jira-service-management-cloud

jira-service-management