Hey there,
As part of a process to add temporary code into our product, I want to automate the creation of tickets to remove that temporary code such that it's added to a sprint in the future, but not the next sprint. We have our sprints set up as such usually:
- Name X (n)
- Name Y (n+1)
- Name Z (n+2)
I have a single rule set up such that:
- if a ticket with a specific label (abc) is moved to Done, it's cloned
- the cloned ticket is added to an epic (TEST-EPIC)
- the trigger label (abc) is removed
At this point, I'm able to specify a sprint of 'Active', which works but does not help our use case. I'm able to specify 'Next Sprint' which is too soon to assign the work.
I thought I could 'Copy from Epic'. I've manually assigned the requested sprint (Name Z (n+2)) to the epic (TEST-EPIC), but the cloned ticket does not seem to actually copy the epic's sprint value.
Would appreciate some insight into picking future sprints. I've played with creating a second rule so that when the issue is cloned, it's given a sprint, but no luck.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.