I'm running a filter sync test and it's not working as expected...
Epic -User Story 1 User Story 2
US1 is below the Epic, so not top level.
Why would a User Story 1 be removed if it's anywhere but the "top / root level" of the Structure? I expected User Story 2 to get removed, since it's on the top level, where new issues are placed, but not so with User Story 1. That's what I thought the "Remove only from where added issues are placed" means...
Is this a bug or a feature?
Here are my settings:
I'm on Version 2.1.9
The "Remove only from where added issues are placed" option works together with the "Place added issues as sub-issue of".
It makes the synchronizer ignore the issues, which were either moved from under the issue, where the synchronizer placed them, or were created or added outside of it. If the synchronizer just adds issues to the top level, this feature does not really work. To avoid the confusion perhaps the option should be disabled unless the "Place added issues as sub-issue of" is selected. We'll discuss with the team and I'll update our wiki to reflect this.
If this behaviour stops you from implementing some workflow, let's discuss in more details and we'll try to come up with some solution. Please feel free to send us an email, or create a Support Request in our JIRA.
Eugene (ALM Works)
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs