Unable to authenticate at Moodle JIRA.

[Mr_ Beedell_ Roke Julian Lockhart _RJLB_]

When I appear to successfully authenticate at https://id.atlassian.com/login?application=jira&continue=https%3A%2F%2Fmoodle.atlassian.net%2Fjira%2Fprojects, I am not authenticated, and see:

Hash Z68R6J
Trace 9cf558c1812242ae9b4d9a312bedc01a

I report this here because https://jira.atlassian.com/projects/JRASERVER/summary#create_link:~:text=Boards-,Create,-Give%20feedback%20to doesn't permit to file a bug (https://jira.atlassian.com/secure/CreateIssueDetails.jspa returns "User '286b26536a40' doesn't have the 'Edit Issues' permission"), instead directing me to http://support.atlassian.com/contact, which doesn't allow me to file a request.

Initially, I filed https://support.atlassian.com/requests/CA-3661729 via https://www.atlassian.com/company/contact/purchasing-licensing#/success. However, I'm not confident that that's the correct avenue.

[Trudy Claspill]

Hello @Mr_ Beedell_ Roke Julian Lockhart _RJLB_ 

Have you reported the problem to the Administrators of your Jira environment? That is the first step.

You Administrators may have set up the environment so that you authenticate against an identity provider, like Okta or Microsoft 365. They would need to investigate that configuration to see if the problem is in that area.

Only Administrators of the environment are permitted to open support cases at https://support.atlassian.com/contact

Opening an authentication ticket with the Billing, Licensing, and Purchasing team is not really the correct route. That team handles Billing, Licensing, and Purchasing issue, and this doesn't reall fall into that category.

Attempting to file a bug at https://jira.atlassian.com is also not the right process and this is a technical issue with your environment, not necessarily a bug in the product.

[Mr_ Beedell_ Roke Julian Lockhart _RJLB_]

Considering JIRA is the bug tracker, I presume that JIRA expects me to ascertain what the correct avenue is independently, then? Most projects that depend upon JIRA have all of their reporting infrastructure geared such that bug reports go to... JIRA.

Regardless, I've posted https://moodle.org/mod/forum/discuss.php?d=469570. Thanks. I suppose that I'm lucky that, in this case, a contact avenue exists.

[Trudy Claspill]

I'm not sure that I understand what you are attempting to express.

Atlassian, the maker of Jira, uses a Jira instance visible to the public to share information about change requests and bugs that have been reported against their products. That is what you found at https://jira.atlassian.com

Atlassian has MANY customers who each have their own instances of Jira and manage their own integrations of Jira with authentication services. 

The customers are responsible for handling front line support for the users they allow to access their instances. If the customer owning that instance finds that the problem is not due to the configuration they have imposed on the environment, then the Administrators within that customer organization can escalate the issue to Atlassian technical support.

Backing up a step, a point we should probably clarify is what were you trying to access when you were directed into the authentication process? Before being able to access an Atlassian Cloud product you may be directed to the Atlassian authentication site to enter your credentials. That in turn may communicate with the authentication service that was configured by the customer owning the Atlassian Cloud product instance.

Alternately you may have been directed to that login when trying to log in to an Atlassian product that Atlassian itself directly owns, such as this Community.

So, I suppose one might suggest that we didn't get the full context of your scenario before offering advice, and so our advice may have missed the mark.