Comments
Thanks for pointing this out to us, Olivier. It should be fixed now. ta.
Hi Mike
Currently there is no way to render empty cells in the table markup. This is caused by a bug in the third-party library that Mingle uses for our wiki markup. We aim to upgrade to a newer version of this library within the next few releases and this should fix the problem.
When I come across this problem in my usage of Mingle, I use a hyphen (-) to indicate the cell is left intentionally blank. Perhaps, this workaround or something similar would work for you in the meantime.
thanks
-jen
Right on! Thanks for sharing this.
Hi Dan
If for some reason you are not able to sort out the Jabber server issues in your organization, one alternative is to use the open-sourced Murmurs.AIR client, which you can read about on this Community post.
-jen
Hey there, Joe
The problem you describe was a defect that we have fixed in the 3.0 release. The issue was that after a card/tree property was set to a project variable, e.g. (Current Iteration), as a card type's default, it could not be set to (not set).
However, I saw from one of your other posts that your org. has not yet upgraded to 3.0 so I can offer one workaround. If you delete the project variable that was used as the default value and recreate it, you should be able to set your Iteration property to (not set) as the default.
hope this helps
-jen
Hi Tim
Currently there is no way to set email notifications from Mingle to be in plain-text format.
I have added this requirement to our feature requests.
thanks
-jen
Hi again.
Apologies for my delayed response.
Are you using Mingle 2.3.1? There is a known defect in Mingle 2.3.1 that could be causing the problem you are seeing. The defect is related to using Project variables in card defaults. Once a card/tree property project variable is used as a value of a card/tree property on a card default, it cannot be removed. The card/tree property on the card defaults page will appear to be (not set), but the value will still be the value of the project variable.
This issue has been fixed in our 3.0 release, which can be downloaded from the Studios website. There is also a workaround in the 2.3.1 release for the issue that I describe above. Deleting the project variable that was used in the card default should enable the card/tree property to be set to (not set) again.
I hope this helps.
-jenHi Yen
I am unable to reproduce this behvior. Can you provide me with a little more information so that I can try to assist you. How are you creating the new story cards, via 'Save and Add another', via card quick add, via 'Add with Detail' button? Which version of Mingle are you running?
thanks.
-jen
Hi again
The new Mingle Macro Development Toolkit (v 1.3) has been uploaded to RubyForge at http://rubyforge.org/projects/mingle-macros/
This version will work with Mingle 3.0, which will be released next week.
thanks.
-jen
Hi Matt
The new Mingle Macro Development Toolkit (v 1.3) has been uploaded to RubyForge at http://rubyforge.org/projects/mingle-macros/
This version will work with Mingle 3.0, which will be released next week.
-jen
Hi Mike
Sorry that you had such a frustrating experience.
I wanted to ask if you could please send the text of the stack trace through to our support team: support@thoughtworks.com. I have a suspicion that it is the content of the stack trace that is causing the problem and not the length. Either way, this is an issue that we would like to look into further and will need more details from you to do so.
thanks
-jen
Hi Matt
We hope to have the new Mingle Macro Development Toolkit (including doco) posted to RubyForge by week's end. I will update the Community when it is available.
-jen
Hi Mike
The syntax for the MQL filter would be: Iteration = NULL or Iteration IS NULL.
This syntax is valid both if your Iteration property is a numeric property or if it is a card/tree property.
More information can be found in our help under the MQL section.
hope this helps
-jen
Hi
Mingle launched with MySQL, and therefore ThoughtWorks Studios has had a long history with it. Over time, we have had a few critical issues associated with MySQL; issues that have required significant bandwidth from our team to resolve. Based on the publicly available roadmap for MySQL, we determined that the fixes we desire will not be addressed in time to accommodate our product development schedule. Therefore, we decided to move away from MySQL. We realize this will be a difficult transition for some customers, but in the interest of product quality we feel that this is the wisest choice.
In the coming weeks, we will be posting further information about how to migrate Mingle to one of our supported databases.
-jen
Hi Rajiv
I think we will best be able to help you if you contact our support team at support@thoughtworks.com.
Please include the Mingle version and OS/DB information and the Mingle.log files when you contact them.
-jen