Comments
- 1-9 of 9
We use MySQL extensively and have never had any issues with it. We have also used Postgres and did not find it to be a significant improvement. Given the mature state of Rails db libraries, most of the differences between the databases are abstracted away. In short, if MySQL is really giving Thoughtworks problems, then the Mingle developers are doing something fundamentally wrong. I challenge them to explain exactly what problems they are running into.
We have a large investment in MySQL (setup scripts, backup scripts, machine configs, etc.) and do not want to set up a new db if we can avoid it. For this reason we may not upgrade to Mingle 3.0 and will definitely start looking for a tool that supports MySQL. I bet I am not alone in this.
MySQL is *the* database for many open source projects, and not supporting it seems downright silly. I have to question what Thoughtworks' motivation is for such a disastrous decision.
A proper implementation would use the filter to set some properties and the defaults to set the other properties. For example, we have a view that shows Stories that are not assigned to an Iteration. Using the Add field should set the Priority to the default (Normal for us) since the Priority property is not being filtered on.
There have been several posts about this, and your response is that this is not a bug, and is rather “as designed”. If enough users perceive of given behavior as a bug, then it is indeed a problem that should be solved. Please consider fixing the design so that only unfiltered properties receive the defaults. Any other behavior is clearly errant.
+1 for colored rows, both in List view and for wiki tables. We would like defects with a high severity to stand out in lists.
The Mingle team recently acknowledged that there is a bug, and that it will be fixed for 2.1. In the meantime, don’t use SVN subdirectories if you are running into problems with revision tracking.
Jen, thanks for the info.
I replaced Task Estimate property with one that used a managed number list, and now everything works perfectly. So that is the obvious workaround until version 2.1 comes out.
..tony..
If you set the repository URL to be the top-level directory (e.g. example.com/myproject) everything works fine. If you try to add a subdirectory, nothing works. I have seen this behavior with two different SVN systems over different protocols. I am working with a support person to resolve this.
I am also getting NoSuchRevision errors in the log when I try to browse the source.
The grid view is not actually a “grid”, but I wish it were. I want rows in addition to columns. This would allow us to have Iterations in the columns and the Owners in the rows, a view my boss desperately wants.
+1 for being able to sort on any relationship or dynamic card property (like Owner). Furthermore, provide option to display the property value right on the card, as a supplement or replacement for color. The property value could replace the ID #.