• Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Problem:
      Since we upgraded from JIRA 5.2 to 6.3.12 on 23.11.2014, we see that the work logged within JIRA (or Tempo in our case) is shown in the History tab of each issue. This was not the case in the older JIRA version.
      We updated to JIRA 6.3.13 to get rid of the worklog emails, but 6.3.13 did not change the History tab problem.

      Reason:
      For us, it is important that Work Log entries are only visible to concerned persons in the company. This typically are project leaders and accounting. All others should not see the worklog of others. It is OK and helpful to see ones own work logs.

      Background:
      Tempo does a good job in hiding work logs from others. It has permissions for time sheets that fit our needs. But at the JIRA level, this high appreciated level of privacy seems to get lost: Activity Streams show worklog entries, History Tabs show worklog entries. Both shall be hidden to users without permission to do so. We managed to hide Activity Streams (which was a long struggle and not all participants were lucky with the found solution).

      This is also a legal issue: In Europe, personal data must be treated in a special way. This is enforced by national and european laws. As I understand it, the current behaviour of JIRA is not conform to European law, because work logs can be seen by people that are not involved with processing this data.

      Expected Solution:
      The worklog entries should be removed from the history tab for users that do not have the required permission for this. "Issue View" permission is not the right permission to use as well as "Edit All Worklogs". A "View All Worklogs" permission (vs. "View Own Worklogs") would be fine.

            [JRASERVER-41728] Time Spent entries show up in History tab

            +1

            Martin Cvrček added a comment - - edited

            Why is on this issue Resolution: "Won't Do" when Status is GATHERING INTEREST?
            This means that Atlassian has already decided not to do it and the History Tab will forever display data that users do not have permissions to?

            Vote does not work!

            Please explain, thank you

            Martin Cvrček added a comment - - edited Why is on this issue Resolution: "Won't Do" when Status is GATHERING INTEREST? This means that Atlassian has already decided not to do it and the History Tab will forever display data that users do not have permissions to? Vote does not work! Please explain, thank you

            eran.gur added a comment -

            +1

            eran.gur added a comment - +1

            I already commented in the Community regarding the named matter:

            Not displaying personal data such as time recording data for other people in the company is an extremely important part of works council agreements and GDPR throughout Europe. 

            Because of the current display of times in the history, time recording in Jira, also in combination with e.g. Tempo Timesheets, is completely senseless.

            The option not to display recorded times, everywhere, is a legal issue. I have no idea how Atlassian could not take care of this issue for so long.

            To sum it up:

            Currently, time tracking with Jira is not legal compliant in large parts of Europe and certainly in other countries.

            R. Sobotka added a comment - I already commented in the Community regarding the named matter: Not displaying personal data such as time recording data for other people in the company is an extremely important part of works council agreements and GDPR throughout Europe.  Because of the current display of times in the history, time recording in Jira, also in combination with e.g. Tempo Timesheets, is completely senseless. The option not to display recorded times, everywhere, is a legal issue. I have no idea how Atlassian could not take care of this issue for so long. To sum it up: Currently, time tracking with Jira is not legal compliant in large parts of Europe and certainly in other countries.

            +1

             

            Kirandeep Kaur added a comment - +1  

            +1

            Andreas added a comment -

            +1

            Andreas added a comment - +1

            maguialahmar added a comment - - edited

            We have also the same problem, work log appears in activity, history and log work tabs. This should be a personal data, and must only be available to managers not to all users. We appreciate considering this request again. 

            maguialahmar added a comment - - edited We have also the same problem, work log appears in activity, history and log work tabs. This should be a personal data, and must only be available to managers not to all users. We appreciate considering this request again. 

            Frederic Lesguillons added a comment - - edited

            We have exactly the same issue, it is well explained by the reporter. Every project manager I know is annoyed by this huge design flaw.

            We need to use another tool for work logs.

            Frederic Lesguillons added a comment - - edited We have exactly the same issue, it is well explained by the reporter. Every project manager I know is annoyed by this huge design flaw. We need to use another tool for work logs.

            Atlassian Update – 27 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 27 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

              Unassigned Unassigned
              9d8c9b72b212 Michael Roßmann
              Votes:
              3 Vote for this issue
              Watchers:
              30 Start watching this issue

                Created:
                Updated:
                Resolved: