Register a Blueprint button should appear on /~team-name

Bug #120582 reported by Matthew Revell
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

On a team's Blueprint page - e.g. https://blueprint.launchpad.net/~launchpad-tech-writers/ - the "Register a blueprint" button should be displayed.

It seems strange not to be able to register a blueprint from this page.

Changed in blueprint:
status: New → Confirmed
Jonathan Knowles (jsk)
Changed in blueprint:
assignee: nobody → jsk
Revision history for this message
Christian Reis (kiko) wrote :

Why does it seem strange? You can't register a bug or a question from a team's bug or answers page either. I'd like Matthew's opinion here.

Revision history for this message
Matthew Revell (matthew.revell) wrote :

When I use the Blueprint pages in a team/person context, I see the Blueprint colour and URL and so think that I am using Blueprint. There's no obvious way to move further up into generic Blueprint pages. Even the Home drop-down doesn't offer me that.

So, if there's no way on that page to register a blueprint, I feel stuck. I can't easily navigate to a page that lets me register a blueprint.

Revision history for this message
Matthew Paul Thomas (mpt) wrote :

I agree with Matthew R. To be precise, I suggest:
* On a person's Blueprints page, there should be a "Register a blueprint" button that takes you to <https://blueprints.launchpad.net/specs/+new?assignee=thatperson>. This should be identical to <https://blueprints.launchpad.net/specs/+new>, but with the assignee field pre-filled.
* On a team's Blueprints page, there should also be a "Register a blueprint" button, but it should just take you to <https://blueprints.launchpad.net/specs/+new>. (It makes little sense for a blueprint to be assigned to a team.)

Revision history for this message
Jonathan Knowles (jsk) wrote :

Assigning to low as per discussion with BjornT.

Changed in blueprint:
importance: Undecided → Low
Jonathan Knowles (jsk)
Changed in blueprint:
status: Confirmed → In Progress
Revision history for this message
Jonathan Knowles (jsk) wrote :

Shifting to 1.1.10.
Have a working branch that is almost ready for review.

Jonathan Knowles (jsk)
Changed in blueprint:
milestone: 1.1.10 → 1.1.11
Jonathan Knowles (jsk)
Changed in blueprint:
milestone: 1.1.11 → 1.1.12
status: In Progress → Confirmed
Changed in blueprint:
assignee: jsk → intellectronica
milestone: 1.1.12 → 1.2.1
Revision history for this message
Eleanor Berger (intellectronica) wrote :

untargetting until after 2.0

Changed in blueprint:
milestone: 1.2.1 → none
Revision history for this message
Dustin Kirkland  (kirkland) wrote :

From a user experience, I started on my own page showing my blueprints, and from there I expected to be able to kick off a new blueprint. I think a "Register New Blueprint" button would be very nice here, from a flow perspective.

Thanks,
:-Dustin

Curtis Hovey (sinzui)
Changed in blueprint:
assignee: Tom Berger (intellectronica) → nobody
tags: added: registry-people
removed: fix-it-friday
Curtis Hovey (sinzui)
tags: added: teams
removed: registry-people
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.