You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…haviour is true (as it was working as today)
When flag is set to false:
- Board list is populated with project uids
- Project-board relation created 1-1 with project uid.
- The board_issues stream is removed from list.
- Task-board relationship is written on faros_issues stream using project uid.
How are sprint report boards being handled, are they all gonna be phantoms. Can we add some tests to validate these mappings
Didn't finish that implementation yet. Trying to think the best approach. The impl. on feeds leaves all boards as phantoms, but then they get linked to the project dummy board on the reports. Maybe we could link them directly to the project board on the graph...
And we would write only one board sprint per project, hoping they don't differ that much.
How are sprint report boards being handled, are they all gonna be phantoms. Can we add some tests to validate these mappings
Didn't finish that implementation yet. Trying to think the best approach. The impl. on feeds leaves all boards as phantoms, but then they get linked to the project dummy board on the reports. Maybe we could link them directly to the project board on the graph... And we would write only one board sprint per project, hoping they don't differ that much.
The issue here is that we are using board slices for sprint and sprint reports, to query sprints by board id. But here the board slices will contain the project key... So I'm not sure if we should query sprints for all project's boards all together for this case and if that would be performant also.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
We are adding use_board_ownership flag, like the one we had on the feed, to be able to keep using it with 1 board per project.
Default behavior is use_board_ownership:true, as it was working as today.
When flag is set to false:
TODO
Type of change
Related issues
Migration notes
Extra info