Fork me on GitHub
#clojure-dev
<
2020-08-25
>
andy.fingerhut18:08:05

When I try to look at particular open issues on the core.rrb-vector library on http://clojure.atlassian.net, it briefly shows what looks like a correct URL, but then before displaying the issue I want, the URL changes to one that shows all open issues. Has anyone else seen such behavior, and/or know what I might do to prevent that?

ghadi18:08:42

Yeah I’m getting the same bug on CLJ too

alexmiller19:08:09

Can you give me an example

ghadi19:08:41

@alexmiller I nav to jira, wait for it to load (takes 10+ seconds to settle down), then click on a different ticket in the left hand side. It briefly goes there then reverts back to the CLJ project

alexmiller19:08:30

sorry, not seeing that. I believe you, because jira, but not seeing it

ghadi19:08:46

Try private window?

alexmiller19:08:48

browser/os ?

ghadi19:08:01

Firefox/mac

alexmiller19:08:46

I think I see what you're describing

andy.fingerhut19:08:41

chrome/mac for me

seancorfield19:08:55

Does it only happen when you're not logged in? JIRA behaves really strangely if you are not logged in but try to browse tickets...

alexmiller19:08:34

yeah, when not logged in

alexmiller19:08:48

nothing has been changed recently (except perhaps jira itself) and I've looked at all the permissions - browse is open to public and the permissions helper says anyone should be able to see these

alexmiller19:08:12

I see it when naving in the context of a filter though

alexmiller19:08:28

if you click on the left list, it goes back to the filter. if you click on the issue id on the detail pane link on the right, it gives you a browse link which works

alexmiller19:08:45

I will check some more stuff with filter permissions

andy.fingerhut19:08:56

When I saw the behavior, I was looking at all open issues for a project, and trying to click on one specific issue in the list.

alexmiller19:08:08

yeah, that should be my last link there

andy.fingerhut19:08:09

Good to know the workaround of providing a URL directly to the issue.

alexmiller20:08:38

well, in summary - I don't know why that doesn't work. seems like it should and afaict there is no permission preventing it. using the web console certainly seems like a lot of weird stuff happening. I'll file a jira on jira. :)

alexmiller20:08:44

although you probably can't see that anonymously, or maybe only I can see it, don't know

ghadi20:08:57

can't see it, but appreciating it nonetheless

ghadi20:08:04

authentication definitely matters