Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Hyperlinks in link tooltip are shown in plaintext #1081

Open
mickmister opened this issue May 28, 2024 · 2 comments · May be fixed by #1128
Open

Hyperlinks in link tooltip are shown in plaintext #1081

mickmister opened this issue May 28, 2024 · 2 comments · May be fixed by #1128
Milestone

Comments

@mickmister
Copy link
Contributor

Jira's "markdown" system is a bit different than Mattermost's, which can cause some issues with interoperability between the platforms. For example, the link tooltip feature will show "smart links" in plaintext like the screenshot below.

From the investigation here: [https://mattermost.atlassian.net/browse/MM-52952|https://mattermost.atlassian.net/browse/MM-52952|smart-link] Seems like the a...

Should instead render as:

From the investigation here: https://mattermost.atlassian.net/browse/MM-52952 Seems like the a...


image


It is a general problem that there are fundamental differences between the two markdown systems, and there have been some efforts to holistically address this, though it may make sense to address the known inconsistencies individually #599 (comment). Meaning, we can have certain things in the code like "replace Jira smart link with regular markdown link" when the information is fetched from Jira before returning to the UI for the tooltip.

@mickmister
Copy link
Contributor Author

@Kshitij-Katiyar Curious about your thoughts on having an effort to handle individual markdown discrepancies between the two systems. I think starting with documenting differences we know would be a good first step (maybe @AayushChaudhary0001 can help produce/find these) Then we can create HW tickets to address the known issues there. This would involve:

  • For the create issue feature, format anything necessary things to fit Jira's markdown model
  • For any rendering (posts, tooltip) of Jira issue descriptions format anything to fit Mattermost's markdown model

@Kshitij-Katiyar
Copy link
Contributor

@Kshitij-Katiyar Curious about your thoughts on having an effort to handle individual markdown discrepancies between the two systems. I think starting with documenting differences we know would be a good first step (maybe @AayushChaudhary0001 can help produce/find these) Then we can create HW tickets to address the known issues there. This would involve:

  • For the create issue feature, format anything necessary things to fit Jira's markdown model
  • For any rendering (posts, tooltip) of Jira issue descriptions format anything to fit Mattermost's markdown model

sure @mickmister we should start by creating the differences list first and depending upon the complexity and time, we can create the help wanted tickets as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants