Comments
Srjan -
Thanks for the request.
This feature is already captured and we will consider it for future releases. If you are interested we have a similar request for this here.
Srdjan -
This feature has been asked by various users in the past and is in our backlog for future releases.
We will update the community when we implement this.
Thanks.
Olivier -
This feature has been requested before and we captured it as a story for future releases.
In a meanwhile, you may want to check out this post about Tree Pivot Table Macro. Hope this helps.
Thanks.
Hi Sydd -
Although it might not be so ideal for some cases, Mingle only supports the search with the search keywords that are 3 characters or longer. So yes, the two letter search string is too short and this logic applies to tags as well.
What you might want to try in your case is to rename the tag 'OP' to 'Operation Procedures' (or anything that's meaningful and 3+ characters) - assuming that you tagged all cards you were looking for with OP.
Hope it doesn't cause any big inconvenience. We'll update the documentation about it too.
Thanks.
Regards to the creation of the card with properties, you can assign a value to properties upon creation of the card.
e.g., if you had a property called status, whose value you wanted to set to 'open' during card create, you could do so as follows:
POSTcard[name]=new open storycard[card_type_name]=storyproperties[status]=open...Please notice that the parameters are still in v1 format. This is a known issue and we are going to fix it in the future release.Hope this helped.Hi Russell -
Glad that you have figured it out. Thanks for updating the post.
Hi Rainer -
You can't make any property to be required upon creation of the card in the current version of Mingle.
However this is the feature that's been requested by quite a few other users in the past, so we are considering to implement this in future releases.
We will update the community when this happens. Thanks.
Hi Michael -
Even though they may be harmless, we acknowledge that it's not ideal that you are seeing those errors in such a rate (errors from your first post). I have created a bug for this, so we can resolve this problem in future release.
However the above error message - SVNException: svn: File not found:.... - it seems like it cannot find a revision in a specified subversion location. I have read your other post, we will need to do a further investigation on this.
A question for you - Where is your subversion repository path set to; the repository root OR subfolder of the root?
Thanks for being patient.
Hi Michael -
Have you tried to wait for the repository to be fully cached in spite of such an error message? This may be a known issue - the fact that you are getting such a message - but normally it won't impact the revision content caching in any way.
You mentioned that it seemed to work fine in the beginning but later looked given up. Mingle normally picks up a batch of revisions to cache and then sleep for a while. It will continue to work after a sleep until all revisions are cached.
I have consulted this with the development team with the log you provided, and it doesn't seem like there is any particular issue.
Please try again and let us know if this helped at all. Thanks.
Hi Sandy,
Thanks :)
Which version of Mingle were you using? The original template I have posted is made from Mingle 2.3.1. Is there a chance you were using any prior version of Mingle? As we do not support the downgrade, this teamplate will only work on 2.3.1 or higher version of Mingle.
Below is the style I used on the Special Header Actions page on the video.
<style type="text/css">
#hd {
background: url(/your/image/file/location/christmas.gif);
background-repeat: repeat-x;
}
#hd-bottom {
background: transparent;
}
</style>Hope this helped.
Hi Rainer -
I'm afraid there is no workaround to serve your need if you use the template before Mingle 3.0 is released. I meant that if you create your own project or template from scratch then you can avoid such a case since now you know what the problem is. But I have to admin that is not helpful if you use the template. You are right, it would not be reasonable to rebuild the Agile template yourself again.
Hope this was clear. Thanks, Bonna.
Hi Rainer -
Welcome to Mingle.
Unfortunately this is a known defect. Any card or tree relationship property that was once set to a project variable - such as "Current Iteration" - cannot be set to "not set" in card defaults. This will be fixed in Mingle 3.0 which will be released later this year. In a meantime you could create your own project or template to avoid such a case? Hope this is not too inconvenient.
Thanks, Bonna.
Hi Jason -
We do not provide highlights on failed rows during import, but we do provide which rows have been failed and why (e.g. too long, bad format etc)
What was actually causing your import to fail?
Hi guys -
I’ve added this request to our backlog for future releases.
Thanks.