Clojurians Log v2

Wanted to check with folks and see whether the "top voted ticket" reports are useful to anyone any longer, e.g. here: https://jafingerhut.github.io/clj-ticket-status/clojure-ticket-info.html I think you can get the "top unweighted" ticket reports with appropriate JIRA queries, and I believe that the reports of weighted vs. unweighted usually look pretty similar. That is, the fears that many people would vote on too many tickets and skew the results somehow seems not to have happened.

If the "unweighted" top voted ticket reports that can be generated automatically from JIRA queries are sufficient, I can put links to those on that page, for anyone that does go there.

I still look at them but I agree that they are not substantially more interesting than the jira equivalents

Do you have handy links to a published JIRA query that shows "all not-{closed or declined or resolved} CLJ tickets"?

I see saved & published JIRA queries for several subcategories, e.g. prescreened, vetted, open, etc. but not the union of all of them lumped together.

I guess I could create and publish one, but leave "CLJ" out of the name, as you have requested before for such published queries.

Hmm. I can create new private JIRA query and save it, but I either don't have permission to make it public to all JIRA users, or just don't see the right button or option to make that happen.

I have some saved queries for by vote already

I have it set so no one can make saved queries but me

Sorry, shared queries

Anyhow, no point in doing this now as I’m working on migrating out of this jira

Making a new one and migrating the votes and tickets?

I am pretty sure Alex wants to ensure all of the existing tickets, comments, attachments, and votes are preserved during the migration.

That's great. Hadn't seen anything about the jira migration yet, despite my unhealthy obsession with slack.

It is a small part of this weekly article by Alex: http://insideclojure.org/2019/04/28/journal/

I read that as updating the first time for some reason. :)

I've written some migration stuff for jira cloud that should preserve all of that. still working through licensing issues.