Restricting state change based on user defined conditions
![]()
Hi
We have a number of exit criteria that we need to fulfil based on tasks to be done and the state of test cases in RQM before a Story can be considered 'ready' and we are looking for a way of highlighting if 'all is OK'. In this way we might be able to look at the Story to say all is OK and restrict the state change if all is not OK. Can this be done? I'm guessing the answer is not automatically. I know that we can add fields that we can set to yes or no, but it would be smart if we could automate it in some way. Hope someone can help! Thanks, Nigel. |
2 answers
![]() Hi Hey Nigel, I think it will be hard to make a "marker" but you can code your own precondition which will prevent you from putting a story in a specific state based on some other criterias in RTC. |
![]()
Geoffrey Clemm (30.1k●3●30●35)
| answered Oct 08 '10, 7:10 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
One common way to handle this is to model the exit criteria as
"approvals". This allows you to indicate who is expected to set that exit condition, as well as specify a date by which it is expected to be done. The in the process editor, you can specify that the approvals must be satisfied in order for the work item to be marked as done. Cheers, On 10/8/2010 10:23 AM, NigelLH wrote: Hi |