Traceability to individuals and privacy reasons ?
2 answers
Thomas,
I'd like to learn more about the particular issues you
have in mind. Can you point me to specific examples?
Like any other bug tracking system Jazz keeps track of the
owner of a bug. In addition to that, the Jazz reporting
component can store how the work items evolve over time.
This information is presented and visualized through
reports. I assume this is what you consider sensitive.
Jazz provides different control mechanism over
these reports:
1) The process associated with a particular project
area defines which reports are initially available for
a project.
2) Permissions govern who can define new reports
or run reports.
In addition, the process definitions that come with
Jazz do not include any reports on individuals.
One reason is the concern you mention above. The
other reason is that we have a team first focus in
Jazz. In this context this means, that we are more
interested in how the team is doing rather than
individual developers.
--erich
I'd like to learn more about the particular issues you
have in mind. Can you point me to specific examples?
Like any other bug tracking system Jazz keeps track of the
owner of a bug. In addition to that, the Jazz reporting
component can store how the work items evolve over time.
This information is presented and visualized through
reports. I assume this is what you consider sensitive.
Jazz provides different control mechanism over
these reports:
1) The process associated with a particular project
area defines which reports are initially available for
a project.
2) Permissions govern who can define new reports
or run reports.
In addition, the process definitions that come with
Jazz do not include any reports on individuals.
One reason is the concern you mention above. The
other reason is that we have a team first focus in
Jazz. In this context this means, that we are more
interested in how the team is doing rather than
individual developers.
--erich
Thomas,
I'd like to learn more about the particular issues you have
in mind. Can you point me to specific examples?
Like any other bug tracking system Jazz keeps track of the
owner of a bug. In addition to that, the Jazz reporting component
can store how the work items evolve over time. This information is
presented and visualized through reports. Jazz provides different
control mechanism over these reports:
1) The process associated with a particular project area
defines which reports are initially available for a project.
2) Permissions govern who can define new reports or
run reports.
In addition, the process definitions that come with Jazz do not include
any reports on individuals. One reason is the concern you mention
above. The other reason is that we have a team first focus in
Jazz. In this context this means, that we are more interested
in how the team is doing rather than individual developers.
--erich
I'd like to learn more about the particular issues you have
in mind. Can you point me to specific examples?
Like any other bug tracking system Jazz keeps track of the
owner of a bug. In addition to that, the Jazz reporting component
can store how the work items evolve over time. This information is
presented and visualized through reports. Jazz provides different
control mechanism over these reports:
1) The process associated with a particular project area
defines which reports are initially available for a project.
2) Permissions govern who can define new reports or
run reports.
In addition, the process definitions that come with Jazz do not include
any reports on individuals. One reason is the concern you mention
above. The other reason is that we have a team first focus in
Jazz. In this context this means, that we are more interested
in how the team is doing rather than individual developers.
--erich
Hello,
is traceability to individuals something that can be switch off for
privacy reasons?
The reasons for this question are the different legal situations in
different countries, concerning union and privacy rights.
Best Regards
Thomas