Started by timer738c11453c0e75288e9d497bff9644e55c9541eafeac11453c0e75288e9d497bff9644e55c9541eafearefs/remotes/origin/devc11453c0e75288e9d497bff9644e55c9541eafeac11453c0e75288e9d497bff9644e55c9541eafearefs/remotes/origin/devc11453c0e75288e9d497bff9644e55c9541eafeac11453c0e75288e9d497bff9644e55c9541eafearefs/remotes/origin/devhttps://github.com/younex1/erp-nuxt-frontend.githttps://jenkins.younex.de/view/all/job/build-logship-frontend/738/artifacthttps://jenkins.younex.de/view/all/job/build-logship-frontend/changeshttps://jenkins.younex.de/view/all/job/build-logship-frontend/738/https://jenkins.younex.de/view/all/job/build-logship-frontend/738/testReportfalse#7386868571602build-logship-frontend #738738falsefalse7385705SUCCESS1789516800273https://jenkins.younex.de/view/all/job/build-logship-frontend/738/- app/components/dashboard/RecentCallsCard.vueserver/api/telephony/blacklist.post.tsserver/utils/telephony/blacklist.tsapp/assets/langs/shared.js31601308527d637a24ce1dbb928085488affb6c81789459780000https://jenkins.younex.de/user/infoinfoinfo@younex.deDashboard: add call-blacklist button to Recent Calls card
Admin-only "Sperren" action per row, writes to FreePBX's astdb-based
Blacklist via AMI DBPut (no MySQL table involved) so future calls from
that number are rejected immediately.
2026-09-15 10:09:40 +020031601308527d637a24ce1dbb928085488affb6c8Dashboard: add call-blacklist button to Recent Calls cardeditapp/components/dashboard/RecentCallsCard.vueaddserver/api/telephony/blacklist.post.tseditapp/assets/langs/shared.jsaddserver/utils/telephony/blacklist.ts
- server/utils/telephony/cdr.tsapp/components/dashboard/RecentCallsCard.vueapp/assets/langs/shared.jsd8620a46b42efac1131bfce361e06bb2beec307b1789460110000https://jenkins.younex.de/user/infoinfoinfo@younex.deDashboard: always show Queue-routed calls on Recent Calls card
Previously the card only showed missed inbound + answered outbound,
so support-line calls that came in via the Queue and got answered
(possibly after a missed ring on another agent) never appeared.
Queue-routed inbound calls now always show regardless of outcome;
direct-dial inbound calls keep the missed-only behavior.
2026-09-15 10:15:10 +0200d8620a46b42efac1131bfce361e06bb2beec307bDashboard: always show Queue-routed calls on Recent Calls cardeditapp/assets/langs/shared.jseditserver/utils/telephony/cdr.tseditapp/components/dashboard/RecentCallsCard.vue
- app/pages/sales/sis/index.vueserver/api/sales/sis/listings.get.tsserver/utils/sisMatching.tsserver/utils/amazonSpApi.tsserver/api/sales/sis/price-update.post.ts89a23e942f5ea0be7a9453c79ffef0b394b352f61789462887000https://jenkins.younex.de/user/infoinfoinfo@younex.deSIS: fix intermittent load hang, safen Amazon price pushes, in-flight glow
Amazon-side errors (report timeout, 429, ...) were silently triggering a
full refresh-and-retry of the whole route (report poll + matching, or a
full price push run twice) because event.context.lastIdempiereError is
only ever set by iDempiere calls — tag Amazon-origin errors and skip the
retry for them. Also: timeouts + retry-after-aware backoff on every raw
SP-API/LWA call (none had any before), parallelize the previously serial
SKU/ASIN/price chunk lookups in sisMatching.ts, a real loading
spinner/elapsed-time + client-side fetch timeout instead of a static
"Loading listings..." line, and a per-order-source push queue so rapid
per-field price pushes never burst past Amazon's ~1 req/sec limit.
Also adds the requested "knight rider" glowing border animation on a
price field while its push is in flight, handing off to the existing
success/error flash once it resolves.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013G7aDXCyYUwGgTG81QTP8E
2026-09-15 11:01:27 +020089a23e942f5ea0be7a9453c79ffef0b394b352f6SIS: fix intermittent load hang, safen Amazon price pushes, in-flight gloweditserver/api/sales/sis/listings.get.tseditserver/api/sales/sis/price-update.post.tseditserver/utils/sisMatching.tseditapp/pages/sales/sis/index.vueeditserver/utils/amazonSpApi.ts
- server/api/telephony/recordings/audio.get.tsserver/utils/telephony/recordings.ts11e64f412c360e3e27d2d2f1e62aceee6f5f3e2f1789462899000https://jenkins.younex.de/user/infoinfoinfo@younex.deTelephony: fix call recording playback for .gsm files
Recordings served as .gsm played inconsistently in the dashboard phone
card and the contact-page recordings modal ("play does nothing" for
most, "player shows up" only for .wav/.mp3) — no browser ships a native
GSM 06.10 decoder, so the <audio> element just sits at
readyState=HAVE_NOTHING forever with no error event. ffmpeg (already
used to decode these same .gsm files for whisper transcription)
transcodes .gsm to mp3 server-side before streaming; .wav/.mp3 pass
through unchanged.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013G7aDXCyYUwGgTG81QTP8E
2026-09-15 11:01:39 +020011e64f412c360e3e27d2d2f1e62aceee6f5f3e2fTelephony: fix call recording playback for .gsm fileseditserver/utils/telephony/recordings.tseditserver/api/telephony/recordings/audio.get.ts
- app/pages/sales/returns/index.vuee7e99c24f3437370b725c5cd1ff3b75eb198bf861789463284000https://jenkins.younex.de/user/infoinfoinfo@younex.deReturns: add searchable Products column (line items + qty)
/sales/returns now fetches ?withLines=1 (the M_InOutLine + nested
M_Product_ID expand already used by the dashboard "Letzte Retouren"
card) and shows the returned products with their quantities inline in
a new grid column, with its own text filter — no master-detail.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013G7aDXCyYUwGgTG81QTP8E
2026-09-15 11:08:04 +0200e7e99c24f3437370b725c5cd1ff3b75eb198bf86Returns: add searchable Products column (line items + qty)editapp/pages/sales/returns/index.vue
- app/pages/integrations/inventory-desktop.vue376abf176801739a3c3d427a56263898d657861c1789470038000https://jenkins.younex.de/user/infoinfoinfo@younex.deInventory Desktop: BOM tags + exclude-BOM filter on article search
Ports the same excludeBom checkbox + BOM/JTL-BOM tags mobile/inventory.vue
already has on its article text search (server already supports both via
/api/materials/products/search?excludeBom=), but defaults the checkbox to
checked here — a physical stock count is about individually-located
articles, not kit/BOM headers, unlike the mobile default (unchecked).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013G7aDXCyYUwGgTG81QTP8E
2026-09-15 13:00:38 +0200376abf176801739a3c3d427a56263898d657861cInventory Desktop: BOM tags + exclude-BOM filter on article searcheditapp/pages/integrations/inventory-desktop.vue
- server/api/print/return-label.post.ts006f06ebd1f54f49f2fef962ffa4a48861c1a8621789482747000https://jenkins.younex.de/user/infoinfoinfo@younex.deReturn label: enlarge header-band text for readability
Company name and date/time in the dark top band were too small against
the fill, especially on the common 74x52/56x75/102x152 label sizes.
Bumps bar height and font sizes on both sides and raises the minimum
shrink-to-fit floor for long company names.
2026-09-15 16:32:27 +0200006f06ebd1f54f49f2fef962ffa4a48861c1a862Return label: enlarge header-band text for readabilityeditserver/api/print/return-label.post.ts
- app/composables/useReturnLabelPrinter.tsserver/api/print/return-label.post.tsapp/components/NavBar.vueapp/composables/states.tsapp/components/rmas/ReturnLabelPrinterPicker.vueapp/pages/mobile/return.vueapp/pages/integrations/returns-desktop.vue8e1a9966727348cffb3a45f49e81b2eebed592d51789482760000https://jenkins.younex.de/user/infoinfoinfo@younex.deReturn-label printer: org default + per-session override
Return labels no longer print per-article, so the legacy per-product
printer field (m_product.labelprinter_rma) no longer fits how they're
used. Replaces it with a printer picker in the top navbar (desktop) /
returns page header (mobile), admin-only (IsClientAdministrator), that
staff switch per working place — remembered per device via localStorage
so it survives reloads. Falls back to the org's CUST_Printer marked
"Default printer (for its type)" (printerType=lab), else the lab
printer with the smallest id.
Also fixes a bug in /api/print/return-label where an explicit body.queue
override was never actually consulted (labelPrinterId always defaulted
to a truthy 'b', winning the || before queue was checked), and
consolidates return-label printing to one request per return instead of
grouping lines by printer — a return is one label listing every article,
so the old per-product grouping could silently split one return across
multiple partial-article labels.
2026-09-15 16:32:40 +02008e1a9966727348cffb3a45f49e81b2eebed592d5Return-label printer: org default + per-session overrideeditapp/composables/states.tseditapp/pages/mobile/return.vueaddapp/components/rmas/ReturnLabelPrinterPicker.vueeditapp/pages/integrations/returns-desktop.vueeditapp/components/NavBar.vueaddapp/composables/useReturnLabelPrinter.tseditserver/api/print/return-label.post.ts
- app/components/sales/OrderForm.vue70d978c5f75ce97343d7740bbd8478a2c3d7b01d1789482764000https://jenkins.younex.de/user/infoinfoinfo@younex.deSales order edit: emphasize ship-to name over partner
On the completed-order shipping summary, the partner name was bold and
the actual ship-to location (Name/Name2) was plain text, making it easy
to misread which one the order ships to. Indents the partner row and
drops its bold, and bolds the Name/Name2 values instead.
2026-09-15 16:32:44 +020070d978c5f75ce97343d7740bbd8478a2c3d7b01dSales order edit: emphasize ship-to name over partnereditapp/components/sales/OrderForm.vue
- app/components/requests/MyTicketDetail.vuec11453c0e75288e9d497bff9644e55c9541eafea1789483734000https://jenkins.younex.de/user/infoinfoinfo@younex.deMy-Tickets: fix staff replies stamped with wrong org, hiding them from limited-role customers
sendMessage() stamped new r_requestupdate rows with the replying staff
member's currently active org (logship_organization_id cookie) instead
of the ticket's own org. A limited-role customer's access is scoped to
only their own org (IsAccessAllOrgs=false), so any reply written while
staff had a different org active became invisible to them via
iDempiere's row-level security — even though the ticket itself and
their own messages stayed visible. Every other send path in this file
(accounting-flag note, assign-to-merchant, status actions) already
preferred the ticket's own org with this exact fallback; only the main
composer's sendMessage() was missing it.
Confirmed against production data: customer "stoyan" (Wonderhome) was
missing 4 of 9 staff replies on ticket 1000426, all sent while support
had a different org active.
2026-09-15 16:48:54 +0200c11453c0e75288e9d497bff9644e55c9541eafeaMy-Tickets: fix staff replies stamped with wrong org, hiding them from limited-role customerseditapp/components/requests/MyTicketDetail.vue
githttps://jenkins.younex.de/user/infoinfoinfo