ZOA controller reported seeing a confusing data block. Controller checked with pilot and then called...

Narrative:

Aircraft X was an eastbound climber into my sector from sector 32. I was distracted working with other issues to the south and aircraft X checked on most likely level at FL350 with FL370 and a climb arrow in his data block. I obviously didn't hear it. Minutes later I noticed on my scan the aircraft level at FL350 and a limited data block on a northbound aircraft in sector 32's airspace. I quickly surmised that the aircraft was given FL350 and handed off to me shown as climbing to FL370. So I asked aircraft X his assigned altitude and he said; 'FL350 but we would like FL370;' and I cleared the aircraft up. This issue has been going on for a while so I called sector 32 and asked; 'hey; are you using something like a dwell lock to remind you when an aircraft needs clearance still as aircraft X was level at 350?' he said; 'sometimes stuff just happens.' I was like (wow) in my head and had no real response except to say; 'you might file a report on that one.' of course my emotions ran high inside and very irritated at the response.according to the 7110.65 an aircraft should be handed off and shipped to the altitude it was assigned. Anything else is dangerous because of memory lapse and aircraft leveling in possible confliction with traffic they would normally miss if given the correct altitude. Area north needs to have a briefing for all controls to return to the basics. If this is happening this often with me; then I am sure with others it is occurring and they are not reporting it.

Original NASA ASRS Text

Title: ZOA Controller reported seeing a confusing data block. Controller checked with pilot and then called transferring Controller to verify what had been done. Reporter then discussed the actions with the transferring Controller.

Narrative: Aircraft X was an eastbound climber into my sector from sector 32. I was distracted working with other issues to the south and Aircraft X checked on most likely level at FL350 with FL370 and a climb arrow in his data block. I obviously didn't hear it. Minutes later I noticed on my scan the aircraft level at FL350 and a limited data block on a northbound aircraft in sector 32's airspace. I quickly surmised that the aircraft was given FL350 and handed off to me shown as climbing to FL370. So I asked Aircraft X his assigned altitude and he said; 'FL350 but we would like FL370;' and I cleared the aircraft up. This issue has been going on for a while so I called sector 32 and asked; 'hey; are you using something like a dwell lock to remind you when an aircraft needs clearance still as Aircraft X was level at 350?' He said; 'sometimes stuff just happens.' I was like (WOW) in my head and had no real response except to say; 'you might file a report on that one.' Of course my emotions ran high inside and very irritated at the response.According to the 7110.65 an aircraft should be handed off and shipped to the altitude it was assigned. Anything else is dangerous because of memory lapse and aircraft leveling in possible confliction with traffic they would normally miss if given the correct altitude. Area North needs to have a briefing for all controls to return to the basics. If this is happening this often with me; then I am sure with others it is occurring and they are not reporting it.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1352238
Time
Date	201605
Local Time Of Day	1201-1800
Place
Locale Reference	ZOA.ARTCC
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	Medium Large Transport
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (mon) 6
Events
Anomaly	ATC Issue All Types Deviation - Altitude Excursion From Assigned Altitude Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

ZOA controller reported seeing a confusing data block. Controller checked with pilot and then called transferring controller to verify what had been done. Reporter then discussed the actions with the transferring controller.