-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
[15.0] [MIG] connector_jira_servicedesk: Migrate to version 15.0 #77
[15.0] [MIG] connector_jira_servicedesk: Migrate to version 15.0 #77
Commits on Jul 19, 2022
-
Add connector_jira_servicedesk
Map projects by external_id + set of jira orgs Project bindings now can be assigned to one or more jira organizations. The binding for the project accept an additional argument for organizations. A task will be linked with the project having the exact same set of organizations that it has, or fallback to a project without organization. A constraint ensures that you cannot have several projects with the same set of organizations or 2 projects without organization. The link wizard has a new step to select the organization. The REST API for Serviced Desk is a different one. The former code was based on pycontribs/jira#388 which is closed and unmaintained. We only need to read the organizations from the servicedesk REST API and the local code is minimal. We can now use the normal jira library.
Configuration menu - View commit details
-
Copy full SHA for 2edaeca - Browse repository at this point
Copy the full SHA 2edaecaView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3fe4b9e - Browse repository at this point
Copy the full SHA 3fe4b9eView commit details -
Fix project binding unique constraint
We should be able to have 2 bindings without external_id (not yet exported)
Configuration menu - View commit details
-
Copy full SHA for 3cc80d1 - Browse repository at this point
Copy the full SHA 3cc80d1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 923a2a3 - Browse repository at this point
Copy the full SHA 923a2a3View commit details -
Allow to have one project binding per project type
The unicity constraint (backend_id, odoo_id) on jira.backend.backend is relaxed: it now allows one binding of each type. The reason for this is: * supporting several projects of different types is a requirements (eg. 1 service desk and 1 software) * but if we implement new features like "if I create a task it is pushed to Jira", with different projects we would not know where to push them Using this constraint, we'll be able to focus new export features by project type.
Configuration menu - View commit details
-
Copy full SHA for b45f53c - Browse repository at this point
Copy the full SHA b45f53cView commit details -
Prevent duplicates with inactive projects
The constraint did not look for inactive projects, which makes the import fail later because it finds several projects for the same task.
Configuration menu - View commit details
-
Copy full SHA for e44b9ba - Browse repository at this point
Copy the full SHA e44b9baView commit details -
Handle 404 errors when importing records
When a record does not exist on Jira: * the job is done instead of failed * a result on the job tells about the missing record * the binding is deleted on Odoo * for worklogs, the analytic line is deleted as well
Configuration menu - View commit details
-
Copy full SHA for 7393fb5 - Browse repository at this point
Copy the full SHA 7393fb5View commit details -
Configuration menu - View commit details
-
Copy full SHA for f95515f - Browse repository at this point
Copy the full SHA f95515fView commit details -
Store jira's 'updated_at' field to compare with binding
We can compare the millisecond dates on both sides to see if any changes has been done on Jira and avoid useless writes. Previously, we were using the 'sync_date' field, which works too but will make more sync than necessary (because the sync happens after the last jira's updated_at value). Fortuitously, the updated_at is also very useful for debugging purposes.
Configuration menu - View commit details
-
Copy full SHA for 1ed4007 - Browse repository at this point
Copy the full SHA 1ed4007View commit details -
Fix fetch pagination of organizations
The pagination specs of the servicedesk API are not the same than the Jira API (respectively isLastPage vs lastPage). So the lib's _fetch_pages does not fetch all the pages. Optimize the requests: we get all the data at the initial call, so the records are passed directly to "import_record" which will not do another request.
Configuration menu - View commit details
-
Copy full SHA for c609411 - Browse repository at this point
Copy the full SHA c609411View commit details -
Configuration menu - View commit details
-
Copy full SHA for 3d950e1 - Browse repository at this point
Copy the full SHA 3d950e1View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6d98af9 - Browse repository at this point
Copy the full SHA 6d98af9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 01bdba0 - Browse repository at this point
Copy the full SHA 01bdba0View commit details -
Configuration menu - View commit details
-
Copy full SHA for cee6dfb - Browse repository at this point
Copy the full SHA cee6dfbView commit details -
[IMP]connector_jira_servicedesk: Add servicedesk_issue_url
Update connector_jira_servicedesk/models/account_analytic_line/common.py Co-authored-by: Stéphane Mangin <StephaneMangin@users.noreply.github.com> Update connector_jira_servicedesk/tests/test_import_organization.py Co-authored-by: Stéphane Mangin <StephaneMangin@users.noreply.github.com> Update connector_jira_servicedesk/tests/common.py Co-authored-by: Stéphane Mangin <StephaneMangin@users.noreply.github.com> Update connector_jira_servicedesk/i18n/connector_jira_servicedesk.pot Co-authored-by: Stéphane Mangin <StephaneMangin@users.noreply.github.com> Update connector_jira_servicedesk/models/account_analytic_line/importer.py Co-authored-by: Stéphane Mangin <StephaneMangin@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 9a22e02 - Browse repository at this point
Copy the full SHA 9a22e02View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7152947 - Browse repository at this point
Copy the full SHA 7152947View commit details -
Configuration menu - View commit details
-
Copy full SHA for 20b1f0e - Browse repository at this point
Copy the full SHA 20b1f0eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2bd3fd9 - Browse repository at this point
Copy the full SHA 2bd3fd9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e37a8e - Browse repository at this point
Copy the full SHA 4e37a8eView commit details