Plan - Bulk move paid features to Core following buyer tier model

IC PMs Review Tiers - create issues for each group to review features and propose tier adjustments. Reference the features page, our pricing model and any open public-issues suggesting tier changes in your issues.

In the issues I'd like to see a table with columns for feature name, current tier, target buyer persona, proposed action (none, tier change), and a link to any public issue suggesting the change in tier.

Buyers: IC (Individual Contributor), M (Manager), D (Director), E (Executive)

Feature Current Tier Target Buyer Persona Proposed Action Public Issues
Issues Core IC None --
Description Template Core IC None --
Task Lists Core IC None --
File Attachments Core IC None ---
Award Emoji Core IC None ---
GitLab Flavored Markdown Core IC None ---
Threaded Discussions Core IC None ---
Filterable System Activity Core IC None ---
Track File Changes Core IC None ---
Labels Core IC None ---
Prioritized Labels Core IC None ---
Scoped Labels Premium M Tier Change: Starter Why: Scoped labels will most likely evolve into custom fields of some sort. We want to take market share from JIRA and custom labels are one of the things customers have said they would need before moving away from it.
Issue Weights Starter M None ---
Milestones Core IC None ---
Issue Due Dates Core IC None ---
Assignee Core IC None ---
Multiple Issue Assignees Starter M None Related Issue
Lock Discussion Core IC None ---
Confidential Issues Core IC None ---
Related Issues Starter M None ---
Move Issue to Another Project Core IC None ---
Mark Issue As Duplicate Core IC None ---
Similar Issue Core IC None ---
New Issue via Email Core IC None ---
Bulk Edit Core IC None ---
Export Issues CSV File Starter M Tier Change: Core Why: Issue CSV import is already in core, and as an IC, I would like the flexibility to take my issues with me easily. Theoretically they can already get the issues from the API and generate a CSV so it seems reasonable to make it available in Core. I'll defer to those with more historical context as to why it is not in Core already.
Import Issues CSV File Core IC None ---
Burndown Charts Starter M None ---
Issue Analytics Premium D None ---
Quick Actions Core IC None ---
Custom Notifications Core IC None ---
To Dos Core IC None ---
Custom Text In Email Premium M None ---
Sub-addressing Email Servers Core IC None ---
Catch-all Email Mailboxes Core IC None ---
Jira Integration Core IC None ---
Jira Issues Integration Core IC None ---
Review: Jira Development Panel Integration Premium D None ---
Project Issue Board Core IC None ---
Group Issue Board Core IC None ---
Multiple Project Issue Boards Starter M None ---
Review: Multiple Group Issue Boards Premium D None ---
Total Issue Count per Issue Board List Core IC None ---
Total Issue Weight per Issue Board List Starter M None ---
Issue Board Label Lists Core IC None ---
Issue Board Assignee Lists Premium M Tier Change: Starter Why: We already allow Issue Board configuration for the Starter level. This feels like a better fit for the "Manager" buyer persona.
Issue Board Milestone Lists Premium M Tier Change: Starter Why: We already allow Issue Board configuration for the Starter level. This feels like a better fit for the "Manager" buyer persona.
Issue Board Configuration Starter M None ---
Issue Board Focus Mode Starter M None ---
Reorder Issues In Issue Board List Starter M None ---
Add Multiple Issues To Project Issue Board Core IC None Note: This only works at the Project Issue Board level.
Time Tracking Core IC None --
Track Time Spent Core IC Remove Seems like this is a duplicate of the "Time Tracking" feature
Track Time Spent Core IC Remove Seems like this is a duplicate of the "Time Tracking" feature
Multi-level epics Ultimate E Needs Strategy Discussion Related Issue, Why: Multi-level epics make sense for Ultimate, Group level epics that span multiple projects is more aligned with the Director buyer. We also don't have the concept of Project level epics, but we probably should given our competitors. Recommendation: Multi-level = Ultimate, Single Level Group = Premium, Project Level = Starter. Additionally, the roadmap view would be available for all paid levels but would have more granular feature splits (i.e. only Ultimate can expand tiered epic tree, both Premium and Epic would get progress reporting on the roadmap, etc.)
Reorder Issues In Epic Ultimate E See "Multi-level epics" thread --
Epic Fixed Dates Ultimate E See "Multi-level epics" thread --
Epic Dynamic Dates Ultimate E See "Multi-level epics" thread --
Promote Issue To Epic Ultimate E See "Multi-level epics" thread --
Roadmaps Ultimate E See "Multi-level epics" thread --
Backlog Management Premium D Remove www-gitlab-com#4939 (closed)
Risk/Issue Management Core IC Remove / ? This describes a solution, not a feature. Not sure what to do with it.
DevOps Pipeline Core IC Remove / ? This describes a capability/solution, not a feature. Not sure what to do with it.
Portfolio Planning Ultimate E Remove / ? This describes a solution, not a feature. Not sure what to do with it.
Portfolio Status Management Ultimate E Remove / ? This describes a solution, not a feature. Not sure what to do with it.
Scrum Starter IC Remove / ? This describes a solution, not a feature. Not sure what to do with it.
Kanban Starter IC Remove / ? This describes a solution, not a feature. Not sure what to do with it.
SAFe (Scaled Agile Framework) - Essential SAFe Premium E Remove / ? This describes a solution, not a feature. Not sure what to do with it.
SAFe (Scaled Agile Framework) - Lean Portfolio Management Ultimate E Remove / ? This describes a solution, not a feature. Not sure what to do with it.
Service Desk Premium D none --
Edited by Gabe Weaver