Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Redirections for links to Marketplace add-on support tags yield a 404


Not sure whether this is a CAC or MAC regression, but given the migration from AAC to CAC already involves quite some redirections, it seems appropriate to start reporting it here.

See for example the Email This Issue listing:

The Atlassian Community link on the support tab still links to the old AAC tag addon-com.metainf.jira.plugin.emailissue, and while that tag also exists as the CAC tag addon-com.metainf.jira.plugin.emailissue, the redirection is broken and yields a 404.

And to make sure this is not overlooked, the same problem exists for add-ons that do not yet have a tag, which should yield a respectively populated question form so that users can seed a tag (better yet, each tag should be auto generated upfront to ease monitoring of course, but that wasn't available before either).

See for example the Automation with AWS (JIRA) listing:

The Atlassian Community link on the support tab still links to the non existent AAC tag addon-net.utoolity.atlassian.jira.automation-with-aws-jira, and while that tag likewise does not yet exists as the CAC tag addon-net.utoolity.atlassian.jira.automation-with-aws-jira, the redirection does not yield a populated 'Ask question' form and yields a 404 instead.

I hope it goes without saying that this is is a notable impediment for the support experience of users and Marketplace vendors alike and should be addressed quickly accordingly ;)

Many thanks,

1 answer

1 accepted

1 vote
Answer accepted

I just realized that I missed last night's resp. announcement in the Atlassian Developer Community (too much, too many information sources still ...), see Redirects for to the new Atlassian Community:

The Atlassian Community launched today and all requests for are being redirected to Marketplace listings that have Atlassian Answers enabled (or a link for "Atlassian Community") are currently being redirected to a 404 page inside of the new Atlassian Community. A fix is in place and will be deployed tomorrow morning.

There is a known issue for community tags without questions. We are working with the Atlassian Community team to fix that experience as well.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events