Feature/bug tracking is "simple", as that is a single item and that item is either "done" or not. If it was in status "done", but failed acceptance criteria, the issue gets reopened.

Test tracking is different, because a test can fail and then you need to redo at least that test, or maybe the whole sequence of tests (if they rely on each other). So as I know it, you have a defined test suite, and a test suite then needs a successful test execution, which consists of several test results.

This setup can be implemented in any tracking tool, and I think this is also the reason that all tracking tools are horrible since they all are workflow tools with their own horrible configuration language for that workflow. And usually they are configured by people who don't know the workflow or have no choice but to implement a random workflow using the tool at hand.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.