Not logged in - Log In / Register

Redirected from page "WorkItems"

Clear message

Launchpad Help > Blueprint


Blueprint is a lightweight way to manage releases of your software and to track the progress of features and ideas, from initial concept to implementation. Using Blueprint, you can encourage contributions from right across your project's community, while targeting the best ideas to future releases.

With very little administrative overhead, Blueprint helps you to create a roadmap for your project and shepherd individual features through to release.

To enable Blueprint for your project, follow the Change details link on your project overview page and select the This project uses Blueprint option.

What is a blueprint?

A blueprint is a simple specification. It describes an idea - such as a feature or process - and tracks enough metadata to show its implementation status and who's involved.

Let's take a look at what information makes up a blueprint:

Launchpad Blueprint leaves you to manage your project in the way that you want. It imposes no project management structure but instead makes it easy for you, and your project's community, to suggest, develop and implement ideas and features.

People: roles and responsibilities

We saw above that there are certain roles associated with each blueprint. Anyone can take any of these roles and anyone can set who is in any of those roles for a particular blueprint. That makes it very easy for members of your community to suggest new features and track their progress for everyone else to see, without requiring special permission.

However, to allow projects to plan future releases, Launchpad restricts who can prioritise and target blueprints and bugs. As you'd expect, the project-group and project owner have these permissions but Launchpad also allows owners to grant them to other individuals and teams. They take role that, in effect, is a release manager and that Launchpad calls the "driver".


Drivers come in three flavours:

Each driver's permission to target and prioritise trickles down the hierarchy, so, for example, project-group drivers also have driver permissions for each project within the group and each series in each of those projects.

As a project owner, you can set driver the driver of your project by

Targeting work

Launchpad Blueprint helps you to plan future release with two tools:

Although only drivers can target blueprints to milestones and set them as series goals, anyone can propose a blueprint as a series goal. As a driver or owner, you can review proposed goals by following the Set goals link on your project's Blueprint overview page.

Your project roadmap

As we saw earlier, you can tell Launchpad which other blueprints must be implemented before the blueprint you're working on.

Launchpad uses this information to recommend the order in which you might implement your project's blueprints.

Subscribing to blueprints

By following the Subscribe yourself link on a blueprint page, you can ask Launchpad to send you email notification of any changes to the blueprint. In most cases, you'll receive notification only of changes made to the blueprint itself in Launchpad and not to any further information, such as in an external wiki.

However, if the wiki software supports email change notifications, Launchpad can even notify you of changes to the wiki page.

If you're a blueprint owner and want Launchpad to know about updates to the related wiki page, ask the wiki admin how to send email notifications. Notifications should go to

Work items

As blueprints usually represent a larger chunk of work, it can be useful to break them down into smaller steps.

You can do this in the Work items text box and can keep track of the status of each of these smaller items.

Here's an example of how a set of work items might look:

[huwshimi] Design the user interaction: DONE
[huwshimi] Visual design: INPROGRESS
[danhg] Test the UI: TODO
[bigjools] Decide on an API format: POSTPONED
[matsubara] Bootstrap the dev environment: TODO
[matsubara] Set up Jenkins CI: TODO

As you can see, each work item can have an assignee and sits on its own line and you indicate its status after a colon.

Work item statuses

You can give each work item one of four statuses:


If a particular work item has a person or team who is working on it, put their name at the state of the work item line. You should use the Launchpad ID for that person or team.


Sometimes a blueprint can be targeted to one milestone but you’ll have a individual work items that need to be targeted to a different milestone. That’s fine, you can tell Launchpad that a bunch of work items are for some other milestone.

In the work items text box, simply use a header like this:

Work items for <milestone>:

If you enter an invalid milestone you’ll get an error message and the opportunity to correct the text field.


Many free software projects find that face to face meetings are a useful opportunity to make plans. They're also usually a great way to get to know your fellow project members.

Launchpad helps you plan development sprints by:

As a meeting organiser, you can download a file of all the attendees. When subscribing to a blueprint, individuals can request that they're listed as an attendee of any meeting at which that blueprint is discussed by selecting the Participation essential option.

Go see the current list of all sprints tracked in Launchpad.

Next step

Launchpad isn't just there for the planning, development, translation and bug fixing: it also helps you get your software to its users. Through your personal package archives, Launchpad will build and host

< Offering help

Personal package archives >

Blueprint (last edited 2012-03-15 17:56:07 by host86-165-134-115)