Jira setup have minor UX issues with the subscriptions step

[DHaussermann]

The subscriptions step pf setup should be improved.
It currently looks like this

There are 2 issues here.

1. Can the string the user must copy not wrap within the text area of the modal? It seem quite clunky that we instruct the user to scroll over.
2. Can we add a button to clipboard the value as we done in other areas of the setup wizard? It would seem smoother for the user to be given a button that copies for them.
   We have buttons elswhere in the setup that have this styling...
   

[Kshitij-Katiyar]

@DHaussermann The string mentioned to be improved in the issue is present in the modal, which renders while setting up the plugin and displays the URL to be used for creating the webhook. One easy fix that I tried was to use markdown here, like next line which is used in the below example of complete.html url you have given, but this is not getting rendered as modal, which is displaying the URL here, and it is getting generated by the backend code, which is not supporting this markdown.
@mickmister Can you please suggest something else that might work here?

[mickmister]

@Kshitij-Katiyar I think the scrolling thing is the most important thing to solve here, as that modal is simply not supposed to work that way.

Having it rendered as a markdown "link" instead of "code" should let the user right-click and select "Copy link address". Not sure if we need anything else here. The "click here to copy" seems overkill for the interactive dialogs.

which is not supporting this markdown.

I'm not sure what this means

[Kshitij-Katiyar]

@mickmister is this what we are looking for ?

[mickmister]

@mickmister is this what we are looking for?

I was thinking it would show the full URL. This screenshot makes me think I should click that link to learn more about webhook URLs. @DHaussermann What do you think?

[Kshitij-Katiyar]

@mickmister What do you think about this

[mickmister]

@Kshitij-Katiyar I'm thinking the URL should be on its own after the paragraph. Otherwise, it's difficult to parse the explanation text versus the text intended for computers (the URL). This sort of thing is not really my specialty though. @DHaussermann What do you think?

[Kshitij-Katiyar]

@mickmister @DHaussermann I tried to keep it in a separate paragraph by putting /n before and after the URL but for some reason, this is not working maybe this is not supported in the modal generated from the backend I guess

[mickmister]

@Kshitij-Katiyar There may be an issue in the way the dialog is rendering markdown https://github.com/mattermost/mattermost/blob/master/webapp/channels/src/components/interactive_dialog/dialog_introduction_text.tsx

Another thought, does the triple backtick code block as an option:

https://mymattermost.com/plugins/jira/webhook

[Kshitij-Katiyar]

@mickmister Triple backticks are currently in use in the master branch and they are not working as intended. As you said there may be an issue in the way the dialog is rendering markdown.

[mickmister]

@Kshitij-Katiyar Okay how about we do the hyperlink approach like #939 (comment), but we put the link at the end of the paragraph?

[DHaussermann]

@Kshitij-Katiyar sorry for the late reply.
For me, I would agree with @mickmister, we should keep the entire string visible to the user. hiding it could make some people uncomfortable as it makes it more diffcult to double check what you're doing.

[Kshitij-Katiyar]

@mickmister @DHaussermann Please share your opinion about this setup. There is a '\n' between the Paragraph and link but it is not working

[mkdbns]

@Kshitij-Katiyar , I don't this will work well without the line-break. Can we explore why it's not working?

[Kshitij-Katiyar]

@mkdbns @mickmister
I worked out an approach for adding a new line. Please share your views on this

[mickmister]

@Kshitij-Katiyar Are you able to open a PR so we can see the changes thus far?

@cwarnermm Do you have any advice on how we should word/structure the above message? This is formatted markdown in the modal

[cwarnermm]

Thanks, @mickmister. I've provided text feedback via #983

[raghavaggarwal2308]

Closing via #983