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

Migration to version 9.0 #120

Closed
6 of 25 tasks
pedrobaeza opened this issue Oct 14, 2015 · 9 comments
Closed
6 of 25 tasks

Migration to version 9.0 #120

pedrobaeza opened this issue Oct 14, 2015 · 9 comments
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Milestone

Comments

@pedrobaeza
Copy link
Member

pedrobaeza commented Oct 14, 2015

Todo

https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-9.0

Modules to migrate

Modules to rename or deprecate

@dreispt
Copy link
Member

dreispt commented Oct 14, 2015

Just edited the list: service_deskmodules needs refactoring/ renaming / feature splitting. I'll detail that in due time. If you use them we can discuss.

@thinkwelltwd
Copy link
Contributor

thinkwelltwd commented May 14, 2016

Where is the place to discuss the service_desk module? We need this for our business and I'm planning to start working on it next week and would very much like to make sure that the work I do on it is in line with OCA intentions regarding 'refactoring/ renaming / feature splitting'.

@dreispt
Copy link
Member

dreispt commented May 14, 2016

@thinkwelltwd Please open an Issue for that discussion.

I also feel that service_desk needs refactoring.
As a coincidence, during this last week I've been looking at other ticketing apps and studying a future design for the Service-related features .
I have a design I like, and my next step was to write a specification and roadmap.
Of course it would be great to hear other ideas about it.

@thinkwelltwd
Copy link
Contributor

thinkwelltwd commented May 14, 2016

Indeed! Very interesting.

We're an IT company, currently using osTicket for much of our ticketing requirements and Odoo for the rest with the goal of migrating completely to Odoo - the better to integrate with other apps I've done for our company's use of Odoo. The more that our needs could be in line with advancing Odoo modules and OCA the better. So that's a short summary of our goals.

I've made rather general study of ticketing systems, but at a high level. I'd be interested in getting a peek at your design and collaborate with you rather than duplicating work. If you're willing to mentor me and put up with my questions. I suppose a first step would be to migrate one these existing modules and prove that I can do Odoo work to the standards of OCA.

@dreispt
Copy link
Member

dreispt commented May 15, 2016

@thinkwelltwd Opened #174 proposing a roadmap

@ghost
Copy link

ghost commented Jul 17, 2016

Hello,
cause that iam working heavily in main modul project I could try to migrate some. I think I have currently used a few in odoo9.
Actually project_issue_baseuser, project_issue_task, project_sla, service_desk, service_desk_issue.

As I understand serice _desk makes a project usable as analytic account, but in odoo9 it seems, that every project is also an analytic account cause project inherits analytic. Default type is always contract and a service desk would be a contract too?!
Please correct me, when I understood wrong starting discussen if service_desk and dependend extensions need to be ported or if we really need a new type of servicedesk for analytic account?
Do we need an exclusive menuitem for service_desk as I can see, that analytic account is hidden and hard to find in account and there isnt any shortcut from project to analytic account..
What do you think about summarizing some modules to a new one for v9.0? I would be interested in pimp it up to handle real contracts and SLA and bring it together with management to offer services more to the paradigmen of ITIL.

regards,
Karsten

@dreispt
Copy link
Member

dreispt commented Jul 18, 2016

Hi, I authored the service_desk module and this it has some design issues and should be replaced by other modules. Please see #174 , it might answer some of your questions. Please comment there, since it is the best place for this discussion.

@LoisRForgeFlow
Copy link

project_closing in #278

@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 Oct 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted stale PR/Issue without recent activity, it'll be soon closed automatically. work in progress
Projects
None yet
Development

No branches or pull requests

4 participants