I am trying to redirect users from one portal to another, as seamlessly as possible.
For example, users of portal A commonly have a question about issue X that is actually handled by portal B. However, due to the volume of users coming to portal A for that issue, it made sense to keep it listed there.
The current, not-ideal solution is to have issue X listed in portal A as a request type, with a link to portal B.
However, because its a request type, on portal A, it's counter intuitive to the users to simply click the link, and it often generates an unnecessary ticket (if they send the request, rather than click the link). And it just doesn't look as professional as I'd like.
Does anyone have any advice or know if it's possible to make this a more seamless transition from clicking on the issue and being directed to the other portal? I was thinking maybe with automation, but I don't know if portal A and portal B can share request types, etc.
Let me know if anyone has any advice.
-Matt
Welcome to Atlassian Community!
You may want to take a look at the external resource feature, it allows you to add links to the portal like this:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That was very helpful, but still not an ideal solution to my problem due to its placement at the bottom of the portal. I wish I could embed a Related Resource into a portal group and/or move it to the top!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.