...
Expand | ||
---|---|---|
| ||
Limitations
Possible workaroundJSM customers can view all the organisations they are a part of as well as the requests shared with them via those organisations.
Note that this only works if all the service desks linked to those organisations have been added as projects into your Refined site. What we are doing to solve these limitationsWe are in continual contact with Atlassian to improve the APIs. To track the status, see the Atlassian tickets. Please vote or comment on the tickets that are related to these limitations, so that Atlassian can also hear your feedback. |
Expand | ||
---|---|---|
| ||
Atlassian's feature for anonymous portal visitors to search a linked Knowledge Base Space is currently not supported by the API provided by Atlassian, which Refined is built on. Thus, anonymous access on portals for Service Management projects is not supported at this point in time by Refined. The main Help Center page can be set as anonymously accessible. Our goal is to continually add functionality as the Atlassian APIs extend in features. To keep track of this issue or vote/comment on it, click here. Possible workaround(s)Create a confluence space that is anonymously accessible. Use this space as your "knowledge base". Then:
|
Expand | ||
---|---|---|
| ||
Due to knowledge base articles being rendered in an iframe, we have no control over the content in the article. As such, we cannot direct the user to view those links on a Refined site.
|
Expand | ||
---|---|---|
| ||
We have had reports of users not being able to access linked articles properly when linked within navigation modules, link list modules, or on a page. WorkaroundThis is due to the article containing an invalid link. Article links must contain the full link in this format: For example: exampledomain.refined.com/portal/2/article/39026710/Payment |
Expand | ||
---|---|---|
| ||
Links in invitation emailWhen adding a customer to a JSM project, by default the customer will receive an email with a link to complete the signup. When the customer has completed the signup, they are taken to the default Jira Service Management Help Center portal (with xyz.atlassian.net URL), and not the Refined one, and currently the limitation is that Refined cannot redirect the user back to the Refined site. WorkaroundBecause the user needs to complete the signup, our workaround suggests keeping the signup link, but make an addition.
This will prompt the user to
What the customer will see |