-
-
Notifications
You must be signed in to change notification settings - Fork 72
[18.0][IMP] spreadsheet_oca: Add Kanban views #84
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
Conversation
|
Hi.
|
|
Hi @legalsylvain
Most of time, we (Mind And Go / Datacup) are using sheets for a specific project, customer etc. We use sheets for computation but also for sharing simple quality process between us. Basically some checklist with colors. |
|
Hi @flotho. Thanks for your reply !
@etobella : a point of view here ? thanks ! |
|
you are solving the issue by using partner, but wouldn't be cleaner to use res_model and res_id and access/generate them from the thread similar to mgmtsystem.nonconformity? |
|
Hum, this leads us to a great path. |
I let @etobella and other main developpers answer on that topic. I didn't contributed on that great repo, and so don't have a clear PoV. |
|
Thanks @flotho it's great to see and i'm 100% behind a kanban view.
|
|
Hi @flotho. I put the PR in draft state, as it looks WIP, with red CI. Feel free to mark it as "Ready for review", once all is green and commit have been refactored. |
52c210d to
831214d
Compare
|
@flotho looks really good, I like the new proposal. Couple of things:
|
you're right. |
I'll wait for other comments @legalsylvain @etobella ?
|
|
ping @legalsylvain @etobella @chrisandrewmann , ready for review |
|
@flotho thanks, changes look good to me. |
done ! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, approved. Will wait for others
|
Hi @etobella @CarlosRoca13 @chrisandrewmann |
etobella
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am in favor of the concept of kanban and tags, but I think it will be better to make the res_model, res_id strategy.
Noted, thanks for the feedback |
|
@flotho if you remove the |
50294c8 to
2013125
Compare
|
Thanks @pedrobaeza , it's done , |
pedrobaeza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please reduce commits into 2 (tags and kanban)
| spreadsheet_oca.access_spreadsheet_spreadsheet_import,access_spreadsheet_spreadsheet_import,spreadsheet_oca.model_spreadsheet_spreadsheet_import,base.group_user,1,1,1,1 | ||
| access_spreadsheet_import_mode,access_spreadsheet_oca_revision,model_spreadsheet_spreadsheet_import_mode,base.group_user,1,0,0,0 | ||
| access_spreadsheet_select_row_number,access_spreadsheet_select_row_number,model_spreadsheet_select_row_number,base.group_user,1,1,1,1 | ||
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,group_user,1,1,1,1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only spreadsheet managers should change tags I think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a matter of taste, IMO.
./src/OCA/manufacture/mrp_bom_tag/security/ir.model.access.csv:access_mrp_bom_tag_manager,Bill Of Material Tag Manager,model_mrp_bom_tag,mrp.group_mrp_user,1,1,1,1
./src/OCA/server-auth/vault/security/ir.model.access.csv:access_vault_tag,access_vault_tag,model_vault_tag,base.group_user,1,1,1,1
./src/odoo/addons/website_forum/security/ir.model.access.csv:access_forum_tag_user,forum.tag.user,model_forum_tag,base.group_user,1,1,1,1
./src/odoo/addons/repair/security/ir.model.access.csv:access_repair_tag_user,Repair Tags user,model_repair_tags,stock.group_stock_user,1,1,1,1
etc.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The examples you are putting, except the first one, it's because there's no manager role. Usually, all the "master data" are only accessible by managers of the area.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The examples you are putting, except the first one, it's because there's no manager role.
I don't get it.
Regarding model_repair_tags for exemple. It is possible to manage tag with stock.group_stock_user group, not only stock.group_stock_manager. (group_stock_manager implies group_stock_user)
Or did I missed something ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please don't go off-topic. The topic here is that it's legit to not allow to modify tags to "simple" spreadsheet users, just the managers. That's it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible for you to speak correctly and on valid points?
That's not the first time, you're acting like an authoritarian leader. It's annoying to talk with you.
Thank you for questionning yourself on this point.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's you the one going to off-topics, as I'm talking about spreadsheet tags, not repair tags. And I'm being totally correct. Please tell me in which moment I have not been correct. It's also annoying to talk to you, deviating conversations that are not targeted to you, but to @flotho, who is the author of the PR.
|
Thanks for the renaming, @flotho Can you please squash commits as suggested, and what do you think about the tag permissions? |
* Add Kanban views * Also add active option [IMP] spreadsheet_oca: * Simplify partner usage * Add tags * Improve kanban view [IMP] spreadsheet_oca: Improve form view [IMP] spreadhseet_oca: add tag menu [IMP] spreadhseet_oca: add default image IMP: Add tag on view [REF] spreadsheet_oca: no more partner [REF] spreadsheet_oca: no more partner [REF] spreadsheet_oca: no more partner [REF]rename file [ACL]Ad specific rule for manager
89102ae to
c7ea389
Compare
|
done @pedrobaeza |
|
@flotho I was talking about 2 commits, as you are doing here 2 things: tags and kanban view. The commit message also lacks the first line explanations. And the tag question is still open. |
|
oh damned I squashed too much ;-) |
|
Thank you for the change in the tags. About the commits, if it's not very difficult to you, it would be great to have both features split, but I don't want to press more. Just tell me and let's finish this. |
| <h1> | ||
| <field name="name" placeholder="Name" /> | ||
| </h1> | ||
| <field name="badge_image" widget="image" class="oe_avatar" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To enable "Archived" ribbon and ability to archive from form, add above:
<field name="active" invisible="1"/>
<widget name="web_ribbon" title="Archived" bg_color="text-bg-danger" invisible="active"/>
| </group> | ||
| </sheet> | ||
| </form> | ||
| </field> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noticed you added inherited "mail.thread", "mail.activity.mixin" to spreadsheet_spreadsheet.py but didn't enable chatter in the view. Think this would be a welcome simple change. Just add this line after the ending sheet tag:
<chatter/>
legalsylvain
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A minor remark. Otherwise, LGTM.
Thanks for this improvment.
| spreadsheet_oca.access_spreadsheet_spreadsheet_import,access_spreadsheet_spreadsheet_import,spreadsheet_oca.model_spreadsheet_spreadsheet_import,base.group_user,1,1,1,1 | ||
| access_spreadsheet_import_mode,access_spreadsheet_oca_revision,model_spreadsheet_spreadsheet_import_mode,base.group_user,1,0,0,0 | ||
| access_spreadsheet_select_row_number,access_spreadsheet_select_row_number,model_spreadsheet_select_row_number,base.group_user,1,1,1,1 | ||
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,spreadsheet_oca.group_user,1,0,1,0 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,spreadsheet_oca.group_user,1,0,1,0 | |
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,spreadsheet_oca.group_user,1,1,1,0 |
At least. Otherwise, if a user create a tag, ans if he made a mistake in the name, he can not change it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, I still think that users should only use them (read them), not to modify them. If they are going to be able to create them, but not to remove them, that's worst.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is your opinion here @flotho, and what do you need ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for sharing your PoV.
I'm personally used to install the module that prevent creation on the fly for a user because in the end it produce inconsistent data. Typically the use case @legalsylvain described : if a user create with a bad name
That's why I'm in favor of @pedrobaeza to prevent user to modify the tag. Keeping data consistent should be the responsibility of managers.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
¿Then should it be this?:
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,spreadsheet_oca.group_user,1,0,1,0 | |
| access_spreadsheet_spreadsheet_tag,access_spreadsheet_spreadsheet_tag,model_spreadsheet_spreadsheet_tag,spreadsheet_oca.group_user,1,0,0,0 |
chrisandrewmann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing, thanks for that. Looks good.
|
This PR has the |
pedrobaeza
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's merge this although there's an extra commit for the last change.
/ocabot merge minor
|
This PR looks fantastic, let's merge it! |
|
Congratulations, your PR was merged at 308acc8. Thanks a lot for contributing to OCA. ❤️ |



Also add active option