Team area admin can't save dev.line change for the team area
Using Eclipse way process we have two team areas created directly under the project area. The team area admin also the teamlead role, report that when they tried to switch dev. lines for their team areas, they can't save the change and got permission error.
Users with project area admin role has no problem to save the changes.
I noticed that The Save Team Area operation is a server side operation that is executed whenever a team area is saved in the repository. Note that the creation
of root (first-level) team areas is not governed by this operation; it is governed by the Save Project Area project operation.
Is it possible that it also applies when it comes to change dev. line (swicth from one to another)in team area?
Users with project area admin role has no problem to save the changes.
I noticed that The Save Team Area operation is a server side operation that is executed whenever a team area is saved in the repository. Note that the creation
of root (first-level) team areas is not governed by this operation; it is governed by the Save Project Area project operation.
Is it possible that it also applies when it comes to change dev. line (swicth from one to another)in team area?
One answer
Answer to my own question:)
I guess the rational behind this behaviour is that Eclipse Way process template is for single devlopment line. We need to switch the dev. line because we need to support concurrent release iterations across different dev. lines.
By checking the other process template CloudBurst which supports concurrent dev. lines, we figured out that we don't need to let teamlead switch the dev. line, but instead create corresponding team areas for each dev. line and stick with them.
Still hope to see alternative solutions though.
I guess the rational behind this behaviour is that Eclipse Way process template is for single devlopment line. We need to switch the dev. line because we need to support concurrent release iterations across different dev. lines.
By checking the other process template CloudBurst which supports concurrent dev. lines, we figured out that we don't need to let teamlead switch the dev. line, but instead create corresponding team areas for each dev. line and stick with them.
Still hope to see alternative solutions though.