taiga-back
taiga-back copied to clipboard
taigaio
Sync issues and promoted user stories
Maybe we do something wrong but we have a problem with issues and user stories sync.
We use issues to create all bugs and features. When we're planning our sprint we promote issues we want to work on to user stories. So we can vote them and add them to the current sprint. Here begins all our problems.
When a story is in the sprint, developers work on it, they create tasks, they finish them so they close the story. But the original issue is still in the same state and it's very difficult to keep synced issues and stories because of 2 things :
- They don't have linked status
- Nothing is automatic
We have to always keep an eye on what's in progress, done or not to manually sync everything.
What's wrong with our way to use taiga ? Or are you planning to do this in a better way ?
Hello @FlorianBezagu,
When we developed this part we were talking a lot about the situation you are talking about. Issues and user stories follow different workflows and Taiga reflects it having different status for each one. We where checking with some teams and each one used them in a different way, to respect the custom workflows of the teams we decided to leave them "linked" but not making cascade actions.
In Taiga when we "promote" we just close the original issue and just forget about the issue. A better approach could be having a "Promoted to user story" status for issues if you want to differentiate easily them in the issues listing.
+1 At the moment is quite difficult to track what issues are going to be resolve in the next sprint.
+1. Maybe a flexible approach would be to configure links between specific statuses as part of the custom status configuration taiga also has. So I could go to admin and set that Closed (for US) links to Closed (to issue). In that case, the issue will be closed when the US is closed, but other changes will not impact (as there is no specified link between statuses).
Maybe we can add an option "Follow promoted user story" for letting developer choose to sync promoted story with relatedissue or not?
