Code Commenting replied by Christiaan @ Sat, 30 Oct 2010 06:55:37 UTC

Christiaan — Sat, 30 Oct 2010 06:55:37 UTC

I don't think you should use repository to document your code. Commit comments describe what functionality has changed with the new version, not how each line of group of lines work. You could commit in multiple fases with 1 commit per functionality. You can keep code documentation in your code. But also have a shrinked version. When it comes to javascript, you can use the yui compressor.

Email Notifications & Gmail Conversations posted by Mauronic @ Wed, 23 Jan 2008 19:38:43 UTC

Mauronic — Wed, 23 Jan 2008 19:38:43 UTC

Due to the generic subject lines of unfuddle email notifications, gmail puts all my unfuddle notifications into a huge conversation thread. I would prefer these conversations to be grouped by bug or message. If the subject line was changed such that Gmail would do a better job organizing conversation threads (e.g. into conversations about bugs, messages, etc) these notifications would be a lot easier to manage and act on. I am not sure of a sure fire way to do this because their conversation grouping algorithm is not entirely transparent. However, I bet starting with more specific subject lines would help. (Right now, it seems that every subject line reads "Recent Activity for ".

Don't save most recent Status as default replied by Joshua Frappier @ Sat, 24 Oct 2009 16:48:29 UTC

Joshua Frappier — Sat, 24 Oct 2009 16:48:29 UTC

Most of the time, if one enters a sequence of tickets, they tend to be similar in form. Accordingly, as you have noticed, we try to be smart about remembering previous values. There is currently no way to specify default values that will always display first. We will consider your post as a +1 for this feature.

Importing from Trac posted by Keith Lancaster @ Wed, 05 Dec 2007 18:27:58 UTC

Keith Lancaster — Wed, 05 Dec 2007 18:27:58 UTC

I have a been using unfuddle for some small projects (I have a micro level account) and have found it quite useful. I am considering moving our main project over to Unfuddle, but we have a pretty significant Trac database of issues, defects, etc. that we can't lose. Has anyone come up with a way to convert/import trac tickets?

[killer] IM/Chat Integration replied by webmasterkai @ Tue, 10 Nov 2009 01:40:42 UTC

webmasterkai — Tue, 10 Nov 2009 01:40:42 UTC

We use gtalk and custom jabber servers. Jabber integration is the most requested feature in our office. It's something we had when using our custom project management software.

CNAME Pointer to Other Domain? replied by tobiassjosten @ Tue, 26 Jan 2010 17:08:49 UTC

tobiassjosten — Tue, 26 Jan 2010 17:08:49 UTC

Thanks for reassuring us that you are at least still "out there". Looking forward to seeing this feature, whenever it shows up!

Allow customers to report bugs (submit ticket)? replied by DW @ Mon, 25 Feb 2008 07:14:04 UTC

DW — Mon, 25 Feb 2008 07:14:04 UTC

Thanks Ben. I'll check it.

Rich Text Editor replied by DW @ Thu, 24 Jul 2008 02:54:23 UTC

DW — Thu, 24 Jul 2008 02:54:23 UTC

"I would like to have our folks in non-tech areas (business analysts, etc) start actively sharing information through unfuddle wiki pages. Markup wouldn’t be comfortable for them." I face the same problem before. In the end, they (business user in my company) don't use Unfuddle. :-( I don't know why many people in this forum think from programmer's perspective. They don't know how "difficult" for those business people to read how to use plain text markup. I love Unfuddle. Our developer use this. But we must use separate software for business users. I'm thinking to move to FogBugz before. I still use Unfuddle because I hope they'll add this feature later. Btw, don't get me wrong. I *really* love Unfuddle. But you have to be realistic. Are you selling this software only for developers? There are many potential users who prefer to use rich text editor. :-) "FogBugz Rich Text Editor":http://www.fogcreek.com/FogBugz/learnmore.html#hist_RichTextEditor

Rich Text Editor replied by ShayneM @ Wed, 09 Sep 2009 02:32:05 UTC

ShayneM — Wed, 09 Sep 2009 02:32:05 UTC

+1 for this Markdown is ok for devs (most of the time) but some flexibility would not hurt. Be ware of not doing the 37Sigs thing and not listening to what users want and offering options rather then deciding for them

Continuous build integration posted by Nix_o_lay @ Wed, 26 Dec 2007 21:10:58 UTC

Nix_o_lay — Wed, 26 Dec 2007 21:10:58 UTC

Guys, Do you plan to add continuous build integrations support? This may add valuability to some of your plans. WBR, Nikolay Ryabkov.

Manually Associate Changesets replied by Michael Bleigh @ Fri, 13 Jun 2008 18:22:52 UTC

Michael Bleigh — Fri, 13 Jun 2008 18:22:52 UTC

Thanks as always!

Honor carrier returns in commit messages replied by Luis Lavena @ Fri, 20 Jun 2008 12:06:10 UTC

Luis Lavena — Fri, 20 Jun 2008 12:06:10 UTC

Thanks David, Is great to see my comments now well formatted ;-) Also thanks to work so quickly! Have a nice weekend! -- Luis Lavena

Agile/Scrumm and unfuddle replied by Gleb @ Sun, 07 Nov 2010 23:08:03 UTC

Gleb — Sun, 07 Nov 2010 23:08:03 UTC

agree especially with displaying tickets as a tree- these relations aren't very convenient to use the way they are implemented now

Setting Default Permissions posted by ghostradio @ Fri, 22 Aug 2008 20:07:19 UTC

ghostradio — Fri, 22 Aug 2008 20:07:19 UTC

Many members of our team have the same permissions level on several projects. Would it be possible to set a default permissions level for a person that is carried over to whatever project they get assigned to? In some cases we may want to tweak their permissions on a specific project, but those permissions would be unique to that particular project.

PHP Markdown Extra posted by Christian Vitroler @ Wed, 03 Oct 2007 12:15:16 UTC

Christian Vitroler — Wed, 03 Oct 2007 12:15:16 UTC

Would it be too much to ask for an implementation of those enhancements? After all, there is already an implementation in Ruby, namely [Maruku](http://maruku.rubyforge.org/maruku.html) Oops... Markdown for links does not work here... anyway... http://maruku.rubyforge.org/maruku.htm

Notification emails in real-time replied by ShayneM @ Wed, 09 Sep 2009 01:23:35 UTC

ShayneM — Wed, 09 Sep 2009 01:23:35 UTC

+1 for this

Restrict information sent in email notifications replied by David C. @ Wed, 14 Oct 2009 18:29:44 UTC

David C. — Wed, 14 Oct 2009 18:29:44 UTC

Youngblood, This is not currently implemented within Unfuddle. This has not been a very oft requested feature, however, we can certainly discuss internally the idea of "locking down" an account like this.

change markdown replied by Ben Strackany @ Tue, 03 Mar 2009 21:39:42 UTC

Ben Strackany — Tue, 03 Mar 2009 21:39:42 UTC

Well, I will say that the FM could do a better job on explaining or showing how to create nested lists.

change markdown replied by ShayneM @ Wed, 09 Sep 2009 01:24:41 UTC

ShayneM — Wed, 09 Sep 2009 01:24:41 UTC

We also find markdown a pain at times due to the need to preview and re-edit Why not offer a fully WYSIWIG options using FCKEditor or TinyMCE? Could toggle between both on toolbar thus catering for all needs.

Assign ticket to someone for verification posted by jumpfroggy @ Wed, 14 Jan 2009 18:10:11 UTC

jumpfroggy — Wed, 14 Jan 2009 18:10:11 UTC

Often I create a ticket, resolve it, then want to assign it to someone for verification. Unfortunately verification is hard-linked to the reporter, which is non-editable. So in order to assign it, it also becomes unresolved. It would be nice to be able to assign the ticket to someone for verification, without having to unresolve it.

Preview for all markdown input fields replied by Thomas Jones-Low @ Wed, 22 Apr 2009 13:58:40 UTC

Thomas Jones-Low — Wed, 22 Apr 2009 13:58:40 UTC

I would like to second this. Coming from wikimedia where preview is ubiquitous and encouraged, I fnd the lack of a preview function very frustrating.

Email a ticket replied by max @ Fri, 08 Feb 2008 06:02:47 UTC

max — Fri, 08 Feb 2008 06:02:47 UTC

David, Sorry that it took so long for me to reply, but yes...you nailed it on the head. It would be great to have some type of "send reminder" option and that would be helpful for any section. Great to hear that you agree with this!

Universal Ticket Numbers posted by chrisk @ Tue, 31 Mar 2009 00:27:46 UTC

chrisk — Tue, 31 Mar 2009 00:27:46 UTC

We use the concept of unfuddle Projects extensively and each project has its own queue of tickets. Oftentimes a ticket will move from one project (say "Feature Requests") to another (say "Engineering"). It'd be nice to be able to see the history of the tickets as they move throughout the unfuddle system. Today when a ticket moves across projects it picks up the next ticket number in that particular project's queue, and there is no way to reference the ticket in the "old" project after it's been saved to the new project.

Universal Ticket Numbers replied by Stewart Robinson @ Fri, 24 Apr 2009 14:33:10 UTC

Stewart Robinson — Fri, 24 Apr 2009 14:33:10 UTC

+1 to this. This is needed. I can't tell with my commits which project a ticket belongs to as all my projects share the same source control

Latest comments RSS replied by David C. @ Thu, 25 Oct 2007 05:57:55 UTC

David C. — Thu, 25 Oct 2007 05:57:55 UTC

Ben, As Josh just mentioned in "another post":http://unfuddle.com/community/forums/4/topics/58 we have considered adding comments to the recent activity list on the overview and dashboard, but in its current layout the list could get very long and unwieldy. So, currently, the best way to keep track of comments on a ticket or message is via the email notifications.

Recent Posts in Feature Requests | Unfuddle Community