JiraCLI
github.com
github.com
Gojira is the original name of Godzilla and the name of a heavy metal band so I always have to include "github" when I search for it.
Which is also where Jira's name originates
Interesting, I would have thought "jira" was two syllables, but I know absolutely nothing about Japanese, so I assume this is correct and the pronunciation rules are just not what I'm used to from English.
It is in fact two syllables.
Fun fact: Gojira is the combination of 'Go' of 'Gorilla' and 'jira' of 'kujira' (whale). It is said, kujira comes from the combination of old Japanese 'ku' (black) and 'shira' (white) aka 'black white' after the coloration of killer whales. So at some level Jira derives from the word "white". I could probably trace back the roots for shira a bit, but I need to get some work done.
Maybe you're suffering from the usual learning curve thing where non-native speakers have trouble differentiating parts of words, because the emphasis and pronunciation simply isn't what you're used to.
Native speakers don't emphasize every syllable separately, just like you wouldn't emphasize every syllable in na-ti-ve; or how a non-native speaker like me would try to split "separate" into syllables that as se-pa-rate or se-pa-ra-te instead sep-a-rate.
(As someone who knows a couple handfuls of Japanese words, and comes from a language with somewhat similar phonemes, gojira is pronounced exactly how I expect it to be pronounced.)
Aha, okay, that's what I was thinking; I was confused by the phrasing that Wikipedia used (i.e. "the product name comes from the second syllable") and assumed that meant that "jira" was a single syllable (the second), and thought that I might be missing something about how the pronunciation works. It sounds like I was just misreading the Wikipedia quote though, so thanks for bearing with my confusion and explaining it!
The bit I struggled with a bit was the template system, but once you have your templates set up you don't have to touch them again (unless things change on the Jira side). There's a section in the README about working with templates.
I set up some aliases to make things easier too, for example to see what needs to be worked on I have an alias 'sprint' for:
jira ls -q "sprint='$JIRA_SPRINT' and status in ('In Progress', 'Peer Review', 'To Do')" | sort -k 2
Jira not so much.
Certain places do, actually. That's why lots of enterprise software was stuck having to support IE just a few years back (and probably still in some places that haven't caught up).
I've seen demands towards certain features working on Edge/Chrome in particular even if it would break something in Firefox, which might be preference of the end users but also corporate policy towards using known software in certain places.
I'm sure that you're still likely to run into plenty of environments where something like Edge might be the only allowed browser.
Yep, and talking about Jira, they only ended that support in March 2020.
And wow, according to Wikipedia, Microsoft still supports Internet Explorer on some non-consumer Windows flavors. Today. I find that actually pretty stunning, must be a huge liability to be running web-apps that breaks on non-IE, because that can't then be the only aspect at which it's still stuck in the stone ages.
(Nothing against ankitpokhrel and this great tool, just making a point in a slightly sarcastic way)
I have done that multiple times. It's not very time demanding, because the working code is there, and all you're doing is essentially deleting code you either don't understand, or don't need. At the same time, you're reading the code you do use.
I am the customer of our IT, I don't know why it should be any other way. It's noteworthy though that I don't work in a tightly regulated sector.
You may also be able to get 3rd party insurance for this.
They only enforce it if you run windows, though.
All software, including open source, technically needs to get approved by a security team.
If you do use this against policy, what are they gonna do? Fire you? For using a jira client? Realistically they'll just say "don't use that", and you can counter by saying "OK, then pay for the other CLI on Marketplace." There is no official client for Jira so you either use this tool, or the paid 3rd party one. I'm sure they'd rather use the free one.
It's up to IT to monitor, detect and ban any user for inappropriate JIRA use. If you're banned it must have been justified by historical misuse. Sorry for you.
TUIs like GoJira and JIRACLI makes the cut for me.
I would like to play with this as I love terminal apps, but connecting a third party app to my Orgs Jira is a concern.
Would be cool if this was adopted by Atlassian.
Each task is a yaml file and hooked up to your text editor is a language server that can talk to Jira and do autocomplete against @username, Jira ticket ids, etc.
Sync on save.
I’m sure there’ll be all sorts of problems I haven’t forseen, but one can dream of editing task as quickly as editing your personal markdown notes.
even without jira, just something like hugo generate a static site to show others the backlog.
also this for confluence.
perhaps I'm just getting old, but I'm wanting more and more of my work to just be text files (markdown/yaml/whatever is appropriate) and tracked in a git repo.
No idea if this still works, but this project exists: https://github.com/MaZderMind/jirafs
It uses this, which is maintained, for talking to JIRA, so maybe: https://github.com/andygrunwald/go-jira
I am preparing a roadmap for v2 where I implement a lot of reliability features, like context support, but also separate APIs for OnPremise and Cloud and easier access for custom fields.
Watch the github repo if you want to stay up to date.
Concurrent edits will ruin your day.
As others in this thread have alluded to -- corporate security policies can, right or wrong, bring down the banhammer on these types of tools, which can be doubleplusfrustrating given the native features are so user-hostile.
It was some PTSD inducing work and I couldn't put up with it any longer so I wrote a CLI utility in python where I'd track my work throughout the day, a simple one-liner of the work I did with some hashtags for routing to the right project/client. At the end of the day I would "process" my entries by typing one command which ran chrome+selenium automation to do the work for me. [edit] From memory, API use wasn't allowed which is why I had to take this route - it was also a great conversation starter for anyone passing by while it ran.
I saved a tonne of time and aggravation, others noticed, so I set them up with the same. A nice byproduct of this: all the entries were also kept in a local sqlite database which allowed you to quickly search and find answers for follow-ups without touching JIRA, all with a few characters in the terminal.
Edit: I wanted to say I definitely gained some inspiration by looking at yours.
JiraCLI seems to spend most of its code budget translating in between CLI args and JQL; that's the easy part.
Because every org uses Jira differently, it seems hard to write a generic tool that works well with your org.
This lib is maintained, still a bit out of date and has a few flaws. Like using the same client for JIRA Cloud and JIRA OnPremise (different APIs). But most of the flaws have been evolved over time, while Atlassian switched strategies.
I am preparing a roadmap for v2 where I implement a lot of reliability features, like context support, but also separate APIs for OnPremise and Cloud and easier access for custom fields.
Watch the github repo if you want to stay up to date.
My original curl commands: https://gist.github.com/TheMightyLlama/9427202
A TUI always feels like terminal fetishism to me.
Part of the reason a lot of work is never logged anywhere is because the tools are way too slow/cumbersome to be pleasant to use by users and this is a problem for every corp.
It is not solving the same problem but back when we were working more with pets than cattles I worked for a company that had a nice tool installed on every solaris and linux machines, it allowed you by a single command to say exactly what you were about to do or what you had already done and why. Everything ended up in a remote database with a simple but efficient dashboard allowing you to know the history of every server. I think you could also attach the output of the script command. Adoption was great because it was quick and easy to do. I wish I could remember the name, I wouldn't use that at work anymore but for personal log and homelab it would be nice. I guess nowadays I could just do that using logger or create a shell function that send a json to an elasticsearch or solr instance for easy indexation.
So I can do `rm -rf / | jiracli`