profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/santostelmo/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

mmequignon/delivery-carrier 0

Odoo Carriers And Deliveries Management

santostelmo/account-financial-tools 0

Odoo Accountant Financial Tools and Utils

santostelmo/addons-onestein 0

Odoo modules developed by Onestein

santostelmo/ak-odoo-incubator 0

Misc Odoo modules maturing before going to a specific repo

santostelmo/bank-statement-import 0

Bank Import Addons

santostelmo/delivery-carrier 0

Odoo Carriers And Deliveries Management

santostelmo/e-commerce 0

Odoo E-Commerce server automation addons

santostelmo/odoo 0

Odoo. Open Source Apps To Grow Your Business.

santostelmo/odoo-cloud-platform 0

C2C Odoo cloud platform addons

create barnchcamptocamp/connector-jira

branch : merge-branch-1305-13.0.0.12.3

created branch time in a day

create barnchcamptocamp/sale-workflow

branch : merge-branch-1305-13.0.0.12.3

created branch time in a day

create barnchcamptocamp/l10n-switzerland

branch : merge-branch-1305-13.0.0.12.3

created branch time in a day

create barnchcamptocamp/purchase-workflow

branch : merge-branch-1305-13.0.0.12.3

created branch time in a day

create barnchcamptocamp/odoo

branch : merge-branch-1305-13.0.0.12.3

created branch time in a day

create barnchcamptocamp/connector-jira

branch : merge-branch-1305-13.0.0.12.2

created branch time in a day

create barnchcamptocamp/sale-workflow

branch : merge-branch-1305-13.0.0.12.2

created branch time in a day

create barnchcamptocamp/l10n-switzerland

branch : merge-branch-1305-13.0.0.12.2

created branch time in a day

create barnchcamptocamp/purchase-workflow

branch : merge-branch-1305-13.0.0.12.2

created branch time in a day

create barnchcamptocamp/odoo

branch : merge-branch-1305-13.0.0.12.2

created branch time in a day

delete branch camptocamp/connector-jira

delete branch : 13.0-connector-jira-unbind-jira-project-task

delete time in 2 days

PR closed OCA/connector-jira

[13.0][IMP] connector jira unbind jira project task

When a project reached a final stage (For example "Done" or "Cancelled"), we don't want to record more timesheet on project tasks. At that moment, the existing binding with JIRA should be cut to prevent time to be added at that stage.

+55 -0

0 comment

5 changed files

santostelmo

pr closed time in 2 days

push eventcamptocamp/connector-jira

Telmo Santos

commit sha 128bfdb4edfcdaf91386129859926ce60dc63d8f

[13.0][IMP] Unbind jira project task in project stage

view details

push time in 2 days

push eventcamptocamp/connector-jira

Telmo Santos

commit sha 11a174689cf11469b84d0a911bf1a0d9f616864b

[13.0][IMP] Unbind jira project task in project stage

view details

Yannick Vaucher

commit sha cba9a5995887fd3c3fc665140013d1846f952edf

Patch for Webhooks Webhooks are unsafe on deletion. If enabled, webhooks allows to delete resources unauthentified. Using an url and a worklog or issue Jira id is enough to trigger an unlink on the Odoo resource. With this patch, when a resource is asked to be deleted throught the webhooks it will interogate Jira to ensure it has indeed be deleted. A deletion will be refused if the object still exists on Jira.

view details

Telmo Santos

commit sha 91f22c78e85ebc7360a41337355b1ca520ab3815

Travis: exclude new branch from build

view details

push time in 2 days

push eventcamptocamp/connector-jira

Telmo Santos

commit sha 11a174689cf11469b84d0a911bf1a0d9f616864b

[13.0][IMP] Unbind jira project task in project stage

view details

push time in 2 days

PR opened OCA/connector-jira

[13.0][IMP] connector jira unbind jira project task

When a project reached a final stage (For example "Done" or "Cancelled"), we don't want to record more timesheet on project tasks. At that moment, the existing binding with JIRA should be cut to prevent time to be added at that stage.

+51 -0

0 comment

5 changed files

pr created time in 2 days

push eventcamptocamp/connector-jira

Telmo Santos

commit sha 47bcd26d68e79c2e7ea78ea087be27f2152d7c99

[13.0][IMP] Unbind jira project task in project stage

view details

push time in 2 days

push eventcamptocamp/connector-jira

oca-git-bot

commit sha 8c0d8dcd04a64eacd4ab865723d6b4b8f52b6916

