Ticket

back to ticket overview

Project RCM Ultimate
Summary Slave does not unassign transponder
Sequence 3269
Classification Bug
Priority Low
Status Done
Kickoff date Dec 30, 1899
Maturity date Dec 30, 1899
Responsible
Version 2.5.4
Expense 0
Description When transponder is unassigned in master the slave pc does not do it, it maintains all transponders (assigned and unassigned) in driver's transponder "table"

Change history

Timestamp Who Modification
Jun 3, 2022 10:20:27 AM Ticket created
Nov 12, 2023 2:22:22 PM Felix Romer Field: Title
Old value: Slave does not unasign transponder
New value : Slave does not unassign transponder
Nov 12, 2023 2:22:28 PM Felix Romer Field: Specification
Old value: When transponder is unasigned in master the slave pc does not do it, it maintains all transponders (asigned and unasigned) in driver's transponder "table"
New value : When transponder is unassigned in master the slave pc does not do it, it maintains all transponders (asigned and unasigned) in driver's transponder "table"
Nov 12, 2023 2:22:32 PM Felix Romer Field: Specification
Old value: When transponder is unassigned in master the slave pc does not do it, it maintains all transponders (asigned and unasigned) in driver's transponder "table"
New value : When transponder is unassigned in master the slave pc does not do it, it maintains all transponders (assigned and unassigned) in driver's transponder "table"
Sep 21, 2024 8:10:34 AM Felix Romer Field: Responsible
Old value: -
New value : Romer Felix
Sep 21, 2024 8:10:34 AM Felix Romer Field: Status
Old value: Opened
New value : Running
Sep 21, 2024 8:10:34 AM Felix Romer Field: Version
Old value:
New value : 2.5.4
Sep 21, 2024 8:50:28 AM Felix Romer Field: Status
Old value: Running
New value : Done