mikepea / go-jira-ui Goto Github PK

Editing tickets is hopefully pretty straightforward.

Use 'e' from TicketList and TicketShow to edit the selected issue.

Termui.v2 fails to build when running go get -v github.com/mikepea/go-jira-ui/jira-ui. I have tested on both my Mac and in a Docker container.

Running the following to attempt to build go-jira-ui in a Docker container as a test environment.

❯ docker run -it --rm golang:alpine ash

/go # go get -v github.com/mikepea/go-jira-ui/jira-ui
...
gopkg.in/gizak/termui.v2
# gopkg.in/gizak/termui.v2
src/gopkg.in/gizak/termui.v2/render.go:107:15: undefined: stack.ParseDump
src/gopkg.in/gizak/termui.v2/render.go:112:15: undefined: stack.Aggregate

/go # go version
go version go1.15.2 linux/amd64

Looking into the issues on the gizak/termui repository that seem to be relevant most of the solutions seem to be to upgrade to the latest version of Termui.

Any help/suggestions would be appreciated! I'm gonna attempt to figure out how to fix this myself later today but thought I would post this here in case anyone has suggestions. Will update with a fix/pull request if I figure out how to fix.

I'm missing a way to updated status of a ticket directly from go-jira-ui, unless I am missing something. Perhaps command :status could be added to change a ticket when viewing it?

Paging is weak in TicketShowPage, largely due to 'wrap' mode in the termui.List element. There doesn't appear to be a way of finding this out.

Options:

