nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Notifications Screen failing to load

Phil Borrell_b8yp7a

Hi All,

So I found an article in the Atlassian community from 2017 that provided a solution to stop internal customers from logging Support projects through the Create button in Jira, instead making them use the Portal to create issues. This works really well, but it has had a side effect:

In the specific JSM Portal I am building, I cannot see the Notifications for this specific project. I know it was caused by my other change as it gave me a generic warning when i made the change, but now that i have reverted it back, the Notification screen is still blank.

Any ideas?

Accepted answers

All comments

Dave LIAO

@Phil Borrell - hi Phil!

Sounds like a coincidence. Locking down the "Create Issues" permission wouldn't prevent someone from seeing a specific admin screen.

Can you share a screenshot?

Phil Borrell_b8yp7a

Thanks for the message @Dave LIAO

I was also under the impression that 'Locking down the "Create Issues" permission wouldn't prevent someone from seeing a specific admin screen.'

Attached is a screenshot

This is a partial URL for that page: atlassian.net/plugins/servlet/project-config/KOS/notifications

Cheers,

Phil

Dave LIAO

@Phil Borrell - try clearing your cache and cookies and load that screen again? Try in an incognito window?

Can you get to the notifications section of other projects you administrate?

Phil Borrell_b8yp7a

@Dave LIAO thanks for the suggestion. I cleared my cache and used Chrome incognito, and i still get the same result.

I also cannot see the notification schemes in any other project, but i can see the Global notification scheme

Dave LIAO

P. S. I definitely suggest opening a ticket with Atlassian to check into your issue. I'll also escalate this thread to them as an FYI

Phil Borrell_b8yp7a

Thanks, I'll open a ticket now!

Angélica Luz

Hello @Phil Borrell,

Thank you for reaching out to Community!

I know it has been a while since you posted this question and I can see that our support team is helping you with this request.

Checking the ticket, I could see that this setting affected a lot your project and I got curious about this article.

I searched here, but maybe I’m using the wrong words because I didn’t find it.

Would you mind sharing with us the community article? I would like to take a look and test on my own site to check if the same issue will happen and to confirm if the steps are correct. Since it’s from 2017, many things changed in Jira, so it might not be valid anymore.

Thank you!

Kind regards,
Angélica

Phil Borrell_b8yp7a

Hi @Angélica Luz

Thanks for the message. This issue is now resolved by Atlassian directly

Lauren Jean

We are having the same issue - Has anyone received an answer?

Vivien Monti

Hello Lauren,

Apparently, this is a known bug at Atlassian. This is the workaround I found:

Step 1. Find your project ID

Go to: https://<your_domain>.atlassian.net/rest/api/3/project

Do a search our your project name and retrieve the corresponding <project_id> (look at the value next to the field "id". Example: "id":"11612" means that the project_id is 11612)

Step 2. Use a direct link to your project notification scheme

Go to: https://<your_domain>.atlassian.net/secure/project/SelectProjectScheme!default.jspa?projectId=<project_id>

(of course you need to replace <your_domain> with your domain name, and <project_id> with the value you found at step 1)

You should now be able to assign a notification scheme to your project.

Hope it helps!

Cheers,

Viv

Lauren Jean

That works, Thanks Viv!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

atl-rvw

jira-service-management