An issue, now called a work item in Cloud, has a stable key and editable fields. The summary names the work. Priority describes urgency or relative importance under the team's policy. Assignee names the person responsible for the next action; reporter identifies who raised it. These fields answer different questions.
Read the key before saving. Similar summaries are common, especially for recurring service requests. A blank assignee is a missing responsibility value, not a user called Unassigned. Story points express an estimate for a team's planning method and can stay empty when work hasn't been estimated. The local practice record shows these values directly. Keep unrelated fields unchanged unless the request explains why they must change too.
Edit the named issue without confusing display text and identity.