Promote burndown charts
Related to https://gitlab.com/gitlab-org/gitlab-ee/issues/2624
Design
Promote trial or license activation for regular EE on-prem sites.
Admin
- Having
Start GitLab Enterprise Edition trialbutton. Read more
- Link to the document, so users can know more about the feature.
- Link: https://docs.gitlab.com/ee/user/project/milestones/burndown_charts.html
- Copy:
Improve milestone with Burndown Charts.
Burndown Charts are visual representations of the progress of completing a milestone.
At a glance, you see the current state for the completion a given milestone.
Without them, you would have to organize the data from the milestone and
plot it yourself to have the same sense of progress. [Read more]Non-admin
- Copy:
Improve milestone with Burndown Charts.
{{ Same as the admin copy for regular EE on-prem sites }}| Admin | Non-admin |
|---|---|
 |
 |
For GitLab.com the feature promotion needs to go to purchase a GitLab.com plan
Admin
- Having
Upgrade your planbutton. - Copy:
Upgrade your plan to improve milestone with Burndown Charts.
{{ Same as the admin copy for regular EE on-prem sites }}
Non-admin
- Copy:
Upgrade your plan to improve milestone with Burndown Charts.
{{ Same as the admin copy for regular EE on-prem sites }}| Admin | Non-admin |
|---|---|
 |
 |
Activity
mentioned in issue #2624 (closed)
@hazelyang I think this one is much too big.
I think we should just display a smaller height banner in the place where the burndown chart should go.
We shouldn't cover the whole page with a promotion, I think it's too in your face.
-
cc @victorwu
@hazelyang : Agree with @mydigitalself . I think as a design rule, at least for GitLab, I don't think we should introduce any additional clicks for users to access their existing content. I think it's okay to put some marketing banners. But that doesn't entirely cover the existing functionality.
@hazelyang: I like your images. What do you think about expanding on that concept and actually make a realistic-looking burndown chart instead? So you would have some static image of a burndown chart, probably slightly smaller than a real one. And it's probably grey-ed out a bit. And there's some messaging to say something like this is what you get if you upgrade.
@hazelyang: Related, if you look at this design on Glassdoor, it seems to imply it is hiding content. To me that's a crappy experience. What do you think? I think a better experience is showing a fake but representative UI of what you do not see (i.e. a static burndown chart). But we are not hiding something real. It's a delicate difference. Thoughts?
-
@victorwu I'm afraid I don't quite agree. If it's not obscured, then people may think it's real and then you have to explain to them it's not real.
In this case, I don't think we should show the burndown chart at all and just put a smaller visual banner similar to the below above the issue board where the burndown chart would go. The icon can be a representation of a burndown chart, which I think many people will recognise.
No problem @mydigitalself . Just some general thoughts from me. I'll let you and @hazelyang agree on the final designs.
@victorwu @mydigitalself Thanks for your feedback and ideas!
Updated the designs:
- Put a banner on the position that the burndown chart displays on GitLab EE.
- Modified the heading and button wording as @mydigitalself mentioned on #2918 (closed).
For regular EE on-prem sites
Admin Non-admin 
For GitLab.com
Admin Non-admin 
@hazelyang : For this issue (and the other ones), you've written "for regular EE on-prem sites". I just want to confirm that we are doing these for both CE and EES installs and GitLab.com at the Free, Bronze, and Silver tiers. Basically as long as the user is at a tier that does not have the feature, then include the promotion UI. @mydigitalself : Can you confirm?
Just wanted to be clear so that perhaps we can update the descriptions to be more clear/explicit. Thanks!
@mydigitalself @hazelyang : The latest design (https://gitlab.com/gitlab-org/gitlab-ee/issues/2966#note_36141293) looks great to me.
@mydigitalself : You want me to have a stab at the text copy? Or did you want to do it / have something else in mind?
@mydigitalself @victorwu I updated the mockups in the description. Please feel free to edit the copy text if you have good ideas for it. Thanks!
changed milestone to %10.0
mentioned in merge request !2540 (merged)
closed via merge request !2540 (merged)
mentioned in commit 83408f08
