Skip to content
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

[blueprint] [8.0] project need to have project.category specific for categorize business #238

Closed
victormmtorres opened this issue Mar 16, 2017 · 6 comments
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.

Comments

@victormmtorres
Copy link

On project_categ

Already have task_categ_id and mean to set a root Category for Tasks linked.

So on Task could choose only Tags which parent is the root Category on Project.

Our concern is to have one unique category on Project that mean to categorize for which kind of Operation is.

For this on
project.categoy we think to add boolean is_business_category
add constrain to prevent have duplicated name if is_business_category

Add on project.project
project_category_id many2one project.category
On Form View: should be required
ACL to be discuss
Group by
Search

@victormmtorres
Copy link
Author

@elicoidal Please have a check

@elicoidal
Copy link

@victormartinelicocorp if we have a specific field o2m, we don't need this do we? for the tags, we do not care much about duplication. Remember:

  • Tags field are used for search and multi-classification
  • Category field is used for statistics and mono-classification

@victormmtorres
Copy link
Author

@elicoidal ok then just might be need to modify the model project.category to add checkbox to manage special cases as we'll need on BR modules.

@elicoidal
Copy link

Yes

@dreispt
Copy link
Sponsor Member

dreispt commented Mar 16, 2017

Instead of a checkbox, I would instead use a "Root for Main Category" field, similar to what was done to with the Tags ("project_categ") module.
That will cover your use case, and is more flexible.

@github-actions
Copy link

There hasn't been any activity on this issue in the past 6 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this issue to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Dec 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale PR/Issue without recent activity, it'll be soon closed automatically.
Projects
None yet
Development

No branches or pull requests

3 participants