limit number of work items per workflow
5 answers
WRT visualization, if you group by Dev Status, it is easy to tell
whether a particular state (status) is getting full, or overflowing.
WRT enforcing a limit, we'd need someone familiar with the work item API
to indicate whether there is API to automatically do that check from a
"workitem save" process adviser.
CHeers,
Geoff
On 2/1/2011 7:23 AM, rydiand wrote:
whether a particular state (status) is getting full, or overflowing.
WRT enforcing a limit, we'd need someone familiar with the work item API
to indicate whether there is API to automatically do that check from a
"workitem save" process adviser.
CHeers,
Geoff
On 2/1/2011 7:23 AM, rydiand wrote:
When customizing a workflow for a work item type is it possible to
impose a limit on number of work items per workflow state?
Secondly, is it possible to visualize if that limit is exceeded?
The intention would be to use RTC to visualize the workflow in an
environment where Kanban is used.
Thanks Geoff,
Can you please tell me what is WRT?
Reagrds
Torben
Can you please tell me what is WRT?
Reagrds
Torben
WRT visualization, if you group by Dev Status, it is easy to tell
whether a particular state (status) is getting full, or overflowing.
WRT enforcing a limit, we'd need someone familiar with the work item API
to indicate whether there is API to automatically do that check from a
"workitem save" process adviser.
CHeers,
Geoff
On 2/1/2011 7:23 AM, rydiand wrote:
When customizing a workflow for a work item type is it possible to
impose a limit on number of work items per workflow state?
Secondly, is it possible to visualize if that limit is exceeded?
The intention would be to use RTC to visualize the workflow in an
environment where Kanban is used.
Hi Geoff,
you could create a work item advisor that checks a post condition on saving a work item state. You could query in a work item advisor and get the number of hits. In a change state event one could most likely use his to limit (not allow the transition to that state if there are too many in that state).
Disadvantages I see would be
1. performance: the query would cost time if it is always run changing a state or going into a specific state.
2. Usability: As a user, what am I supposed to do now that I can't change into the state.
I'd rather prefer the team monitors this in dashboards or reports and the team decides to do something if they feel a state gets "Full".
Thanks,
Ralph
you could create a work item advisor that checks a post condition on saving a work item state. You could query in a work item advisor and get the number of hits. In a change state event one could most likely use his to limit (not allow the transition to that state if there are too many in that state).
Disadvantages I see would be
1. performance: the query would cost time if it is always run changing a state or going into a specific state.
2. Usability: As a user, what am I supposed to do now that I can't change into the state.
I'd rather prefer the team monitors this in dashboards or reports and the team decides to do something if they feel a state gets "Full".
Thanks,
Ralph
WRT visualization, if you group by Dev Status, it is easy to tell
whether a particular state (status) is getting full, or overflowing.
WRT enforcing a limit, we'd need someone familiar with the work item API
to indicate whether there is API to automatically do that check from a
"workitem save" process adviser.
CHeers,
Geoff
On 2/1/2011 7:23 AM, rydiand wrote:
When customizing a workflow for a work item type is it possible to
impose a limit on number of work items per workflow state?
Secondly, is it possible to visualize if that limit is exceeded?
The intention would be to use RTC to visualize the workflow in an
environment where Kanban is used.