-
Suggestion
-
Resolution: Duplicate
-
None
-
None
Could it be possible to restrict access to time spent information in issues, exports, activity tab & history tab for clients ?
Today, even if we block access to worklog to certain users groups, they can access to these information by having a look at the activity or history tab, or by exporting issues, or displaying "time spent" in dashboard gadgets. It should be blocked everywhere.
- duplicates
-
JRACLOUD-41728 Time Spent entries show up in History tab
- Gathering Interest
[JSWCLOUD-16473] Restrict access to time spent
Workflow | Original: JAC Suggestion Workflow JSWCLOUD [ 4098524 ] | New: JAC Suggestion Workflow 3 [ 4369721 ] |
Workflow | Original: JAC Suggestion Workflow 3 [ 3701985 ] | New: JAC Suggestion Workflow JSWCLOUD [ 4098524 ] |
Workflow | Original: JAC Suggestion Workflow [ 3465485 ] | New: JAC Suggestion Workflow 3 [ 3701985 ] |
Status | Original: RESOLVED [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2494401 ] | New: JAC Suggestion Workflow [ 3465485 ] |
Status | Original: Closed [ 6 ] | New: Resolved [ 5 ] |
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Open [ 1 ] | New: Closed [ 6 ] |
Link | New: This issue duplicates JRACLOUD-41728 [ JRACLOUD-41728 ] |
Description |
Original:
Could it be possible to restrict access to time spent information in issues, exports, activity tab & history tab for clients ?
Today, even if we block access to worklog to certain users groups, they can access to these information by having a look to the activity or history tab, or by exporting issues, or displaying "time spent" in dashboard gadgets. It should be blocked everywhere. |
New:
Could it be possible to restrict access to time spent information in issues, exports, activity tab & history tab for clients ?
Today, even if we block access to worklog to certain users groups, they can access to these information by having a look at the activity or history tab, or by exporting issues, or displaying "time spent" in dashboard gadgets. It should be blocked everywhere. |