Movement of ticket from one sprint to another after the ticket has been closed (or is in production)

[Evalaji Jones]

Do not really want to create the same ticket all the time.

[Mark Segall · Accepted solution]

Hi @Evalaji Jones - Generally, you don't want issues to keep moving from sprint to sprint.  It skews reporting.  However, if this is a repetitive activity, you could use automation to generate a new one each sprint:

• TRIGGER: Sprint Started
• ACTION: Create Issue
  Set the pertinent fields you want set each time and add it to the current sprint.  Here are suggestions:
  
  • Summary:  Sprint Task - {{sprint.name}} 
  • Description
  • Assignee
  • Sprint: {{sprint}}

[Evalaji Jones]

Thanks!