You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users are having issues with adding contacts to project revisions (including new projects). Then end result of whatever is going on is that the form data does not get a contactIndex assigned, which seems to prevent them from being able to commit the revision.
One description of behaviour that resulted in this bug:
"When entering primary and secondary contacts they will flip on each other (making secondary the primary and the primary the secondary) This can righted by going back in to the drop downs and reselecting the contacts but thought I would mention it since we've had issues within this tab recently. " -LP
And another:
"when you select "Add a Secondary Contact" the fields appear and then quickly disappear...prompting you to select the secondary contact option again and when you do, two sets of secondary contact fields show up, leaving you to remove one and then you can proceed to populate them - but not always able to apply to revision." -LP
Probability (how likely the bug is to happen, scored from 1-5): 2 although it is in fact happening
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): 5 users cannot commit project revisions
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:
We've been unable to reproduce any of the behaviour locally or in dev so far. The evidence of it happening is there in prod though.
OS: [e.g. iOS]
Browser: [e.g. chrome, safari]
Version: [e.g. 22]
Additional context
The text was updated successfully, but these errors were encountered:
Describe the Bug:
Some users are having issues with adding contacts to project revisions (including new projects). Then end result of whatever is going on is that the form data does not get a
contactIndex
assigned, which seems to prevent them from being able to commit the revision.One description of behaviour that resulted in this bug:
"When entering primary and secondary contacts they will flip on each other (making secondary the primary and the primary the secondary) This can righted by going back in to the drop downs and reselecting the contacts but thought I would mention it since we've had issues within this tab recently. " -LP
And another:
"when you select "Add a Secondary Contact" the fields appear and then quickly disappear...prompting you to select the secondary contact option again and when you do, two sets of secondary contact fields show up, leaving you to remove one and then you can proceed to populate them - but not always able to apply to revision." -LP
Probability (how likely the bug is to happen, scored from 1-5): 2 although it is in fact happening
(For example, probability of 5 is something like "it happens to all users every time they log in."
Probability of 1 "only happens to certain users when a really specific and unlikely path is followed.")
Effect (how bad the bug is when it does happen, scored from 1-5): 5 users cannot commit project revisions
(For example, effect of 5 is "the entire app crashes and makes it unusable for all users" or "the bug causes the wrong data to be saved, with critical information (e.g. payment) being affected."
Effect of 1 is "It makes some styling look a little bit weird.")
Steps to reproduce the behaviour:
Screenshots:
Additional information:
We've been unable to reproduce any of the behaviour locally or in dev so far. The evidence of it happening is there in prod though.
The text was updated successfully, but these errors were encountered: