Back to issue list Export

The CLI interface is very utilitarian. It's more suitable to scripting than being used by human beings. This should be fixed. Likely what is needed is a suite of commands meant for humans and then a separate command which is meant to be used by scripts and would thus have various querying options.

travisb 2013-08-13 20:54:20
hash: e4665c8198191b277cd5a666dc6e013c621959911201c7082d6d67998314ae1a
Date: 2013-08-13 20:54:20
User: travisb

I've been using a CLI based bug tracking extension to Bugzilla for the past few months and the experience has led me to believe that what is needed is really two levels of interface as part of the CLI. First there needs to be a way to perform complex bug changes in a single command line. This means taking a bug as a parameter and then a series of options on what actions to perform on that bug. Things like writing a comment using the editor, and changing the state and changing the owner. This is the nitpick <options> bugid CLI. Beside that there need to be simple commands for the common cases. Such common cases include: a user claiming a bug, commenting on a bug, listing the bugs, viewing a bug. This is a CLI interface more inline with the interface as it stands.


Tracked by Nitpick