Please do not enter new items.

Markdown Case Editing

Allow FogBugz users to use simple markdown elements to add formatting to case edits and events. (More on Markdown here: http://en.wikipedia.org/wiki/Markdown)

218 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    I agree to the terms of service
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    AdminDan Wilson (Admin, fogbugzplugins) shared this idea  ·   ·  Admin →

    14 comments

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      I agree to the terms of service
      Signed in as (Sign out)
      Submitting...
      • Ken commented  · 

        Since Fog Creek has access to this functionality in stackoverflow/stackexchange, why not make this part of the FogBugz core? Or alternatively, it could be a Fog Creek supplied plugin like Case Event Edit.

      • David Mitchell commented  · 

        What is the status of development on this? The codeplex page looks like it has stalled. I would be so interested in this plugin when it is ready.

      • James Bayley commented  · 

        I think this is a great idea. I like the simplicity of Markdown syntax and would find it really useful in FogBugz

      • JohnFx commented  · 

        It looks like several people were working on this same plug-in, so I created an Open Source project on CodePlex so that anyone interested in contributing can do so.

        Here's a link to the project if you are interested:
        http://fogbugzcasemarkdown.codeplex.com/

      • JohnFx commented  · 

        I'm getting pretty close with a plug-in to do this. However, the biggest concern I have about this is that most other tools that offer some kind of markup/down also let you edit the text after you save it. With this you are stuck after you hit the save button because of the FogBugz No-edit/no-delete rules. I'm going to try to mitigate this as much as possible by having a preview available before you save.

      • JohnFx commented  · 

        @stefanrusek: Did you give up on this or are you still working on it? I have a basic implementation working right now that I was grooming for release, but if you have been working all this time on your own, I'll stand down and let you tackle this one.

        BTW: I agree that the API makes this pretty complicated, even with the new BugEventDisplay method. However, I think I'm off to a good start.

      • daniel.simms commented  · 

        In general, I'm skeptical of "simplified" markup languages, but using MarkDown more regularly on StackOverflow, I've grown a bit fond of it. It's quite a nice compromise.

      • David Fullerton commented  · 

        @stefanrusek please post on the developer discussion group the interface you want / what you want to be able to do

      • stefanrusek commented  · 

        @David As soon as that interface is available I will write a markdown generator. Anyway we could get something similar for email generation?

      • adambox commented  · 

        stefan, there is a way to do this using the sHTML and fHTML columns in BugEvent, but I'm not sure if you can do email

      • stefanrusek commented  · 

        The downside is that the Plugin API doesn't really provide a clear way to do this. I may start on something like this today, though I don't see a way to make outgoing emails work, because the only way I see would be to add some JS to the case view page to convert the markdown to HTML at page load time.

      • mfn commented  · 

        Although not my favorite choice of syntax, I actually care more to *have* some kind of formatting instead of none at all.

        **for bold** is weird to me, *many* application support already *this* for bold (Mediawiki, TortoiseSVN, Thunderbird, etc.).

        However, stackoverflow adopted it and it "just works", so, request from me, too.

      • Greg Saven commented  · 

        Yes! I have often wanted a simple bulleted list, the ability to bold a bit of text, or reduce an obnoxious URL to a single word.

      Feedback and Knowledge Base