The way to 'plan' FR and bugs is by adding "storycardname:" in front of the bug/FR. This will automatically create task under the correct storycard.
Can we make sure that if the task is closed that the corresponding Bug/FR in the code related project is closed also?
A downside of this approach is that commits to fix a bug are tracked on a task (which is not public) and not on the bug/FR itself. This means the community can't see which commits fix a certain bug. Or do I see this wrong?
If I read https://gig.gitbooks.io/agile/content/repos.html
The way to 'plan' FR and bugs is by adding "storycardname:" in front of the bug/FR. This will automatically create task under the correct storycard.
Can we make sure that if the task is closed that the corresponding Bug/FR in the code related project is closed also?
A downside of this approach is that commits to fix a bug are tracked on a task (which is not public) and not on the bug/FR itself. This means the community can't see which commits fix a certain bug. Or do I see this wrong?