Project shortcuts show saved successfully but never appear (Free plan, Jira Cloud)

Dimitris Sigalas

Hi all,

We're on a Jira Cloud Free plan and running into an issue with Project Shortcuts that I can't resolve on my own (I'm Global Admin on the site).

Issue: When adding a new Project Shortcut, the UI confirms "saved successfully," but the shortcut never appears in the list — not after reload, not after hard refresh.

Steps to reproduce:

1. Go to Project Settings → Shortcuts
2. Add a new shortcut (tested with multiple different URLs — both external and internal/local domains)
3. UI shows a success confirmation
4. Shortcut does not show up in the list afterward

Troubleshooting already done:

• Reproduced across 2 different browsers, both in incognito/private mode (rules out cache/extensions)
• Reproduced across multiple projects and multiple different URLs
• Deleted an existing (previously working) shortcut and tried to re-add it — same silent failure
• Confirmed Global Admin / Administer Projects permissions
• Existing shortcuts added in the past still display correctly — issue is isolated to new additions

Since we're on the Free plan, I don't have access to a direct support ticket. Has anyone else seen this, or does anyone from the Atlassian team have insight into what might cause this?

Thanks in advance!

Brita Moorus

Hi, @Dimitris Sigalas! 👋

A few extra things I would check:

• Try with a very simple public URL, for example <a href="https://www.atlassian.com" target="_blank" rel="nofollow noopener noreferrer">https://www.atlassian.com</a>

• Avoid local/internal-only URLs for the test, just in case validation is behaving oddly

• Check whether the shortcut name contains any special characters

• Ask another site/project admin to try the same action

• Check the browser dev tools/network tab to see whether the save request returns an error, even though the UI says “saved successfully”

I tried to reproduce this on my own Jira Cloud Free plan instance, but the shortcut was created successfully. I also wasn't able to find a matching known bug in Atlassian's public Jira, so hopefully one of the checks above helps narrow it down 💙