-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Epic 1704: Display report planning conflicts in Summary, Calendar, Map and Table tabs #3082
Labels
Comments
17 tasks
ysf-simsoft
added a commit
that referenced
this issue
Jun 23, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jun 23, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jun 23, 2020
10 tasks
ysf-simsoft
added a commit
that referenced
this issue
Jul 9, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jul 9, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jul 9, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jul 24, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jul 24, 2020
ysf-simsoft
added a commit
that referenced
this issue
Jul 24, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Planning conflict detection has been implemented in #1839 (#3017) and conflicts are only shown in Report Form and Report Show. Conflict detection should be extended to cover ReportSummary, ReportCalendar, ReportMap and ReportTable views.
Current implementation of
PlanningConflictForReport
component works in a way that it makes a graphql query for every report. It can also be utilized to show conflicts in ReportSummary, ReportCalendar, ReportMap and ReportTable. However, when used in ReportCalendar with monthView will result it hundreds of queryies which is not feasible. Please see this comment.Part of #1704 epic
The text was updated successfully, but these errors were encountered: