Details
-
Type:
Sub-task
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 4.4.0-b1
-
Component/s: None
-
Labels:None
Description
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). The markdown editor does not currently support defining definitions for those languages, so only English is supported currently.
- Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g.
<textarea data-markdown-editor=''></textarea>
- Define a specific language for the markdown editor with the "lang" attribute, e.g.:
<textarea data-markdown-editor="" lang="fr"></textarea>
- By default, the editor will use the HTML document's language, unless overidden by the textarea field.
<html lang="fr"> ... <textarea data-markdown-editor=""></textarea>
- By default, the editor will use the HTML document's language, unless overidden by the textarea field.
Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well.
Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility.
Additional Options
https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off.When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI.
Issue Links
- blocks
-
CORE-2299
Support Manager: Add markdown editor
-
- Closed
-
Activity
Tyson Phillips (Inactive)
created issue -
Tyson Phillips (Inactive)
made changes -
Tyson Phillips (Inactive)
made changes -
| Fix Version/s | 4.3.1 [ 11104 ] |
Tyson Phillips (Inactive)
made changes -
| Fix Version/s | 4.4.0-b1 [ 11105 ] | |
| Fix Version/s | 4.3.1 [ 11104 ] |
Automated transition triggered when Tyson Phillips (Inactive) created a branch in Stash -
| Status | Open [ 1 ] | In Progress [ 3 ] |
Tyson Phillips (Inactive)
made changes -
| Remaining Estimate | 0 minutes [ 0 ] | |
| Time Spent | 6 hours [ 21600 ] | |
| Worklog Id | 11385 [ 11385 ] |
Tyson Phillips (Inactive)
made changes -
| Description |
Pull in a Markdown editor into the core that uses (or supports) our flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Pull in a Markdown editor into the core that uses (or supports) our flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Tyson Phillips (Inactive)
made changes -
| Description |
Pull in a Markdown editor into the core that uses (or supports) our flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). *The markdown editor does not currently supporting defining definitions for those languages, so only English is supported currently.* # Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g. {code} <textarea data-markdown-editor=''></textarea> {code} # Define a specific language for the markdown editor with the "lang" attribute, e.g.: {code} <textarea data-markdown-editor="" lang="fr"></textarea> {code} #* By default, the editor will use the HTML document's language, unless overidden by the textarea field. {code} <html lang="fr"> ... <textarea data-markdown-editor=""></textarea> {code} ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Tyson Phillips (Inactive)
made changes -
| Description |
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). *The markdown editor does not currently supporting defining definitions for those languages, so only English is supported currently.* # Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g. {code} <textarea data-markdown-editor=''></textarea> {code} # Define a specific language for the markdown editor with the "lang" attribute, e.g.: {code} <textarea data-markdown-editor="" lang="fr"></textarea> {code} #* By default, the editor will use the HTML document's language, unless overidden by the textarea field. {code} <html lang="fr"> ... <textarea data-markdown-editor=""></textarea> {code} ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). *The markdown editor does not currently supporting defining definitions for those languages, so only English is supported currently.* # Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g. {code:html} <textarea data-markdown-editor=''></textarea> {code} # Define a specific language for the markdown editor with the "lang" attribute, e.g.: {code:html} <textarea data-markdown-editor="" lang="fr"></textarea> {code} #* By default, the editor will use the HTML document's language, unless overidden by the textarea field. {code:html} <html lang="fr"> ... <textarea data-markdown-editor=""></textarea> {code} ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Tyson Phillips (Inactive)
made changes -
| Description |
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). *The markdown editor does not currently supporting defining definitions for those languages, so only English is supported currently.* # Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g. {code:html} <textarea data-markdown-editor=''></textarea> {code} # Define a specific language for the markdown editor with the "lang" attribute, e.g.: {code:html} <textarea data-markdown-editor="" lang="fr"></textarea> {code} #* By default, the editor will use the HTML document's language, unless overidden by the textarea field. {code:html} <html lang="fr"> ... <textarea data-markdown-editor=""></textarea> {code} ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Pull in a Markdown editor into the core that uses (or supports) github flavor of Markdown. It should be setup to easily be usable by the core and plugins in various locations.
This can be used by creating a textarea field with the attribute "data-markdown-editor". All textarea fields with that attribute set will be converted to a markdown wysiwyg. Additionally, a "lang" attribute can be included on the same textarea field to include what language definitions to use for the markdown editor. This currently only supports 2-character language (e.g. "en", "es", or "fr"). *The markdown editor does not currently support defining definitions for those languages, so only English is supported currently.* # Make any textarea field a markdown editor by including the attribute "data-markdown-editor", e.g. {code:html} <textarea data-markdown-editor=''></textarea> {code} # Define a specific language for the markdown editor with the "lang" attribute, e.g.: {code:html} <textarea data-markdown-editor="" lang="fr"></textarea> {code} #* By default, the editor will use the HTML document's language, unless overidden by the textarea field. {code:html} <html lang="fr"> ... <textarea data-markdown-editor=""></textarea> {code} ---- {quote} Add markdown editor support for tickets. Consider adding any necessary libraries to the core, as we may want to use this in other areas as well. Take a look at https://stackedit.io/, which supports Github flavored markdown, as well as others. http://www.codingdrama.com/bootstrap-markdown/ may be another possibility. *Additional Options* https://pandao.github.io/editor.md/ looks promising, MIT licensed, and a side-by side preview option that can be toggled on/off. When clients or admins open or respond to a ticket, they can use markdown syntax but there is no editor. Add the editor to both client and admin areas for opening or responding to tickets from the UI. {quote} |
Tyson Phillips (Inactive)
made changes -
| Time Spent | 6 hours [ 21600 ] | 7 hours, 45 minutes [ 27900 ] |
| Worklog Id | 11386 [ 11386 ] |
Automated transition triggered when Tyson Phillips (Inactive) created pull request #499 in Stash -
| Status | In Progress [ 3 ] | In Review [ 5 ] |
| Resolution | Fixed [ 1 ] |
Tyson Phillips (Inactive)
made changes -
| Time Spent | 7 hours, 45 minutes [ 27900 ] | 1 day, 1 hour, 34 minutes [ 34440 ] |
| Worklog Id | 11404 [ 11404 ] |
Automated transition triggered when Tyson Phillips (Inactive) merged pull request #499 in Stash -
| Status | In Review [ 5 ] | Closed [ 6 ] |
