Using TestTrack’s automation rules is a great way to populate field values, move an object through the workflow, interface with another system, and notify the right people about what is happening in their project. Some of these rules can get complicated and often some tracing and debugging is necessary to make sure the rule is working as you designed it.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponArchive for December, 2009
Since the introduction of TestTrack RM earlier this year, I’ve had a chance to demonstrate the product many times to prospects. While the initial feature set of the product is impressive, every once in a while I do hear about features that are not currently available. These become feature requests, which are prioritized and scoped out by our product management team.
One feature request I have heard a few times is for a very specific need. This scenario is for a user whose only action related to requirements is to approve or reject them. This user is not in development, QA, or any other group directly involved with software development and does not use TestTrack. This individual is likely to only deal with business requirements and not functional requirements. The user does not want to install the TestTrack client and learn how to use it when only a simple view is needed to review and approve or reject requirements.
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUpon
A common question I hear from TestTrack users is how to display a value that was entered as part of a workflow event on the main issue/test case/requirement window. As some of you may know, this is not “out of the box” functionality. However, this can be configured rather easily using automation rules and custom fields.
The only requirement is that the field on the main window has to be of type “String”.
Continue reading…
Works with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
Some time ago, I posted an example on how to use Surround SCM triggers in conjunction with the workflow to email a file in your local working directory.
While the solution was nice in that it involved the workflow, it was very cumbersome to set up and configure.
This plug in sample simplifies the process and uses the Outlook Interop interface to launch an Outlook message with the local file attached.
Continue reading…
This Surround SCM plugin allows you to view JIRA issues from the Surround SCM client.
Continue reading…
Escalation rules allow you to evaluate a certain condition on a continuous, scheduled basis. The most common use for escalation rules is to prevent inactivity on items. For example, every day at midnight, check for any items that have not been modified in the last 3 days. Escalation rules also allow you to configure an action or actions to perform on any item that matches the criteria, which is specified in the form of a filter.
Continue reading…
Works with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
This is a Mac version of the Launch Outlook example. In this example, we’ll use Applescript to attach the files. The AppleScript is a little more complicated, as we have to handle the various ways that the results can be passed in (see the original article for the details.)
Share on Technorati . del.icio.us . Digg . Reddit . Slashdot . Facebook . StumbleUponWorks with Surround SCM 2010 and later
Will not work with Surround SCM 2009 and earlier
Overview
This is a short sample showing how to leverage the new client menu integration in Surround SCM 2010 and AppleScript on the Mac. This sample shows how to add a file context menu item which copies the sscm:// path to the clipboard for pasting into another application. The XML file for the menu is simple enough (Please refer to the Surround SCM Custom Client Menus article for help on creating a custom menu option to access the tool)
Continue reading…
