Fork me on GitHub

in the new JIRA world, where do things happen once the support request is accepted, is the rest of the process visible or only between core members?


We are also looking at a new process to obtain a contributor account and gain access to the system for commenting or other work. Stay tuned for more on that.''


ok, found my answer

Alex Miller (Clojure team)12:05:35

Tickets are still publicly visible regardless


I'm not finding where though at the moment

pyr12:05:13 lands me on the home for the support requests and doing requests -> all shows me no output


direct links to an existing CLJ ticket have the same effect


if I log out


I can see them

Alex Miller (Clojure team)12:05:18

Yeah, I was just going to guess that


so probably a migration wart

Alex Miller (Clojure team)12:05:38

Atlassuans identity model is ... weird

👍 4

and I'm sure migrating from the age old install brought its own challenges 🙂

Alex Miller (Clojure team)12:05:35

I’ll look at your account or whether you have one when I get to a computer


no rush anyway


I'm supposed to be in the having previously edited crowd if that helps

Alex Miller (Clojure team)12:05:06

So you should have an account - did you do the reset process to get a new password ?


I'm all setup with an account, I followed the link I received by email

Alex Miller (Clojure team)12:05:51

So when you log in, you can’t see links?


Actually, I didn 't generate a new password but used google sign-on


and yes, once logged in I cannot access tickets


(email is <mailto:[email protected]|[email protected]> if that helps once you reach your computer)

Alex Miller (Clojure team)13:05:57

I don't think you can use google sign-on for this org as this site is not tied to a single domain

Alex Miller (Clojure team)13:05:07

you'll need to use email/password


uh, I logged in with google sign-on and it worked


FYI I get a 403 when I try to hit, not sure if that was supposed to redirect

Alex Miller (Clojure team)13:05:20

that shouldn't at the moment, although it could

Alex Miller (Clojure team)13:05:33

well that's good to know

Alex Miller (Clojure team)13:05:40

@pyr your acct was missing access to the jira product, not sure how that happened, but it should help


@alexmiller things look much better now, thanks!

Alex Miller (Clojure team)14:05:28

everyone should have had that added during the import, but maybe it messed up for some people. will probably do some spot checks later.


`select-keys` does not preserve metadata on its first map argument. Yes, it does. Must be time to stop work -- I'm hallucinating! What would be the pros and cons of changing it to do so? I get the impression that several other functions have recently been "fixed" to do so...


Are you preparing ticket / patch for this? I can if you aren't already doing it.


I was about to, but then when I tried to repro, it worked.


I swear it had not worked when I first tested it...


Looking at select-keys implementation in Clojure 1.10, it looks like it should always preserve metadata


Change looks like it was made before release of Clojure 1.5