Hiding Work Item fields from certain user groups
Is there a way to make certain work item fields invisible to some users, but visible to others?
For example, the use case would be a work items that was created by a customer, with additional fields available for internal use but hidden from the customer view. Both groups would be able to see the open items in a query, however, but opening the details of the work item would reveal separate information to each group.
Thanks in advance.
For example, the use case would be a work items that was created by a customer, with additional fields available for internal use but hidden from the customer view. Both groups would be able to see the open items in a query, however, but opening the details of the work item would reveal separate information to each group.
Thanks in advance.
3 answers
Is there a way to make certain work item fields invisible to some users, but visible to others?
For example, the use case would be a work items that was created by a customer, with additional fields available for internal use but hidden from the customer view. Both groups would be able to see the open items in a query, however, but opening the details of the work item would reveal separate information to each group.
Thanks in advance.
This work item contains a discussion of new capabilities that may be helpful. It was not clear to me if this provided the full flexibility you require. https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/64253
The short answer is no, you cannot really hide specified fields from
specific groups. Work item 64253 gives you control on how things get
displayed in editors, but does not allow you to control what is seen in
query results.
But if hiding things in the editor is of value to you, you'll have to
decide how you want to specify the groups that are allowed to see the
specified fields. One reasonable approach would be to say that only
users that are in a specified role in the project can see the specified
field. I speculate that you then could use the mechanism described in
work item 64253 to display the given field only if the current user has
that role (if someone from the work item team could confirm/deny that
speculation, that would be good).
Cheers,
Geoff
rsnelson wrote:
specific groups. Work item 64253 gives you control on how things get
displayed in editors, but does not allow you to control what is seen in
query results.
But if hiding things in the editor is of value to you, you'll have to
decide how you want to specify the groups that are allowed to see the
specified fields. One reasonable approach would be to say that only
users that are in a specified role in the project can see the specified
field. I speculate that you then could use the mechanism described in
work item 64253 to display the given field only if the current user has
that role (if someone from the work item team could confirm/deny that
speculation, that would be good).
Cheers,
Geoff
rsnelson wrote:
This work item contains a discussion of new capabilities that may be
helpful. It was not clear to me if this provided the full
flexibility you require.
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/64253
nkotterwrote:
Is there a way to make certain work item fields invisible to some
users, but visible to others?
For example, the use case would be a work items that was created by
a customer, with additional fields available for internal use but
hidden from the customer view. Both groups would be able to see the
open items in a query, however, but opening the details of the work
item would reveal separate information to each group.
Thanks in advance.
Yes Geoff, your speculation goes is the right direction.
The problem is that editor presentations are global per project area,
so it is not possible to have different presentations for different
teams or roles.
However, for Post-2.0 we are planning to add role support to attribute
visibility.
--andre weinand
RTC Work Item Team
On 2009-05-23 04:41:50 +0200, Geoffrey Clemm <geoffrey> said:
nkotterwrote:
Is
The problem is that editor presentations are global per project area,
so it is not possible to have different presentations for different
teams or roles.
However, for Post-2.0 we are planning to add role support to attribute
visibility.
--andre weinand
RTC Work Item Team
On 2009-05-23 04:41:50 +0200, Geoffrey Clemm <geoffrey> said:
The short answer is no, you cannot really hide specified fields from
specific groups. Work item 64253 gives you control on how things get
displayed in editors, but does not allow you to control what is seen in
query results.
But if hiding things in the editor is of value to you, you'll have to
decide how you want to specify the groups that are allowed to see the
specified fields. One reasonable approach would be to say that only
users that are in a specified role in the project can see the specified
field. I speculate that you then could use the mechanism described in
work item 64253 to display the given field only if the current user has
that role (if someone from the work item team could confirm/deny that
speculation, that would be good).
Cheers,
Geoff
rsnelson wrote:
This work item contains a discussion of new capabilities that may be
helpful. It was not clear to me if this provided the full
flexibility you require.
https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/64253
nkotterwrote:
Is
there a way to make certain work item fields invisible to some
users, but visible to others?
For example, the use case would be a work items that was created by
a customer, with additional fields available for internal use but
hidden from the customer view. Both groups would be able to see the
open items in a query, however, but opening the details of the work
item would reveal separate information to each group.
Thanks in advance.