Fixes Safari issue. Does not fix the "chrome browserstack issue",
which turned out to be a timezone/systemtime issue and occured
because the browserstack session had different timezone.
Propose to tackle timezone/systemtime handling in separate story.
Change-Id: I892b888b929df21de04bf06626c3d404c34375e3
What has been done:
- TT#39817, [Issue] CallForwarding: "Number destinations" that contain
non-number chars are not rendered
- TT#39819, [Issue] CallForwarding: Terminated destinations tooltip have
wrong meaning
Change-Id: I3ba55f367012f0deb82c5e9d6fef8c1d1b800335
What has been done:
- TT#29602, CallForwarding: Create UI input form
- TT#29603, CallForwarding: Implement API method for add new destination
- TT#29604, CallForwarding: Implement store and bindings for add new
destination feature
Change-Id: I723488e684990c21ee74700cf6e849a5d16cda9c
What has been done:
- TT#28055, CallForwarding: As a Customer, I want to see all call
forwarding rules that apply "Always" (INCL all subtasks)
- TT#28059, CallForwarding: As a Customer, I want to remove Destinations
Change-Id: Id1e95dbaf1e55dba25f855ef9ad61352ededd5bb
What has been done:
- TT#23719, Conversations: Discover the conversations endpoint and
investigate dev tests
- TT#23812, Conversations: Implement store with needed states
- TT#23813, Conversations: Implement minimal card component
- TT#23814, Conversations: Implement store and api tests
- TT#23815, Conversations: Implement action and api request
Change-Id: I40231aded1309695d9a2ab15e196db7c83b62018
raxelsen
Hans-Peter Herzog