[IMP] pre-commit: pin node version [ci skip]

view details

Stéphane Bidoul

commit sha 559cccdb7502799e6357e2f95f0ffc7742bbf481

Use prettier/pre-commit for compatibility with pre-commit 2.8 [ci skip]

view details

Stéphane Bidoul

commit sha 1da3a5642158ecfbd0334cdf27b2b9585801f177

update dotfiles [ci skip]

view details

Stéphane Bidoul

commit sha 5e9e2c3822d25042bf80827662ba3caa2b32d54c

Upgrade pylint-odoo for 13.0 [ci skip] This is apprently necessary for the development status checks to work correctly.

view details

Guewen Baconnier

commit sha 0ffbf622b6c3ced7641ab7a87a34e3eb22cbc161

Add first brick of the connector_jira addon Add project binding Add export of projects Add Jira project tasks model Add external dependencies in manifest Add security accesses Add basic import of tasks Task import are triggered by Jira webhooks. A batch import must be added later to import the changes from missed hooks or for those not wanting to use the webhooks. Add a basic backend adapter Batch import of project tasks Remove markdown The fields are not in markdown, but in a wiki syntax (proper to JIRA yet be determined) Link users and import tasks assignees Import worklogs Use an adapter for the project export Import issue types Filter type of issues to synchronize And assign the worklog to the first parent we find that we synchronize. If the type of the worklog's issue is synchronized, the worklog is assigned on this issue. If the worklog's issue is a sub-task, and the parent task of the sub-task is of a synchronized type, it link it to it. If the task has an epic, and the epics are synchronized, it link it to it. In last resort, the worklog will be linked with the project but with no task. Configure the name of the Epic Link field from API Create webhooks in JIRA from Odoo Choose template on project creation Discard Epics from different projects JIRA allow to choose an epic for any project. Setting the Epic as the Odoo task would create inconsistencies between the project and the task. We discard such an Epic, likely the task will be empty. Delete worklogs deleted on JIRA (only with webhooks) Delete tasks deleted on JIRA (only with webhooks) Add JIRA issue type in tasks Add JIRA Issue Key Add core business project types Improve display of JIRA backend Use a dedicated button to activate the Epic Link. Link the Epic in a dedicated field Add JIRA Parent for subtasks Show JIRA key in name Create project from shared project Check JIRA project keys Remove the button to 'one-click-export' a project It can't be working because we have other fields to configure on the binding. Add help on issue type synchronizations Accept tasks without parent Do not use id builtin

view details

Damien Crier

commit sha a7db69cc619d60527e3940f12965a3bcd0792031

Update ir.model.access.csv add `jira_account_analytic_line` object

view details

Guewen Baconnier

commit sha 12903be53cfa3f649975c97a87dcf3733a5f89d7

Set uninstallable Replace openerp namespace by odoo namespace Change to new Binder's API Migrate connector_jira to new 10.0 API Make addons uninstallable Apply 2to3 for python3 Migrate to new Component API Add setup guide in readme Migrate to v11 and Py3 Allow to delete a backend if we have issue types

view details

Simone Orsi

commit sha aa2edcfc26a02314f15cfb7a2eff8e8c4669abb4

C2C-152 Add project.task.jira_issue_url Fix project listener name typo Add links to JIRA issue on a.a.l Fix connector tab naming

view details

Timon Tschanz

commit sha 43d36c2eb869d39550c78061aa7e3bdd3fb5e055

add epic and issuetype to analytic line

view details

Tonow-c2c

commit sha 0878b37713ee13587ee050ab52face1f1cb6a8da

Test jira_key only if connector_no_export is True (#13)

view details

Simone Orsi

commit sha 4a6a7280ea804ac5342fd09e4f637048212594cd

Better handling of users sync

view details

Guewen Baconnier

commit sha 54c364738796b880226e9388f84e043cd8b3a8bf

Replace text_field by options text_field as attribute could not by validated by RNG, options is always valid Add base to support both export and link with projects Now linking a project with JIRA must be done through a wizard instead of the binding view. It must be either export (create the project on jira) or link (link with an existing project on jira). We keep this choice in the binding so we never export data to JIRA when we chose the link only.

view details

Patrick Tombez

commit sha f5f9330e221918542516c70155a92ef3fb863717

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 https://github.com/pycontribs/jira/pull/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.

view details

Guewen Baconnier

commit sha 13de7810a7cdd2bbb907fd3350f85dbf2605a550

Read access tokens with sudo A normal user must be able to use the jira rest client under the hood. Update documentation Store original jira issues on analytic lines Instead of the issue they are linked to in Odoo. With the mechanism in place, if we don't import the task or bug issue types and we synchronize the epics, the worklogs will be attached to the epics of their tasks (of subtasks to tasks). The fields were showing the values of the Epic (or task for subtask), though it makes much more sense to keep the keys and URLs of the original issue and epic on the analytic lines. We still have the link to the task if we want to get the URL for the task they are currently linked to. Fix project binding unique constraint We should be able to have 2 bindings without external_id (not yet exported) Add wizard to link a task to JIRA Refactorize multistep wizards with a mixin Handle jira bindings in tasks merge wizard Import name of Epics instead of summary The Epic issues have a special (custom) field for their name. In fact they use both, the custom field AND the summary field. But I guess they are better identified by their epic name than their summary. Extract multi_step_wizard as an addon Set a timeout on requests to JIRA Fix typo in readme Fix backend selection on wizard to link a task The computed field was not called, due to the model being a TransientModel, replace it by default values. Add is_master on jira project bindings 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. Move jira_key from project to jira project binding As we can have more than one project binding, we cannot store a single jira key. In case we have more than one jira key for a project, we compute a compound key joined by commas. Add method to handle jira API / connection errors Add migration for 11.0.1.1.0 Fix error when several odoo users match When we are importing a worklog for a user not yet linked and we found several candidate users in odoo, they will both be linked with the same jira user and make the unicity constraint fail. Properly raise an error in this case. Fix project_type as string Add fallback project for worklogs A new optional field on the backend allows to choose a fallback project for the worklogs. When a worklog doesn't match any project linked with Jira, they will be created there, allowing to find the misconfigurations and fix them. Add action to reimport worklogs from Jira This is meant mainly to be used when a worklog has been imported in the fallback project and we need to re-affect them to the correct project after we linked it. Add related action to open jira with import issues The 'related' button on jobs which import issues or worklog will now open jira directly on the issue. Skip import of tasks/worklogs before batch dates Jira may send webhooks for old records, for instance worklogs from 6 month ago because their task has been changed. This change ensures that we never import any record which has a last update date before the last date of batch import. The job methods now return the result of Importer.run() so the result is shown on the jobs in the UI. Extract import of dependencies Allowing to override partially the dependencies to import Fix import of subtasks When importing the parent of a subtask, the record in the 'parent' field (the task data) is incomplete, it contains only a few fields. Providing only the id to the dependency Importer will force it to read the whole record from Jira. 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. 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 Change xmlid for model_account_analytic_line account is not necessarily installed, while analytic is installed by the project module in any case Partial revert of 2fa7d39 Commit title was: Skip import of tasks/worklogs before batch dates The process is the following: * Read T from backend, T is the is the last time we ran the import * Create a batch job to import tasks/worklogs from T to now() and update the backend with now() The batch job is run asynchronously, it generates one job per task or worklog to import between T and now(). When the jobs are executed, the last batch date has already been updated to now(), so the jobs would never import any record. Fix error when force_reimport called on several records Prevent changing task's project on binding When the task Mapper binds a task to a task already existing in Odoo, we must not change the project_id of the task. This is not possible as long as we have invoiced timesheet lines, even if the id is the same than the current one. Add base for tests and a test for oauth Add test for check of connection With a fix in the method: getting the client only wasn't triggering any error, calling 'myself' raises a 401 when we are not authenticated. Add documentation for tests Add travis configuration Add tests on issue types and tasks Add first test for analytic account lines Make pylint-odoo happy Add a script to initiate the Oauth dance

view details

Thierry Ducrest

commit sha 0086278f4cad2d1bab5381806dc90e74311051ff

Apply suggestions from code review Co-Authored-By: guewen <guewen.baconnier@camptocamp.com>

view details

Guewen Baconnier

commit sha c5ce1fa174f62881f5128499bfbea7369b93d754

Prevent error when linking users When another user is already linked with the same jira user and matches. Without this check, the transaction fails with a unique constraint error. Do not change project_id on tasks updates When a task has invoiced timesheet lines, writing on 'project_id', even if the id is the same, would fail because of a constraint preventing to write project_id on timesheet lines. Refactorize aal batch importer with 'updating since' jira method This Jira method returns the list of ids updated since a timestamp, and the youngest timestamp, which means we can store this timestamp and reuse it the next time we ask the modified worklogs: this way we should never miss any update. To support this, a type of field which support milliseconds in datetime is required, otherwise lose this precision that Jira gives us. As of today, the "updated since" method exists on for worklogs on the Jira webservice, so the rest of the batch import still have to use the JQL filters (with minute-precision only). Use Datetime as main format for MilliDatetime field 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. Add batch deleter for worklogs Force reimport of worklogs as admin Add tests for jira.backend.timestamp Add jira.backend tests Fix JiraTransactionCase → JiraSavepointCase 👀 Add tests for batch importer of tasks and worklogs Add tests for worklogs deletes Fix lint

view details

Thierry Ducrest

commit sha 0e3d05e5615795ae8ce8eb75f84d7b146ef87eb2

Apply suggestions from code review Co-Authored-By: guewen <guewen.baconnier@camptocamp.com>

view details

Guewen Baconnier

commit sha 05639a6b1528c45c63ebc4d3250ce033d6622ab3

Fix oldname field Apply suggestions from @simahawk in code review Add scheduled action for importing deleted worklogs 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.

view details

Akim Juillerat

commit sha b6ac96550848100f2420995f53fc2f2fcde7119c

Fix psycopg2.ProgrammingError: syntax error when no updated_worklogs are passed

view details

Guewen Baconnier

commit sha d49df888631caa2a824a161d7b2f75b75346dd3b

Make migration more robust It seems that when updating other addons, even if we don't update connector_jira, it may already create the columns, then when we update connector_jira, it tries to create the columns when they already exist. Check before. Use the rendered task description as HTML The Jira REST API returns a rendered version of the description instead of the markup when we pass the 'expand=renderedFields' parameter. Update vrcpy cassettes as we read expanded issues With "expand=renderedFields"

view details

push time in 2 days

push eventcamptocamp/connector-jira

oca-git-bot

commit sha 1d14678ad495a4a14da1ed721237373db9ef6195

[IMP] pre-commit: pin node version [ci skip]

view details

Stéphane Bidoul

commit sha 4a2a1631a368a0e95e1ed70598b4243322b35406

Use prettier/pre-commit for compatibility with pre-commit 2.8 [ci skip]

view details

Stéphane Bidoul

commit sha 713b51c158ddd3dd7aa19e3c2e24b82d52644153

update dotfiles [ci skip]

view details

Stéphane Bidoul

commit sha e25fa2a4a1b12a095b18df20569cd9ae34332979

Upgrade pylint-odoo for 13.0 [ci skip] This is apprently necessary for the development status checks to work correctly.

view details

Guewen Baconnier

commit sha 960f15013aca1d6f39ae4130e8906b80e0081611

Add first brick of the connector_jira addon Add project binding Add export of projects Add Jira project tasks model Add external dependencies in manifest Add security accesses Add basic import of tasks Task import are triggered by Jira webhooks. A batch import must be added later to import the changes from missed hooks or for those not wanting to use the webhooks. Add a basic backend adapter Batch import of project tasks Remove markdown The fields are not in markdown, but in a wiki syntax (proper to JIRA yet be determined) Link users and import tasks assignees Import worklogs Use an adapter for the project export Import issue types Filter type of issues to synchronize And assign the worklog to the first parent we find that we synchronize. If the type of the worklog's issue is synchronized, the worklog is assigned on this issue. If the worklog's issue is a sub-task, and the parent task of the sub-task is of a synchronized type, it link it to it. If the task has an epic, and the epics are synchronized, it link it to it. In last resort, the worklog will be linked with the project but with no task. Configure the name of the Epic Link field from API Create webhooks in JIRA from Odoo Choose template on project creation Discard Epics from different projects JIRA allow to choose an epic for any project. Setting the Epic as the Odoo task would create inconsistencies between the project and the task. We discard such an Epic, likely the task will be empty. Delete worklogs deleted on JIRA (only with webhooks) Delete tasks deleted on JIRA (only with webhooks) Add JIRA issue type in tasks Add JIRA Issue Key Add core business project types Improve display of JIRA backend Use a dedicated button to activate the Epic Link. Link the Epic in a dedicated field Add JIRA Parent for subtasks Show JIRA key in name Create project from shared project Check JIRA project keys Remove the button to 'one-click-export' a project It can't be working because we have other fields to configure on the binding. Add help on issue type synchronizations Accept tasks without parent Do not use id builtin

view details

Damien Crier

commit sha 053b840bd19adc326e9db493bc72b74f41024eeb

Update ir.model.access.csv add `jira_account_analytic_line` object

view details

Guewen Baconnier

commit sha 3d7f480bbb1a89183c97956ed69eac744a1bf374

Set uninstallable Replace openerp namespace by odoo namespace Change to new Binder's API Migrate connector_jira to new 10.0 API Make addons uninstallable Apply 2to3 for python3 Migrate to new Component API Add setup guide in readme Migrate to v11 and Py3 Allow to delete a backend if we have issue types

view details

Simone Orsi

commit sha c0a619655c3ae81a97794316d11289d6f06cf585

C2C-152 Add project.task.jira_issue_url Fix project listener name typo Add links to JIRA issue on a.a.l Fix connector tab naming

view details

Timon Tschanz

commit sha 93af31825debeed9f225075fb01ae78ea4d41dd0

add epic and issuetype to analytic line

view details

Tonow-c2c

commit sha 6a469843ba36bb1d22a2b77756afaeb9a5481086

Test jira_key only if connector_no_export is True (#13)

view details

Simone Orsi

commit sha 3b4a28067c6cec9c862ad8d01bf54d3b03c621fc

Better handling of users sync

view details

Guewen Baconnier

commit sha 0c8e0df4af27cfd07ee5cf3feb2c90c6e880403d

Replace text_field by options text_field as attribute could not by validated by RNG, options is always valid Add base to support both export and link with projects Now linking a project with JIRA must be done through a wizard instead of the binding view. It must be either export (create the project on jira) or link (link with an existing project on jira). We keep this choice in the binding so we never export data to JIRA when we chose the link only.

view details

Patrick Tombez

commit sha 73838b2ec55e3df6b9a62212a1c5b3238b6003d7

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 https://github.com/pycontribs/jira/pull/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.

view details

Guewen Baconnier

commit sha c6677b42d9fd7711fc3966f216938a53cbd0c950

Read access tokens with sudo A normal user must be able to use the jira rest client under the hood. Update documentation Store original jira issues on analytic lines Instead of the issue they are linked to in Odoo. With the mechanism in place, if we don't import the task or bug issue types and we synchronize the epics, the worklogs will be attached to the epics of their tasks (of subtasks to tasks). The fields were showing the values of the Epic (or task for subtask), though it makes much more sense to keep the keys and URLs of the original issue and epic on the analytic lines. We still have the link to the task if we want to get the URL for the task they are currently linked to. Fix project binding unique constraint We should be able to have 2 bindings without external_id (not yet exported) Add wizard to link a task to JIRA Refactorize multistep wizards with a mixin Handle jira bindings in tasks merge wizard Import name of Epics instead of summary The Epic issues have a special (custom) field for their name. In fact they use both, the custom field AND the summary field. But I guess they are better identified by their epic name than their summary. Extract multi_step_wizard as an addon Set a timeout on requests to JIRA Fix typo in readme Fix backend selection on wizard to link a task The computed field was not called, due to the model being a TransientModel, replace it by default values. Add is_master on jira project bindings 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. Move jira_key from project to jira project binding As we can have more than one project binding, we cannot store a single jira key. In case we have more than one jira key for a project, we compute a compound key joined by commas. Add method to handle jira API / connection errors Add migration for 11.0.1.1.0 Fix error when several odoo users match When we are importing a worklog for a user not yet linked and we found several candidate users in odoo, they will both be linked with the same jira user and make the unicity constraint fail. Properly raise an error in this case. Fix project_type as string Add fallback project for worklogs A new optional field on the backend allows to choose a fallback project for the worklogs. When a worklog doesn't match any project linked with Jira, they will be created there, allowing to find the misconfigurations and fix them. Add action to reimport worklogs from Jira This is meant mainly to be used when a worklog has been imported in the fallback project and we need to re-affect them to the correct project after we linked it. Add related action to open jira with import issues The 'related' button on jobs which import issues or worklog will now open jira directly on the issue. Skip import of tasks/worklogs before batch dates Jira may send webhooks for old records, for instance worklogs from 6 month ago because their task has been changed. This change ensures that we never import any record which has a last update date before the last date of batch import. The job methods now return the result of Importer.run() so the result is shown on the jobs in the UI. Extract import of dependencies Allowing to override partially the dependencies to import Fix import of subtasks When importing the parent of a subtask, the record in the 'parent' field (the task data) is incomplete, it contains only a few fields. Providing only the id to the dependency Importer will force it to read the whole record from Jira. 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. 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 Change xmlid for model_account_analytic_line account is not necessarily installed, while analytic is installed by the project module in any case Partial revert of 2fa7d39 Commit title was: Skip import of tasks/worklogs before batch dates The process is the following: * Read T from backend, T is the is the last time we ran the import * Create a batch job to import tasks/worklogs from T to now() and update the backend with now() The batch job is run asynchronously, it generates one job per task or worklog to import between T and now(). When the jobs are executed, the last batch date has already been updated to now(), so the jobs would never import any record. Fix error when force_reimport called on several records Prevent changing task's project on binding When the task Mapper binds a task to a task already existing in Odoo, we must not change the project_id of the task. This is not possible as long as we have invoiced timesheet lines, even if the id is the same than the current one. Add base for tests and a test for oauth Add test for check of connection With a fix in the method: getting the client only wasn't triggering any error, calling 'myself' raises a 401 when we are not authenticated. Add documentation for tests Add travis configuration Add tests on issue types and tasks Add first test for analytic account lines Make pylint-odoo happy Add a script to initiate the Oauth dance

view details

Thierry Ducrest

commit sha 4ba2b87ae17e6aae81a5325a3bc56212c600495a

Apply suggestions from code review Co-Authored-By: guewen <guewen.baconnier@camptocamp.com>

view details

Guewen Baconnier

commit sha 77219d1958035122da3027a35e7e577f3bd5d58a

Prevent error when linking users When another user is already linked with the same jira user and matches. Without this check, the transaction fails with a unique constraint error. Do not change project_id on tasks updates When a task has invoiced timesheet lines, writing on 'project_id', even if the id is the same, would fail because of a constraint preventing to write project_id on timesheet lines. Refactorize aal batch importer with 'updating since' jira method This Jira method returns the list of ids updated since a timestamp, and the youngest timestamp, which means we can store this timestamp and reuse it the next time we ask the modified worklogs: this way we should never miss any update. To support this, a type of field which support milliseconds in datetime is required, otherwise lose this precision that Jira gives us. As of today, the "updated since" method exists on for worklogs on the Jira webservice, so the rest of the batch import still have to use the JQL filters (with minute-precision only). Use Datetime as main format for MilliDatetime field 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. Add batch deleter for worklogs Force reimport of worklogs as admin Add tests for jira.backend.timestamp Add jira.backend tests Fix JiraTransactionCase → JiraSavepointCase 👀 Add tests for batch importer of tasks and worklogs Add tests for worklogs deletes Fix lint

view details

Thierry Ducrest

commit sha 2b04fab43289216e84d1a9f752a65db7fc12b60e

Apply suggestions from code review Co-Authored-By: guewen <guewen.baconnier@camptocamp.com>

view details

Guewen Baconnier

commit sha 334b1f8806136f7576b2d2e6ccd0122a17a824a4

Fix oldname field Apply suggestions from @simahawk in code review Add scheduled action for importing deleted worklogs 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.

view details

Akim Juillerat

commit sha 7390bef964fa886f70be8f313d348cb61cbd377b

Fix psycopg2.ProgrammingError: syntax error when no updated_worklogs are passed

view details

Guewen Baconnier

commit sha 0b7d7f1afb75b2766eea17d143476a2eef4c139f

Make migration more robust It seems that when updating other addons, even if we don't update connector_jira, it may already create the columns, then when we update connector_jira, it tries to create the columns when they already exist. Check before. Use the rendered task description as HTML The Jira REST API returns a rendered version of the description instead of the markup when we pass the 'expand=renderedFields' parameter. Update vrcpy cassettes as we read expanded issues With "expand=renderedFields"

view details

push time in 2 days

create barnchcamptocamp/multi-company

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

create barnchcamptocamp/sale-workflow

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

create barnchcamptocamp/server-env

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

create barnchcamptocamp/event

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

create barnchcamptocamp/e-commerce

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

create barnchcamptocamp/pos

branch : merge-branch-2805-13.0.2.14.0

created branch time in 3 days

PR opened camptocamp/odoo-event-addons

[13.0][Fix] event_report_badge event-badge stlye

Fixing page size that was not fitting the page height. Also addim a page break after each event-badge.

+2 -1

0 comment

1 changed file

pr created time in 3 days

fork santostelmo/odoo-event-addons

Our collection of Odoo events management addons

fork in 3 days