The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Enable export for user group without work log

Christian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 1, 2024

Hello everyone,

I have multiple "Project Roles" (Admin --> System --> Security --> Project Roles) to manage access rights and functions on projects for different users. Among these roles is one called "Customer".

I want to enable users of that group to export tickets and filtered tickets. Currently they don't have that option, but I can allow it by going to "Admin --> Issues --> Permission schemes" and in the corresponding scheme by adding the user group to "Work On Issues" at the bottom of the page under the section "Time tracking permissions". I haven't found any other option where I could enable the export option.

The problem with my solution is, that it enables the "Customer" users to log their work and see logged work from others.

Is it possible to enable the export feature (maybe elsewhere) and keep the work log hidden?

I am using Jira Server 9.5.0.

Thanks in advance for your suggestions and help.
Chris

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Deniz Oğuz - The Starware
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
August 24, 2026

Hi Christian,

Even if some add-ons lets you hide time tracking from the UI, Customers can still use Jira's REST API (https://yours-server/api/latest/issue/ISSUE-KEY something like that) URL to the browser and get all of the issue details. Without built-in support from Jira itself, it is not possible to do. ACloud is worse of course.

What you can do is, you may create subtasks for issues, and only let your own users (not customers) to view those issues using "issue level security". Or you may track worklogs in another project which customers doesn't have access and link those issues together.
Please note that there are other places where customer can see worklogs, for example, in issues "history tab", dashboard "activity gadget". If you are ok with only hiding these information from the UI, WorklogPRO can hide most of them. 

Disclaimer: I work for vendor of WorklogPRO.

0 votes
Анна
August 22, 2026

Hi Chris,

I dug into this a bit and it looks like this is actually a built-in limitation of Jira rather than something wrong with your setup. Worklog visibility is tied directly to the "Work on issues" permission, and there's no separate permission for "export without worklog" in standard Jira. I found a few similar discussions on the forum with the same conclusion, so you're not missing some hidden setting.

One option that might actually solve this is a marketplace app called Field Security for Jira. It lets you hide specific fields, including time tracking/worklog, from selected groups regardless of what your permission scheme says. So you'd keep your "Customer" group in "Work on Issues" (so export keeps working for them), and the app would hide the worklog tab/field from their view on top of that.

I haven't tested it myself, but based on the description it sounds like it's built for exactly this kind of situation. Might be worth trying the free trial first to confirm it works well with Server 9.5.0 before buying.

Hope this points you in the right direction!

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events