New module "project_analytic_line_view" #107
Merged
Conversation
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
| :alt: License: AGPL-3 | ||
|
|
||
| Analytic lines view from project | ||
| ================================================= |
mdietrichc2c
force-pushed
the
8.0-project-analytic-line-view
branch
from
2c29d5a
to
0ca8a66
Compare
|
👍 |
2 similar comments
|
👍 |
|
👍 |
dreispt
added a commit
that referenced
this pull request
Aug 13, 2015
New module "project_analytic_line_view"
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is to create a new small module,
project_analytic_line_view, which is in fact a part of the moduleproject_billing_utilsin https://github.com/OCA/project-reporting .The main reason for this split is that the module
project_classification(currently ported in PR #97 ) depends on this part ofproject_billing_utils; however, adding a dependency in this functional module to a reporting module would be bad practice.When this PR is validated, I will add the dependency to the new module in PR #97 , and remove the code + add the dependency in project-reporting.