CareerCup

The severity should be very high
and priority too should be very high (ship stopper)
because this is the major use case of any mobile number. and all customers wil face it

With saving Diffrent name,call will goes to another person.

So,Priority should be P1.And Severity should be blocker r go for critical bug.

priority should be high n seviority should be major.

In this case the severity is medium or low and the priority will be High. because it may effect from the business point of view.
And low severity Because it is not affecting the other feature of the Mobile Phone

Bug severity:

Sev. 1: Catastrophic.
The system is breaking. The existence of the system is in question.
Ex: installation failing

Sev. 2: Feature blockage.
A promised feature is not working at all.
Ex: The save contact feature not working as above.

Sev. 3: Use case failure
Feature working but a major use case failing
Ex: Save contacts working but cannot store names beginning with Z.

Sev. 4:
Not exhaustive coverage of use cases (less severe than sev. 3)
Ex: Save contacts working fine but not displaying error messages when the name field is left empty.

Sev. 5:
Cosmetic
Ex: Background is not according the the UE standards.

Sev. 6:
Enahncement
Ex: Save email address also in addition to the phone number in every contact.

According to the aforementioned definitions, the bug mentioned in the question looks to be a Sev. 2.

Priority depends on the time and resource constraints and other bugs that the team is supposed to handle.

Priority will also depend on how critical the feature is from the marketing, user experience and product impact, product impression perspective.

Priority will also depend on whether the bug is blocking the test team from further testing.

Sev = 1
Pri = 1
As this is related to the major functionality of the phone, Person will not be able to contact the right person. So acting as a showstopper plus creating new problems as number is going to someone else.

Think of SMS, if you are sending to you frnd about yout gf and it actually reaches your gf :P :P

At customer point of view ,Priority is high & severity is low (anyway he/she can able to save the number in phone)

If unable to save means P is Very High & S is Very High

A BA / User defines priority depending upon importance of the defect and a developer defines severity depending upon complexity of the defect. Asking tester to set it is wrong practice. Anyway, if a tester has to set it then the defect is..

High priority: As my domain knowledge as a tester suggests me that the feature is verify important.

Low Severity: As the issue is with a variable in the code or a the query that inserts data which is not complex and won't take much time to fix