Workflow Specific Interfaces for Bazaar Explorer

Registered by Dr Al on 2009-11-10

Extend the "Hats" feature such that the way people work (using checkouts rather than branches, using feature branches, pushing to launchpad etc) significantly customises the user interface to make it easier to do the operations that are required every day: why have a branch button when you always checkout? Why have a lightweight checkout option when you always use full checkouts? Why have all the options in the Initialise dialog box when you only ever create one type of repository?

Blueprint information

Status:
Not started
Approver:
None
Priority:
Medium
Drafter:
None
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Not started
Milestone target:
None

Related branches

Sprints

Whiteboard

Definitely +1 for this! I would love to have the inapplicable buttons just fade away and have the UI focus on what I do.

I also recommend being able to set this with different granularities (i.e., per-user defaults, per-project, per-branch, etc.)

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.