ober / gerbil-jira Goto Github PK

Proposal:

At least initially, the tool does not provide the full set of functionality currently provided in the user interface. If I want to upload/view photos, better format comments, etc, sometimes I just want to pop open the issue in a browser. Would be nice to have something like:

jira open <issue>

I am noticing that when I add a comment, if I include special characters, it usually fails.

Example:

jira comment "I will be in the office by 9 AM tomorrow. Thanks!"
-bash: !": event not found
^^

If I put things in single ticks, things appear to be ok, but I guess this was just somewhat unexpected behavior.

Proposal:

Would be nice to color block different sections of an issue to make viewing an issue and comments more easy.

Proposal:
Unless you have transition ids and flow memorized, you are forced to do the following:

1. jira transitions
2. Pick from list, jira transition
3. jira transitions
4. Pick from new list, jira transition

This flow is common if you go from Open->In Progress->Resolved->Closed

The proposal is to provide this workflow as a single command:

1. jira transition
2. Lists ids, type which one
3. Keep transitioning? If yes, show list, type which one
4. Stop when done transitions.

Proposal:

Currently in ~/.jira.yml, you can specify a set of pre-defined queries. However, I have found that it would be nice to have some base queries I would like build onto. Below is an example:

.jira.yml
myopen: "assignee = currentUser() AND status != Closed"

command
jira q myopen "AND PROJECT = DEMO"

I am finding it hard to know when something was successful or not when run.

Example: Transition success?

jbragg$ jira transitions <issue> 11

jbragg$

Example: Assign success?

jbragg$ jira assign <issue> jbragg

#!void
jbragg$