After workitem moved to resolved, stop editing of changeset
After the workitem moved to the resolved state, user can still add or remove or edit the changeset attached to the workitem. My intension is, the user cannot be able to add/remove/edit the changeset attached to work item after the work item moved to the resloved state.
Please suggest what setting i do in my project to fullfill the above intension.
Please suggest what setting i do in my project to fullfill the above intension.
6 answers
I don't think that can currently be enforced. It's recommended to complete all associated change sets before closing the work item (change sets are automatically completed on deliver), but AFAIK there's no way to enforce that, and no way to prevent further change sets from getting associated after the work item is closed.
There's a similar enhancement request open: 108857: Add a process rule that validates that all change sets in a work item are complete.
See also 124331: In change set its possible to use already ( a long ago ) closed workitems.
I suggest adding your thoughts to the first one.
There's a similar enhancement request open: 108857: Add a process rule that validates that all change sets in a work item are complete.
See also 124331: In change set its possible to use already ( a long ago ) closed workitems.
I suggest adding your thoughts to the first one.
I don't think that can currently be enforced. It's recommended to complete all associated change sets before closing the work item (change sets are automatically completed on deliver), but AFAIK there's no way to enforce that, and no way to prevent further change sets from getting associated after the work item is closed.
There's a similar enhancement request open: 108857: Add a process rule that validates that all change sets in a work item are complete.
See also 124331: In change set its possible to use already ( a long ago ) closed workitems.
I suggest adding your thoughts to the first one.
what about "Restict associating to closed work items" operation behavior? This doesn't seem to work. Any information on this would help. we are using 2.0.0.2 IFIX3
Thanks,
Binoy
We are using 2.0.0.2 IFIX3. I am comparing the two snapshots. time difference between them is 3months. The comparing tool fails saying...
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0586I Query is too complex (7524 parameters).
Any idea what is the maximum no. of work items that can be compared by the compare tool of RTC???
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0586I Query is too complex (7524 parameters).
Any idea what is the maximum no. of work items that can be compared by the compare tool of RTC???
It probably isn't the number of work items that is a problem (more
likely, change sets), but in either case, please submit a bug report ...
the system should never generate a "Query is too complex" error on a
snapshot compare operation.
Cheers,
Geoff
On 2/18/2011 12:23 AM, dibyanduroy wrote:
likely, change sets), but in either case, please submit a bug report ...
the system should never generate a "Query is too complex" error on a
snapshot compare operation.
Cheers,
Geoff
On 2/18/2011 12:23 AM, dibyanduroy wrote:
We are using 2.0.0.2 IFIX3. I am comparing the two snapshots. time
difference between them is 3months. The comparing tool fails
saying...
com.ibm.team.repository.common.TeamRepositoryException: CRJAZ0586I
Query is too complex (7524 parameters).
Any idea what is the maximum no. of work items that can be compared by
the compare tool of RTC???
We're facing the same error while loading a Product Backlog plan. This only happens to one backlog in one Project Area. We have several backlogs there and several project areas using more or less the same processes, and no issues there.
An error occurred while executing the operation. See the error log for details.
CRJAZ0586I Query is too complex (14391 parameters).
Is there any update on this?
An error occurred while executing the operation. See the error log for details.
CRJAZ0586I Query is too complex (14391 parameters).
Is there any update on this?
