The release label creation at the RTC project area level
I have the following team structure under project area
Proj-Cheeta-PF ===> Team1
Team2
Team3
When I tried to create the "Release" lable at project area level (used it in "defect" work item), there is an option to "restrict" visibility to other team members.
How this release label is “restricted” to the particular team area? Here how the tool identify which “Team area” this label should be restricted? There is no option to select the “team area” that should be visible or restricted! Based on which information this is “restricted”? Please clarify.
2 answers
Hi,
looking at the help, I have to admit, it leaves a lot to be desired in explaining this feature.
The best hint i found is when creating a release from a build in Eclipse:
What this setting does, as far as I can tell is as follows:
It hides the release as selectable in the Found In work item attribute for anyone who is not a member of the project area or a team area within that project area.
If you change the visibility in the Eclipse client, it also says "Project Internal".
The reason why this is not on an individual team level is basically because releases have no direct relationship to a team area. They don't even necessarily have a relationship to a build. So there is no ownership that could be used.
This feature is meant to allow the project to create many releases on the way to their final one, but hide intermediate releases from external users, so that they can't file work items against it.
looking at the help, I have to admit, it leaves a lot to be desired in explaining this feature.
The best hint i found is when creating a release from a build in Eclipse:
What this setting does, as far as I can tell is as follows:
It hides the release as selectable in the Found In work item attribute for anyone who is not a member of the project area or a team area within that project area.
If you change the visibility in the Eclipse client, it also says "Project Internal".
The reason why this is not on an individual team level is basically because releases have no direct relationship to a team area. They don't even necessarily have a relationship to a build. So there is no ownership that could be used.
This feature is meant to allow the project to create many releases on the way to their final one, but hide intermediate releases from external users, so that they can't file work items against it.
Comments
One option you can consider now (assuming any enhancement would take some time to make its way into the product): For each release, prefix the label with a name that makes it easier to scope. E.g., in your example:
[Ford] S1
[Ford] S2
...
[Honda S1]
....
At least, while the list will still be long, the user can scroll quickly to the release they care about.
The other thing you can do is make eager use of the ability to "archive" a release as soon as it is no longer relevant for current work.
Also, just wanted to make the usage is what you intend: This is the value that will appear in the "found in" field, e.g, for reporting defects. This is not the same as what is available for the "planned for" field.
[Ford] S1
[Ford] S2
...
[Honda S1]
....
At least, while the list will still be long, the user can scroll quickly to the release they care about.
The other thing you can do is make eager use of the ability to "archive" a release as soon as it is no longer relevant for current work.
Also, just wanted to make the usage is what you intend: This is the value that will appear in the "found in" field, e.g, for reporting defects. This is not the same as what is available for the "planned for" field.