View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0007036 | 10000-014: PubSub | Spec | public | 2021-06-17 16:44 | 2022-06-23 12:33 |
| Reporter | Zbynek Zahradnik | Assigned To | Matthias Damm | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Target Version | 1.05.02 RC1 | Fixed in Version | 1.05.02 RC1 | ||
| Summary | 0007036: Timestamp and Status in keep-alive JSON DataSetMessage not clearly specified | ||||
| Description | In a keep-alive JSON DataSetMessage, if Timestamp or Status field is enabled in JsonDataSetMessageContentMask, should they also be included in the keep-alive message, and if so, what should be their values? | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
| related to | 0006308 | closed | Matthias Damm | Clarify how a JSON PubSub message is encoded |
| related to | 0007871 | closed | Matthias Damm | JSON DataSetMessage fields Timestamp and StatusCode need clarification. |
|
|
Resolved with changes to 0007871 |
|
|
Agreed to changes edited in Munich F2F. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2021-06-17 16:44 | Zbynek Zahradnik | New Issue | |
| 2021-06-17 16:44 | Zbynek Zahradnik | Status | new => assigned |
| 2021-06-17 16:44 | Zbynek Zahradnik | Assigned To | => Matthias Damm |
| 2022-03-10 18:46 | Matthias Damm | Relationship added | related to 0006308 |
| 2022-03-10 18:46 | Matthias Damm | Target Version | => 1.05.02 RC1 |
| 2022-03-18 13:35 | Zbynek Zahradnik | Relationship added | related to 0007871 |
| 2022-06-22 13:36 | Matthias Damm | Status | assigned => resolved |
| 2022-06-22 13:36 | Matthias Damm | Resolution | open => fixed |
| 2022-06-22 13:36 | Matthias Damm | Note Added: 0016988 | |
| 2022-06-23 12:33 | Jim Luth | Status | resolved => closed |
| 2022-06-23 12:33 | Jim Luth | Fixed in Version | => 1.05.02 RC1 |
| 2022-06-23 12:33 | Jim Luth | Note Added: 0017028 |
