How to restrict users from adding any new stories/defects in to the current sprint once planning is completed?
We would like to kind of lock the sprint plan once it is approved in the planning meeting. There are scenarios where the stories/defects are either moved out of the sprint or added to the sprint which are already approved by the stakeholders.
We thought of locking the "planned for' attribute for the team members and give access only for certain roles like RTEs. But this will prevent the team members from creating tasks on their own.
We tried to use the snapshots in the plan but it tracks all the changes to workitems. Also, this data could not be reported using JRS or any other mechanism to show in the dashboard.
Is there a way to track these changes to a particular sprint?
|
One answer
Ralph Schoon (63.4k●3●36●46)
| answered Mar 14, 4:09 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER In general, using permissions, you can limit what role can - modify work item links.
There is no criterium for "Planned is done" you could use to control permissions.
You can control permission based on iteration type. You can use an iteration to control which permissions hold and which don't. The JKE Banking Sample shows an example. You could try to use a hidden iteration "planning done" to switch to prevent creating links for roles. You can control which attributes are required in which states and who can set them based on role. So the statement "But this will prevent the team members from creating tasks on their own. " is only how your process is set up. You could allow to create items without having to set planned for in the new state - which actually makes more sense than having it as required in the new state. In this respect, I would suggest to review your required attributes. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.