[{"data":1,"prerenderedAt":74},["ShallowReactive",2],{"help-article-status-rollups":3},{"data":4},{"title":5,"excerpt":6,"content":7,"help_category":8,"seo":11},"Status Rollups","Read the colored bar in a PD table row: how status rolls up from attribute to model to feature to solution as a distribution, and how to click through.","\u003Cp>\u003Cstrong>What you'll learn\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>What the little colored bar in a PD table row actually shows.\u003C\u002Fli>\n\u003Cli>How status rolls up from leaf to root: attribute → model → feature → solution.\u003C\u002Fli>\n\u003Cli>How to read the distribution and click through to the children behind it.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>This builds on \u003Ca href=\"\u002Fhelp\u002Fthe-product-development-concept\">The Product Development Concept\u003C\u002Fa> and \u003Ca href=\"\u002Fhelp\u002Fyour-first-solution\">Your First Solution\u003C\u002Fa>.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>What a rollup is\u003C\u002Fh2>\n\u003Cp>Every layer of the PD tree owns children: a Solution owns Features, a Feature owns Models, a Model owns Attributes (and Controllers, and Events). A \u003Cstrong>status rollup\u003C\u002Fstrong> is how a parent row summarizes the statuses of its children so you can see how far along a branch is without opening every child.\u003C\u002Fp>\n\u003Cp>In the table, a rollup shows up as a small horizontal bar with a count next to it — for example, a "Models" column on a Feature row, or an "Attributes" column on a Model row. The bar is divided into equal segments, one segment per child, each colored by that child's status. The number in parentheses is how many children there are.\u003C\u002Fp>\n\u003Cp>So a Feature with five Models shows a five-segment bar. If four segments are the color of a "done"-tier status and one is the color of an early status, you can see at a glance that the Feature is mostly built but not finished — without reading a single Model.\u003C\u002Fp>\n\u003Cp>The rollup is a \u003Cem>distribution\u003C\u002Fem>, not a single computed grade. m18t doesn't collapse the children into one number or auto-set the parent's own status from them. It shows you the spread and lets you draw the conclusion. (The parent row also has its own status, which you set directly — that's separate from the rollup bar.)\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>The chain, leaf to root\u003C\u002Fh2>\n\u003Cp>The same mechanism repeats at each level, so status effectively rolls up the whole tree:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>An \u003Cstrong>Attribute's\u003C\u002Fstrong> status is a leaf — you set it directly.\u003C\u002Fli>\n\u003Cli>A \u003Cstrong>Model\u003C\u002Fstrong> shows the distribution of its Attributes (and its Controllers and Events).\u003C\u002Fli>\n\u003Cli>A \u003Cstrong>Feature\u003C\u002Fstrong> shows the distribution of its Models.\u003C\u002Fli>\n\u003Cli>A \u003Cstrong>Solution\u003C\u002Fstrong> shows the distribution of its Features and Models.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Read top-down, a Solution row tells you how its Features are spread; click into a Feature and you see how its Models are spread; click into a Model and you see its Attributes. Each level is one bar summarizing the level below.\u003C\u002Fp>\n\u003Cp>Statuses come from the shared \u003Ca href=\"\u002Fhelp\u002Fthe-status-set\">status set\u003C\u002Fa> — the same opinionated vocabulary used across content and the rest of the workspace, with each status carrying a fixed color. That's why the segment colors are consistent everywhere you see a rollup.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>How to read one\u003C\u002Fh2>\n\u003Col>\n\u003Cli>Open \u003Cstrong>Product Manager\u003C\u002Fstrong> (\u003Ccode>\u002Fstudio\u002Fproduct-development\u003C\u002Fcode>) and pick an entity tab — say, \u003Cstrong>Features\u003C\u002Fstrong>.\u003C\u002Fli>\n\u003Cli>Find the rollup column (e.g. "Models"). Each row shows a segmented bar and a count.\u003C\u002Fli>\n\u003Cli>Hover the bar. A popover lists every child by name and slug, colored by status.\u003C\u002Fli>\n\u003Cli>Click any child in that popover to jump straight to it.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The count in parentheses also flags empty branches: a \u003Ccode>(0)\u003C\u002Fcode> bar means the parent has no children of that type yet.\u003C\u002Fp>\n\u003Chr>\n\u003Ch2>Variations\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Empty rollups are information.\u003C\u002Fstrong> A Feature showing \u003Ccode>(0)\u003C\u002Fcode> Models hasn't been broken down yet — that's a gap worth noticing, not a bug.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>One bad segment stands out.\u003C\u002Fstrong> Because every child gets an equal slice, a single early-status child in an otherwise-finished branch is visible immediately.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>The graph view is the same data, drawn differently.\u003C\u002Fstrong> If you'd rather see the whole tree at once than scan rows, the \u003Ca href=\"\u002Fhelp\u002Fthe-dependency-graph\">dependency graph\u003C\u002Fa> renders the same status colors across the entire structure.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Chr>\n\u003Ch2>FAQ\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Does finishing all the children automatically mark the parent as done?\u003C\u002Fstrong>\nNo. The rollup shows the distribution of children; it does not change the parent's own status. You set a parent's status yourself. Status transitions aren't enforced as a workflow today, either — see \u003Ca href=\"\u002Fhelp\u002Fthe-status-set\">The Status Set\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Why are all the segments the same width?\u003C\u002Fstrong>\nEach child gets an equal slice regardless of size or importance. The bar is a count-weighted distribution of statuses, not a progress percentage.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>What does the number in parentheses mean?\u003C\u002Fstrong>\nIt's the number of children rolled into that bar. \u003Ccode>(5)\u003C\u002Fcode> means five Models (or Attributes, etc.); \u003Ccode>(0)\u003C\u002Fcode> means none yet.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Can I click through to a specific child?\u003C\u002Fstrong>\nYes. Hover the bar to open the list, then click any child to navigate to it.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Where do the colors come from?\u003C\u002Fstrong>\nFrom the shared \u003Ca href=\"\u002Fhelp\u002Fthe-status-set\">status set\u003C\u002Fa>. Each status has a fixed color used consistently across the workspace.\u003C\u002Fp>\n\u003Chr>\n\u003Cp>\u003Cstrong>What's next\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-status-set\">The Status Set\u003C\u002Fa> — the shared vocabulary behind the colors.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fthe-dependency-graph\">The Dependency Graph\u003C\u002Fa> — the same status data across the whole tree.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fyour-first-solution\">Your First Solution\u003C\u002Fa> — build the structure the rollups summarize.\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"\u002Fhelp\u002Fattaching-artifacts\">Attaching Artifacts\u003C\u002Fa> — note \u003Cem>why\u003C\u002Fem> a branch is stuck where it is.\u003C\u002Fli>\n\u003C\u002Ful>\n",{"slug":9,"title":10},"product-manager","Product Manager (PD)",{"meta_title":12,"meta_description":6,"keywords":13,"canonical_url":14,"og_title":12,"og_description":6,"og_image":15,"robots":16,"json_ld":17},"Status Rollups | m18t Help","status rollups, status distribution, PD table, progress bar, leaf to root, status set, product manager, m18t","https:\u002F\u002Fm18t.com\u002Fhelp\u002Fstatus-rollups","https:\u002F\u002Fm18t.com\u002Fog-default.png","index, follow",{"@context":18,"@graph":19},"https:\u002F\u002Fschema.org",[20,33,58],{"@type":21,"headline":5,"description":6,"articleSection":10,"inLanguage":22,"datePublished":23,"dateModified":23,"image":15,"author":24,"publisher":28,"mainEntityOfPage":31},"Article","en","2026-06-25",{"@type":25,"name":26,"url":27},"Organization","m18t","https:\u002F\u002Fm18t.com",{"@type":25,"name":26,"url":27,"logo":29},{"@type":30,"url":15},"ImageObject",{"@type":32,"@id":14},"WebPage",{"@type":34,"mainEntity":35},"FAQPage",[36,42,46,50,54],{"@type":37,"name":38,"acceptedAnswer":39},"Question","Does finishing all the children automatically mark the parent as done?",{"@type":40,"text":41},"Answer","No. The rollup shows the distribution of children; it does not change the parent's own status. You set a parent's status yourself. Status transitions aren't enforced as a workflow today, either.",{"@type":37,"name":43,"acceptedAnswer":44},"Why are all the segments the same width?",{"@type":40,"text":45},"Each child gets an equal slice regardless of size or importance. The bar is a count-weighted distribution of statuses, not a progress percentage.",{"@type":37,"name":47,"acceptedAnswer":48},"What does the number in parentheses mean?",{"@type":40,"text":49},"It's the number of children rolled into that bar. (5) means five Models (or Attributes, etc.); (0) means none yet.",{"@type":37,"name":51,"acceptedAnswer":52},"Can I click through to a specific child?",{"@type":40,"text":53},"Yes. Hover the bar to open the list, then click any child to navigate to it.",{"@type":37,"name":55,"acceptedAnswer":56},"Where do the colors come from?",{"@type":40,"text":57},"From the shared status set. Each status has a fixed color used consistently across the workspace.",{"@type":59,"itemListElement":60},"BreadcrumbList",[61,65,69,72],{"@type":62,"position":63,"name":64,"item":27},"ListItem",1,"Home",{"@type":62,"position":66,"name":67,"item":68},2,"Help","https:\u002F\u002Fm18t.com\u002Fhelp",{"@type":62,"position":70,"name":10,"item":71},3,"https:\u002F\u002Fm18t.com\u002Fhelp\u002Fcategories\u002Fproduct-manager",{"@type":62,"position":73,"name":5,"item":14},4,1786312171742]