Is there a way to prevent new timelines from being created during WI imports with Planned For updates
During work item imports with Planned For value updates, if Planned For value does not match existing timeline values, new/bogus timelines are being created. Is there any way to prevent this from happening? It is very easy to make a mistake in setting the Planned For value for import. First, following advice of exporting first to get the correct values to work with can mislead the person doing the import; the Planned for value really needs to be the internal value and not the visible value which is the default. And, of course in general it is easy to have other mistakes.
I would think that RTC should just come back with an error if Planned For values do not match, or provide a means to remove the permission for certain roles (doing imports) to create new timelines. I have looked in role permissions and didn't see anything obvious.
I am working on a project with 100+ users doing imports and 6 scrum masters importing Planned For values every sprint during sprint planning, so when bogus timelines get created it is difficult to clean up.
Any help would be greatly appreciated.
One answer
Try using an id (for bulk load) with the assigned role that doesn't have permission to modify project area or timeline structure.
Comments
showing 5 of 10
show 5 more comments