• Submit a PR to termui to get this support in place. It should be feasible and handy.
• Work around it, by calculating the wrapping (bletch, but feasible)
• Use our own wrapping (meh, but would mean we could split lines more intelligently, and would help make #4 more useful)

Sometimes you want to look at tickets from a create date perspective, sometimes by last update.

We should support useful sort orderings, as per the JIRA UI.

Doing the API query to ensure the TIcketList page has up-to-date results is expensive, and makes the interface somewhat sluggish.

Instead, if we kept the cachedResults and had a 'refresh' option, we can work around this in an acceptable way.

'R' for refresh results.

Jira supports Kanban boards. It would be nice if go-jira-ui supported viewing and interacting with them. At a minimum, being able to view a board would be nice. Ideally, you would also be able to easily preview an issue and move it to a different column.

I thought I would be able to page up and down.

The TicketShow page comes from the results of a query in TicketList. There is value in being able to step through tickets in this list, without the cost of going back to the TicketList page.

Use 'n' and 'p' keys for this.

This is an example of a class of problems.

      "VpnGateways":

... becomes

 [      "VpnGateways": [](fg-white,bg-blue)

when highlighted.

Something is screwy, but it's not obvious what from the above. Fix it!

Atlassian cloud based installs require an API token instead of username/password, as described in the jira-ui docs here.

When I use the jira CLI tool, I supply this token with the JIRA_API_TOKEN environment variable, but for jira-ui there doesn't seem to be a way to supply this token.

If you paste text into the command buffer, (eg view {paste-ticket-id}), it gets mangled.

There's nothing in the way of buffering, w/r/t Key events, so this is kind of expected.

It needs fixing though, not sure how as yet.

I get:

$ export GOPATH=$HOME/go
$ export GOBIN=$GOPATH/bin
$ mkdir -p $GOPATH
$ export PATH=$PATH:$GOBIN
$ go get -v github.com/mikepea/go-jira-ui/jira-ui
github.com/mikepea/go-jira-ui
# github.com/mikepea/go-jira-ui
go/src/github.com/mikepea/go-jira-ui/ui_controls.go:170:10: e.Data undefined (type termui.Event has no field or method Data)
go/src/github.com/mikepea/go-jira-ui/ui_controls.go:269:10: e.Data undefined (type termui.Event has no field or method Data)

System details:

macOS 10.14.1 running Go version go1.11.2 darwin/amd64.

Am I missing anything?

Thanks!

I open jira-ui, select a query, use down-arrow to select an issue, enter to view issue. Then "E" to edit the issue, I see edit screen, make a change and exit out of edit and back to viewing issue. At this point navigation is dead, I cannot "q" back to the query results, and "P" and "N" do not go away from issue. In fact it seems like no keys work, include C-c q, so I cannot even exit. The only way to get back to console is it open another console and kill the process. No idea what the root cause of this is.

I cannot type Vietnamese language in command section
Example: When i type :comment Không thể làm được gì cả it display :comment Khng t lm duoc g c

On a per-ticket basis, provide a select-box (a'la sort order) that will let the user select an available transition, like 'In Progress', or 'Done'.

Some care is needed here - how would we set the close 'resolution' for example.

What you think about passwordeval option in config. file? It would allow user to read password from keychain or tools like that - without putting them in config file in plain text.

I'd like my custom queries to be at the top of the page and I'm not gonna use the default ones now that I defined mine. Adding an option to disable default queries would be great :)

I've been wondering how this would materialise, as there is no graceful handling of this condition - when a re-login to JIRA is needed, CmdLogin will potentially trigger.

It's just happened, and 'Password: ' prompt was displayed. I typed my password, it was accepted and the token refreshed. I'm sort of amazed this worked. However, I doubt it will in every situation, and obvs not a solution.

Really this involves figuring out how to do this in-interface.

As per #2 -- implement commenting.

This will fall foul of #8, but that's ok for now. Commenting is pretty essential.

I'm not sure why yet, but I can't seem to get go-jira editor operations (eg 'edit', 'comment') to return successfully to the termui interface.

A workaround is to simply exit after the operation, which is awful but better than hanging the UI.

Logging this ticket to track progress on fixing it.

We can select lines in TicketShow, we may as well utilise it.

If an issue ID appears on that line (so of the form [A-Z]+-[0-9]+), do TicketShow on that issue ID.

Seriously, no-one will read the README.

'h', as per every ncurses interface in the world, ever.

Using the default installation steps I am getting the following error on OSX Sierra using homebrew golang 1.7.5

$ go get -v github.com/mikepea/go-jira-ui/jira-ui
github.com/mikepea/go-jira-ui
# github.com/mikepea/go-jira-ui
../base_list_page.go:100: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../base_list_page.go:101: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../base_list_page.go:114: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../base_list_page.go:115: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar.go:26: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar.go:31: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar_fragment.go:20: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar_fragment.go:26: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar_fragment.go:32: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar_fragment.go:48: log.Debugf undefined (type *logging.Logger has no field or method Debugf)
../command_bar_fragment.go:48: too many errors

Issue #26 was resolved by shifting default queries down instead of allowing to disable them. This is fine in my mind, however in my use-case the default queries are not valid and therefore even less useful as they are by default.

My suggestion is therefore to implement a way of editing the default queries. Would this be possible? :)

I was surprised when my queries, uh, "filters", from Jira didn't show up. It would be helpful to be able to export those (the filter definitions are available via API).

We need to find ticket IDs in plaintext, for a couple of reasons:

• It means we can do the drill-down from the TicketShow page, where ticket IDs are in the comments, blockers, ... fields
• The TicketList page currently works on a template, so we actually pull the ticketID out from the raw string.

@Feriority found this in #23 -- https://confluence.atlassian.com/jira/changing-the-project-key-format-192534.html -- which indicates that we need to perform a better match.

Also, it's probably worth adding some logic to the TicketList page to pull the ticket IDs out via the API response, rather than via findTicketIdInString(). More robust, innit.

Go-jira has the ability to issue the command :browse to open a ticket in the browser. I would love to see this possible also in go-jira-ui. Would this be possible? Thanks!

After entering edit mode by pressing E and exiting it, arrows no longer work for navigation (while j and k still work as before).

Command history is not preserved across pages, only saves one command, and invalid commands are kept.

Update it to:

• Maintain state across pages
• Include a proper history
• Keep a ':' and 'search' list

It's never going to be ideal shelling out to $EDITOR even if we fix #8

Implement a termui page for adding/editing a comment.

Instead of displaying dates like "2016-01-04T11:15:42.000+0000" it would be nice to be able to see them as 10 days ago/3 hours ago.

I am already working on a patch for this 👍

Once we have text input box support, this should be a no-brainer.

Should be reasonably straightforward, and removes another reason to drop to the web UI or edit-and-quit.

It'd be pretty easy to reverse, and this makes dealing with older tickets easier.

We're effectively replacing less, so let's add its killer feature.

The JIRA API does report the tasks within an Epic in the API request for that ticket. It's possible to do this via a query though.

Allow for drilling into an Epic ticket in a way that presents the user with the list of those tickets. Unresolved is probably ok, for brevity.

Old:

cat ~/jira.d/jira-ui-config.yml:

New:

cat ~/.jira.d/jira-ui-config.yml:

need to add pointer before jira.d

./jira-ui --endoint=https://jira.yelpcorp.com

2016/01/27 09:48:39 Unknown option: --endoint=https://jira.yelpcorp.com
....
General Options:
-e --endpoint=URI URI to use for jira

This would be a really useful cli command, so I could filter out the ticket ID in a mutt keybinf and add myself as a watcher.. without a browser window.