[HN Gopher] Scrumdog - a program to download Jira Issues to a lo...
___________________________________________________________________
Scrumdog - a program to download Jira Issues to a local database
Author : bosveld
Score : 96 points
Date : 2022-07-15 15:58 UTC (7 hours ago)
(HTM) web link (whoek.com)
(TXT) w3m dump (whoek.com)
| ellisv wrote:
| Looks like a cool project!
| bicx wrote:
| I built a very similar tool for my company to download a set of
| DataDog logs into SQLite. Products like Jira and DataDog have
| their own query engines for sure, but you really can't beat the
| capabilities of true SQL for deeper analysis.
| mdonahoe wrote:
| link?
| bicx wrote:
| Wish I could! It's locked away in a private company repo.
| nonameiguess wrote:
| My manager a few jobs back did something like this, but just
| using Microsoft Excel with Power Query. No need to even install
| sqlite. Normally, that probably isn't much of an obstacle, but
| this was in a classified environment where it was nearly
| impossible to get the local IT admins to install additional
| software on your workstation. Every corporate Microsoft box is
| going to already have the Office suite.
| crestfallen wrote:
| I'm curious about this. I would say I'm fairly versed in Excel
| but haven't dug too deep into Power Query / the data model. If
| you wouldn't mind, how is this done?
| vorpalhex wrote:
| I liked the approach to slowly narrowing down the language choice
| based on needs. A good example of finding the right tool for the
| job.
| christophilus wrote:
| Missed naming opportunity: should have been "scrumbag".
| mnd999 wrote:
| How about Jira-is-dog-slow-and-the-interface-is-garbage-so-
| just-give-me-the-data? Not catchy enough?
|
| Presumably if you built a front end for the database you'd then
| have a not shit issue tracker.
| mxuribe wrote:
| Agreed, but i also think the -dog portion of the name likely
| refers to *fetching* of data...you know, like a dog
| fetches...well, i woud guess anyway. ;-)
| tomjakubowski wrote:
| "slumdog"
| np_tedious wrote:
| They are definitely hoping to make millions of dollars off
| this tool, and then become a...
| ananthakumaran wrote:
| I had used https://github.com/go-jira/jira in my previous job.
| custom-commands is a very useful feature. I had built a set of
| commands to filter out issues for different use cases. The
| command line approach was way faster than waiting for the jira
| page to load and click the correct set of filters.
| bbkane wrote:
| You might also try https://www.beekeeperstudio.io/ or
| https://dbgate.org/ for working with databases (SQLite and
| others). I really like the UIs of each and they're both open
| source- supported by donations if you find either useful.
| dijondreams wrote:
| This is what I need but for Mac! Any idea of alternatives? I have
| multiple Jira instances I want to combine -- literally can't find
| an app that does this.
| ellisv wrote:
| > Any alternatives?
|
| You could use Steampipe w/Jira plugin:
| https://hub.steampipe.io/plugins/turbot/jira
| bosveld wrote:
| Author here - Yes that is exactly what it does. I'll compile it
| for the Mac later today and load it on the Scrumdog.app
| website. Thanks for your comments.
| dijondreams wrote:
| Wow thank you so much!!
| nathanwallace wrote:
| Readers may also enjoy Steampipe[1], an open source [2] tool that
| uses Postgres FDW's for live SQL queries against Jira,
| Confluence, GitHub, GitLab, AWS, Slack and many more tools [3].
|
| 1 - https://steampipe.io 2 - https://github.com/turbot/steampipe
| 3 - https://hub.steampipe.io
| tomrod wrote:
| Steampipe sounds interesting (and will be looking into scrumdog
| too).
|
| Is Steampipe a community + services model, or just open source
| + community?
| adren123 wrote:
| There is also git-bug [1], an offline bug tracker fully
| embedded in git which can bridge to Github, Gitlab, Jira
|
| [1] https://github.com/MichaelMure/git-bug
| theknarf wrote:
| Why are you hosting compiled binaries on GitHub and no source
| code...
| [deleted]
| zaphar wrote:
| Jira's querying and reporting facilities leave a lot to be
| desired. I have some scripts to pull the data down into a sqlite
| database so I can query it much better.
| simonw wrote:
| Absolutely love this. I have a whole bunch of similar tools for
| importing stuff from different services into SQLite but I never
| got up the courage to take on Jira!
|
| Here's my github-to-sqlite tool which imports GitHub Issues
| https://datasette.io/tools/github-to-sqlite - being able to query
| them in a local SQLite database is super-handy. I run a demo
| instance of the resulting database here: https://github-to-
| sqlite.dogsheep.net/
| evantahler wrote:
| Just noting that you can use an EL(T) tool like Airbyte (OSS) for
| this as well! The integrations are already built - Jira -> mongo,
| Jira -> Postgres, etc.
|
| https://docs.airbyte.com/integrations/sources/jira/
| Tostino wrote:
| Yup it makes a lot of sense to use the already built tools for
| this.
| zerop wrote:
| Just to get ideas, what custom reports are users looking for that
| can not be built by Jira.
| jrockway wrote:
| I've been wanting to suck in Jira tickets to my own database so
| that I can full-text index them along with code, docs, customer
| requests, Slack, etc. Then when you're looking for information,
| you only have to go to one place.
|
| (My ulterior motive is to write a blog post that's like "how I
| used the product I make at work to index all information at the
| company". I can usually just do a linear scan across the
| backlog to find the issue I want, but hey, when marketing and
| software combine, I can't complain.)
|
| If there's some service I can buy that does this, though, I'd
| rather use that.
| SloopJon wrote:
| In my case, I find it hard to query related issues of different
| types. It's kind of hard to explain unless you see how we use
| Jira, but I basically want to do joins. You can do some
| interesting things with the Structure plugin, or
| issueFunction() from the Adaptavist ScriptRunner plugin. The
| other thing I've done is to pull a few REST queries into a
| single-page app., but that takes more work.
| standardly wrote:
| I think this is more of a way to automate pulling large amounts
| of data from Jira rather than doing it directly from a
| dashboard. Also could be utilized as a backup repository.
| zerop wrote:
| If program/project managers having coding love/passion, a lots of
| innovation could come around Jira
| Benjammer wrote:
| FYI - This type of workflow automation and connecting to Saas
| product APIs and moving data around can also be easily built
| using a no-code RPA tool like PixieBrix[0].
|
| [0] https://www.pixiebrix.com/
| digerata wrote:
| No explanation necessary. Anyone that has followed Atlassian in
| the news knows that downloading Jira Issues is an excellent idea!
| brtkdotse wrote:
| Are you suggesting they're going out of business?
| onion2k wrote:
| Apparently they've never made a profit...
| verst wrote:
| Probably a testament to performance and reliability of the
| hosted offering (we all remember the multi day outage not
| long ago).
| rozenmd wrote:
| There were zero issues with performance/reliability that
| caused the outage, they just deleted hundreds of customers
| data, and had to manually restore the data due to lack of
| automated restore scripts.
| IncRnd wrote:
| Reliability is measured from a customer's perspective,
| not from a geeky vendor-oriented perspective of a backend
| service. When the vendor deletes data, the vendor's
| reliability quotient decreases, because that data is no
| longer available to the customer.
| beckingz wrote:
| Once again we learn the hardware that accessibility is
| not the same thing as reliability.
| RexM wrote:
| Are you referring to the April outage?
|
| Technically 14 days is multi day, but when it can be
| measured in weeks, you might as well.
| IncRnd wrote:
| > Technically 14 days is multi day, but when it can be
| measured in weeks, you might as well.
|
| What does that mean? Two days is multi day. Even 25 hours
| is multi day.
| tleilaxu wrote:
| I believe they're saying that we might as well say
| "multi-week" rather than "multi-day", given that it was
| 14 days!
|
| Multi day seems to imply a time period of 2-5 days, not
| 14...
| outworlder wrote:
| Until the current crop of managers retire, Atlassian will
| still have business. Some don't know anything other than
| Jira, so will recommend it on corporate purchases.
| lloydatkinson wrote:
| Maybe someone can build a functioning UI for jira with this
| because Jira is terrible.
| zerop wrote:
| Atlassian may want to provide SQL interface to Jira data. JQL is
| limited in many ways.
| tgv wrote:
| There's an sql database backing Jira, but it looks rather ugly.
| I guess that's why they translate it.
| bokchoi wrote:
| This is my favorite limitation:
| https://jira.atlassian.com/browse/JRACLOUD-21372
___________________________________________________________________
(page generated 2022-07-15 23:01 UTC)