Has the tags URL pattern changed in the Atlassian Answers upgrade to Confluence Questions?

Keiei Tanto _Vivid_ September 9, 2014

Now that Atlassian Answers has stabilized, I'm confirming proper operation of the Atlassian Answers link from the Support tab of the Marketplace add-on listing, here, as well as tag watch notification emails. I found that following the link as it is now results in a Page Not Found error. What should I change the URL to? And, for everyone's future reference, what is the correct URL pattern?

 

Randomly clicking on tags to get a sense of the URL patterns, I discovered that pre-migration, the URL format looked like this:

https://answers.atlassian.com/tags/addon-vivid.trace

and after migration, it now looks like this:

https://answers.atlassian.com/questions/topics/758411/confluence-answers

(Ignore the fact that the tags in the above samples differ; just imagine they are identical)

 

I created a question myself with the same tag, clicked it, and derived the following URL:

https://answers.atlassian.com/questions/topics/5603332/addon-vivid.trace

Hmm.. is this usable and dependable by customers?

Furthermore, it seems that a handful of addon-* tags are already registered, as indicated by autocomplete in the tags field.

 

Also, the input field placeholder text is "Choose some topics for your question". Are "tags" (OSQA era) now called "topics"?

1 answer

1 accepted

2 votes
Answer accepted
elibishop
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 10, 2014

There's a known issue of links from Marketplace being broken since the Answers migration; we're tracking it here: https://ecosystem.atlassian.net/browse/AMKT-10760

It's unclear at present whether the solution is going to involve changing how Marketplace generates the link, or making the Answers site able to recognize URLs in the old format, so unfortunately I can't tell you yet what the canonical URL format will be in the future. But however we resolve this, it will be noted on that linked issue.

Keiei Tanto _Vivid_ September 10, 2014

Thanks for the info. We'll update the URL once a solution is determined, and use a temporary URL (as generated above) for the meantime.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events