...
If time tracking is activated in JIRA and a user has the rights to browse a certain project, there is no way in JIRA to restrict access to time tracking information, i.e. time logged with all description details as well as work estimates will be visible to a user who sees has access to issues. Even though you can restrict the right to log time, you can't prevent users from seeing time tracking information, and you can't restrict access to the fields "Original estimate" and "Remaining estimate" (these fields appear even of you do not grant the "work on issues" permission). This might be perfectly okay within a developper team, but probably is generating huge problems if you grant your customers access to a project. There is no proper solution for this as JIRA does not offer this level of permissions.
...
You have the following configuration options:
SS XXX
Note |
---|
You are denying access! By default, according to JIRA permissions, all users with browse project permissions can see the information. |
Permission | Description | Remarks |
---|---|---|
Tab Permissions | Deny access to the tabs "All", "Work Log", "Activity", "History", "Activity Stream" on the view issue screen. Deny access to the Activity Stream on the project summary screen. All these tabs contain time tracking information. | The activity stream can also be available as gadget on dashboards; see note below. |
Webpanel Permissions | Deny access to Webpanels; this is the "Time Tracking" panel in the right column of the view issue screen. | |
Issue Permissions | Deny access to "original estimate" and "remaining estimate" fields on the create/edit issue screen. |
Note |
---|
The Activity Stream gadget for dashboards will also display time tracking information. As there is no way from preventing users with browse project rights to create own dashboards and to add any gadget they want, you can only take away this gadget from the system dashboard and hope that your clients have better things to do than adding new dashboards with the Activity Stream Gadget. We are looking for a solution for this, too. |
Note |
You are denying access! By default, according to JIRA permissions, all users with browse project permissions can see the information. |
Permissions are set on group level. You can select as many existing groups as you need:
...