Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.

Kind regards,
Dong Hoang
JIRA Software

Hi jorhett,

If you'd like to comment on https://ecosystem.atlassian.net/browse/FISH-587 you will need to sign up for an account on that instance at https://ecosystem.atlassian.net/secure/Signup!default.jspa. If you jsut want to look at the issue you should be able to. If you're happy to comment here, that's fine also.

Cheers,
Eric

I might be a bit dense at this late hour, but I'm not sure I understand what you mean. We don't use or have any OnDemand accounts. Do I have to register in an OnDemand instance to login to this? It seems a way bit orthogonal to an enterprise support issue...

Hi jorhett,

You've actually highlighted a good usability issue there. The Ecosystem instance actually runs in OnDemand and as a result that page is asking if you are part of the Atlassian Google Apps accounts or have an account within that OnDemand instance - in this case it's the latter (or will be once you sign up ). If you register for an account and sign in with the OnDemand option that'll give you all you need here.

Regards,

Chris

It did redirect me there last night. It gives two choices: OnDemand login or Google auth. Since we are your largest size/price commercial account we aren't really ondemand profile...

Hi jorhett,

We realise that having many systems is indeed frustrating, and we are working towards consolidating them and reducing the number of different credentials requires where possible. That said, if you make comments on this issue we will still see them

studio.plugins.atlassian.com has been removed as part of our consolidation efforts. The linked issue should now be at https://ecosystem.atlassian.net/browse/FISH-587 and should be anonymously accessible. It should redirect, but I guess that isn't working for you?

You should be able to sign up for that system (I know, it's another account) which will create an account that does not use google auth.

Our goal is not to prevent people from tracking or discussing issues. Tracking in a separate project means that the team responsible for the plugin can take care of it in a much more efficient manner, and release separate releases that (theoretically) should allow people to upgrade just that plugin and get the bug fix without also having to performa complete JIRA upgrade. If you have any suggestions on how we could better achieve the goals of managing projects separately but at the same time maintaining visibility, I'd love to hear them. We have some ideas already but we're always open to new ones.

Regards,
Eric

Eric, you've moved this out to a system where I cannot login to vote or watch, etc because your Atlassian logins don't work there and I won't use Google Auth systems.

Seriously, how many different "single" authentication systems does Atlassian have? Really?

Or is the goal to do what you've achieved: removed our ability to argue for or even track the status?

Hi Jo,

I've copied this issue to https://studio.plugins.atlassian.com/browse/FISH-587 for tracking in the project for this plugin.

Cheers,
Eric