Bug 42542 – Reflect rebranding to "G Suite" in app

Bug 42542 - Reflect rebranding to "G Suite" in app


Summary:	Reflect rebranding to "G Suite" in app

Status:	RESOLVED DUPLICATE of bug 47680

Product:	UCS
Classification:	Unclassified
Component:	Google Apps for Work
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Mail maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-30 11:07 CEST by Erik Damrose
Modified:	2019-02-01 10:36 CET (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Erik Damrose

2016-09-30 11:07:53 CEST

Google rebranded "Google Apps for Work" to "G Suite"

https://gsuite.google.com
https://cloud.googleblog.com/2016/09/all-together-now-introducing-G-Suite.html

Our connector app should be adapted and use the new name.

Comment 1 Stefan Gohmann

2019-01-03 07:17:51 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.

Comment 2 Erik Damrose

2019-02-01 10:36:33 CET


*** This bug has been marked as a duplicate of bug 47680 ***