(In reply to Alessandro Castellani [:aleca] from comment #5) I'm still wondering how hard it would be to just restore the old `Get Maps` button using the existing strings as an interim fix... > This is not a severe bug. That's why I had marked it `S3 = (Normal) Blocks non-critical functionality and a work around exists` which still looks like a good fit ;-) As discussed elsewhere, [triaged defects](https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-is-a-triaged-bug) should always have an explicit severity set. > It's indeed annoying but it's not a major blocker and a workaround with a URL is possible. Sure. It's just that first creating the URL online (by manually putting the address data in) and then copying it back to TB is quite cumbersome, compared to just clicking the `Get Map` button... > We're exploring the possibility to add an integrated map inside the contact view, if the user enables it. That's super cool if and when it really happens, however, in the meantime, our users would probably be happy just to have the old `Get Maps` button back to reduce their workflow suffering from its absence... > Setting P3 for backlog as P4 is reported to be as "Do not use, this priority is for web platform test bots". :P > https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Good catch! Not sure why "P4 - ...this priority is for web platform test bots" should be applicable to Thunderbird, but then, you never know and until we have agreed on a Thunderbird priority matrix which matches our release cycles, we can probably just stick to that.
Bug 1781076 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Alessandro Castellani [:aleca] from comment #5) I'm still wondering how hard it would be to just restore the old `Get Maps` button using the existing strings as an interim fix... > This is not a severe bug. That's why I had marked it `S3 = (Normal) Blocks non-critical functionality and a work around exists` which still looks like a good fit ;-) As discussed elsewhere, [triaged defects](https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-is-a-triaged-bug) should always have an explicit severity set. > It's indeed annoying but it's not a major blocker and a workaround with a URL is possible. Sure. It's just that first creating the URL online (by manually putting the address data in) and then copying it back to TB is quite cumbersome, compared to just clicking the `Get Map` button... > We're exploring the possibility to add an integrated map inside the contact view, if the user enables it. That's super cool if and when it really happens, however, in the meantime, our users would probably be happy just to have the old `Get Maps` button back to reduce their workflow suffering from its absence... > Setting P3 for backlog as P4 is reported to be as "Do not use, this priority is for web platform test bots". :P > https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Good catch! Not sure why "P4 - ...this priority is for web platform test bots" should be applicable to Thunderbird, but then, you never know and until we have agreed on a Thunderbird priority matrix which matches our release cycles, we can probably just stick to that.
(In reply to Alessandro Castellani [:aleca] from comment #5) I'm still wondering how hard it would be to just restore the old `Get Maps` button using the existing strings as an interim fix... > This is not a severe bug. That's why I had marked it `S3 = (Normal) Blocks non-critical functionality and a work around exists`, which still looks like a good fit ;-) As discussed elsewhere, [triaged defects](https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-is-a-triaged-bug) should always have an explicit severity set. > It's indeed annoying but it's not a major blocker and a workaround with a URL is possible. Sure. It's just that first creating the URL online (by manually putting the address data in) and then copying it back to TB is quite cumbersome, compared to just clicking the `Get Map` button... > We're exploring the possibility to add an integrated map inside the contact view, if the user enables it. That's super cool if and when it really happens, however, in the meantime, our users would probably be happy just to have the old `Get Maps` button back to reduce their workflow suffering from its absence... > Setting P3 for backlog as P4 is reported to be as "Do not use, this priority is for web platform test bots". :P > https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Good catch! Not sure why "P4 - ...this priority is for web platform test bots" should be applicable to Thunderbird, but then, you never know and until we have agreed on a Thunderbird priority matrix which matches our release cycles, we can probably just stick to that.
(In reply to Alessandro Castellani [:aleca] from comment #5) I'm still wondering how hard it would be to just restore the old `Get Maps` button using the existing strings as an interim fix... > This is not a severe bug. That's why I had marked it `S3 = (Normal) Blocks non-critical functionality and a work around exists`, which still looks like a good fit ;-) As discussed elsewhere, [triaged defects](https://firefox-source-docs.mozilla.org/bug-mgmt/policies/triage-bugzilla.html#what-is-a-triaged-bug) should always have an explicit severity set. > It's indeed annoying but it's not a major blocker and a workaround with a URL is possible. Sure. It's just that first creating the URL online (by manually putting all pieces of address data in) and then copying it back to TB is quite cumbersome, compared to just clicking the `Get Map` button... > We're exploring the possibility to add an integrated map inside the contact view, if the user enables it. That's super cool if and when it really happens, however, in the meantime, our users would probably be happy just to have the old `Get Maps` button back to reduce their workflow suffering from its absence... > Setting P3 for backlog as P4 is reported to be as "Do not use, this priority is for web platform test bots". :P > https://firefox-source-docs.mozilla.org/bug-mgmt/guides/priority.html Good catch! Not sure why "P4 - ...this priority is for web platform test bots" should be applicable to Thunderbird, but then, you never know and until we have agreed on a Thunderbird priority matrix which matches our release cycles, we can probably just stick to that.