When someone receives a notification from Jira Align (i.e. Dependency Change Notification), the email is delivered and there are links to the dependency.
Selecting any of the links in the email takes the user to the "Whoops" screen and kicks them out of Align.
Does anyone know why the link would not work and why it kicks the user out of Align?
We have Jira Cloud and Jira Align, we use SSO for access and the user is logged in prior to accessing the link.
Thank you!
Hi Allan,
That field is populated with our [servername].jiraalign.com.
Any other suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Rebecca Hylek Does it work if the user logs into Jira Align first and then clicks on the link? It may have something to do with your SSO or needing to be on the VPN.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I had the recipient forward the email to me and I've done a little testing. I have a feeling it is related to something on our end so have our team looking into that. My testing so far and the results are below.
The email contains five links. I'm signed in with SSO, my role is Super admin, I'm using a Chrome browser and our email is Outlook.
1. Select the Dependency ID (i.e. xxxx); Result: Fail; New tab opens on my browser, takes me to the "Whoops" screen and kicks me out of Align. I have to go through SSO to get back in.
2. The next two links include the id and a the description of the dependency (i.e. xxxx - [Description of the dependency]; Result: Successful; A new tab is opened, I can see the dependency, and I'm not kicked out of Align.
3. The next two links are in the area of the email that says "Change Details".
a. Select the Dependency ID (i.e. xxxx); Result: Fail; Same as #1 above
b. Select the Feature link (i.e. xxxxx: External ID - [Description of the feature]; Result: Fail; same as #1 above
Again, we're checking with our team and right now we feel it may be internal. If not, we'll open a support ticket.
Thank you!!!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Rebecca we are having the same issue. I had opened a support ticket with Atlassian and they pointed out they have an open bug and also pointed me to this Community post:
Hopefully this will help in your case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.