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.
I figured it out:
- I added a branch rule / related issues
- set for linked (cloned) issues
- new action to edit issue fields
- set Sprint to Copy from Epic
Now what happens, the ticket is created into the backlog, but then moved into the correct sprint.
Calling all Confluence Cloud Admins! We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events