View Issue Details

IDProjectCategoryView StatusLast Update
00033761 - BacklogBugpublic2019-07-11 23:34
ReporterKC7FPFAssigned ToKC7FPF 
PrioritynormalSeverityminorReproducibilityalways
Status feedbackResolutionopen 
Summary0003376: Incorrect QTH Data
DescriptionWhen you look at my address and QTH you find the word Kingstown, which is incorrect information. Several months ago, I talked with an HRD technician several times about this issue and was assured that the problem would be corrected with the next revision of HRD. That has been several months ago and it still hasn't been corrected.



Steps To ReproduceI did a callsign loop up on this customer as got the same result. With incorrect QTH information in the HRD logbook. However if you do a call sign lookup in QRZ is displays the correct information.
Additional InformationSeveral months ago, I talked with an HRD technician several times about this issue and was assured that the problem would be corrected with the next revision of HRD. That has been several months ago and it still hasn't been corrected. Both Ferry and Tim got the same result. Speaking with tim he indicated at some point. this issue was resolved.

I changed the call sign look up to the callook option in the logbook. At this point it did retrieve and display the correct QTH information for the customer.
Please refer to ticket 319986.
TagsNo tags attached.
ModuleLogbook
Sub-ModuleCall lookup
TestingNot Started

Relationships

related to 0003001 resolvedK7ZCZ 3 - Current Dev List Callsign lookup function does not appear to be working as designed 

Activities

K7ZCZ

2019-07-05 15:21

administrator   ~0008194

Please provide clear repro steps so that this issue can be investigated.

KC7FPF

2019-07-05 15:59

updater   ~0008197

I changed the call sign look up option to callook.info option in the logbook Callsign lookup option. Once this was completed. Did a
Call sign lookup with the the callsign in question. At this point it did retrieve and display the correct QTH information for the customer.
Returned to the callsign lookup option. Changed it back the QRZ.com. Once this was completed. Did a callsign lookup with the callsign in question. Came back with the incorrect QTH information. QTH data is listed correctly on QRZ.

Please refer to ticket 319986.

K7ZCZ

2019-07-11 18:50

administrator   ~0008216

I've related this to 3001, which is the issue that's tracking the re-write of the callsign lookup. Odds are, this issue is resolved by that re-write.

If we think a fix is more urgent, that issue should be brought up with triage with suggested prioritization.

WA9PIE

2019-07-11 23:34

administrator   ~0008217

This is a duplicate that will get corrected with the revision to callsign lookup.

Issue History

Date Modified Username Field Change
2019-07-05 09:51 KC7FPF New Issue
2019-07-05 15:21 K7ZCZ Assigned To => KC7FPF
2019-07-05 15:21 K7ZCZ Status new => feedback
2019-07-05 15:21 K7ZCZ Note Added: 0008194
2019-07-05 15:59 KC7FPF Note Added: 0008197
2019-07-11 14:23 K7ZCZ Relationship added related to 0003001
2019-07-11 18:50 K7ZCZ Note Added: 0008216
2019-07-11 23:34 WA9PIE Note Added: 0008217